MobilityData / gtfs-realtime-validator

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

Should header timestamps always be the most recent timestamp in the feed? #48

Open isabelle-dr opened 2 years ago

isabelle-dr commented 2 years ago

Issue by barbeau October 11, 2017 Originally opened as https://github.com/CUTR-at-USF/gtfs-realtime-validator/issues/288


We currently throw an error E012 (https://github.com/MobilityData/gtfs-realtime-validator/blob/master/RULES.md#e012---header-timestamp-should-be-greater-than-or-equal-to-all-other-timestamps) if any entity timestamps are greater than the header timestamp, as I believe this is the most common interpretation of the spec.

However, I tried to formalize this in the spec via google/transit#55 and wasn't able to get any agencies or consumers attention to comment on it (google/transit#55). This would be a good candidate for GTFS-realtime best practices discussion.