search

MobilityData / gtfs-realtime-validator

Java-based tool that validates General Transit Feed Specification (GTFS)-realtime feeds
Other
38 stars 9 forks source link

Frequency-based trips: use arrival/departure times, not delay #132

Closed e-lo closed 2 years ago

e-lo commented 2 years ago

Relevant Best Practice text:

For trips denoted in GTFS frequency.txt as frequency-based by setting exact_times=0 or omitting the exact_times field In TripUpdate.StopTimeUpdate, the StopTimeEvent for arrival and departure should not contain delay because frequency-based trips do not follow a fixed schedule. Instead, time should be provided to indicate arrival/departure predictions.

barbeau commented 2 years ago

I believe this issue is a duplicate of https://github.com/MobilityData/gtfs-realtime-validator/issues/64.

e-lo commented 2 years ago

Closing as duplicate after adding relevant best practice text to #64 and flagging as a GTFS RT Best Practices