search

MobilityData / gtfs-realtime-validator

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

Remove rule E014 related to TripUpdates being in block order #37

Open barbeau opened 2 years ago

barbeau commented 2 years ago

Issue by barbeau Wednesday Apr 26, 2017 at 13:58 GMT Originally opened as https://github.com/CUTR-at-USF/gtfs-realtime-validator/issues/158

Summary:

trip_updates for each trip in the feed must match the sequential order for the trips in the block. For example, if we have trip_ids 1, 2, and 3 that all belong to the same block, and the vehicle travels trip 1, then trip 2, and then trip 3, the trip_updates should occur in the GTFS-rt feed in the order trips 1, 2, and 3. For example, trip 3 predictions shouldn't occur in the feed prior to trip 2 predictions. If they are out-of-order, this is an error.

This is currently defined as E014 in ValidationRules but is not implemented.

barbeau commented 2 years ago

Comment by barbeau Tuesday Mar 27, 2018 at 19:03 GMT

To my knowledge this isn't actually currently clearly specified in the GTFS-rt spec, so it requires clarification as well.

barbeau commented 2 years ago

Comment by barbeau Monday Jul 29, 2019 at 21:30 GMT

Proposal opened at https://github.com/google/transit/pull/176.

barbeau commented 2 years ago

Comment by barbeau Monday Feb 17, 2020 at 14:23 GMT

https://github.com/google/transit/pull/176 was accepted, which means that producers don't need to provide TripUpdates in block order in feeds.

So, we need to remove rule E014 - it's not currently active, but we should delete it to be clear.