Elizabeth Sall
Elizabeth Sall
🤔 🤔 🤔 Hmmm... I think this conflicts with the descriptions of times in [`stop_times.txt`](http://gtfs.org/schedule/reference/#stop_timestxt), which specify *local time* in the sentence discussing overnight travel? > For times occurring after...
Regardless, the spec needs to clarify in `stop_times.txt` whether it is agency time or local time for the stop which is specified. Amtrak has implemented it as local time. -...
> I could not reproduce the issue. I ran the validator on the dataset given in this PR...I got 12 fast_travel_between_far_stops but no mention of stop NDL That is b/c...
Submitted this issue: https://github.com/google/transit/issues/322
> A possible solution could be to always generate a WARNING and let data producers/consumer decide on whether or not an entry should be fixed. Perhaps the warning should be...
> flagged as part of the manual GTFS grading process? I think both would be useful, but food for thought: 1. In our experience the grading process already takes a...
> We invite this part of the industry to contribute in kind as an op-in validation rule What is the framework for parameterizing what rules are called?
The above was my interpretation of the best practice under [`stop.txt location_type`](https://gtfs.mobilitydata.org/spec/gtfs-schedule#h.o3q8uyzc81o7) which is as follows: > Many stations or terminals have multiple boarding facilities (depending on mode, they might...
> When naming the station and child stops, set names that are well-recognized by riders, and can help riders to identify the station and boarding facility (bus bay, platform, wharf,...
I wasn't part of the original best-practice discussion as to why this is important. Perhaps @LeoFrachet or @antrim can provide background (or link to it?)