search

MobilityData / gtfs-realtime-validator

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

Check that there is at most one TripUpdate per scheduled trip_id #20

Open barbeau opened 2 years ago

barbeau commented 2 years ago

Issue by barbeau Wednesday Nov 30, 2016 at 18:51 GMT Originally opened as https://github.com/CUTR-at-USF/gtfs-realtime-validator/issues/33

For TripUpdate. This would generate an error. See https://groups.google.com/d/msg/gtfs-realtime/qNc7ButQbW8/tDwanvClBQAJ.

Note that this only applies to normally scheduled trips, not trips appearing in GTFS frequencies.txt.

barbeau commented 2 years ago

Comment by barbeau Thursday Jul 06, 2017 at 21:27 GMT

https://github.com/google/transit/blob/master/gtfs-realtime/spec/en/trip-updates.md says:

There should be at most one trip update for each scheduled trip. In case there is no trip update for a scheduled trip, it will be concluded that no realtime data is available for the trip. The data consumer should not assume that the trip is running on time.

barbeau commented 2 years ago

Comment by barbeau Thursday Sep 07, 2017 at 02:51 GMT

Implementation of this will likely be related to https://github.com/CUTR-at-USF/gtfs-realtime-validator/issues/255.

barbeau commented 2 years ago

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

Implementation of this rule can be very similar to detecting if vehicle_ids are unique in E052: https://github.com/CUTR-at-USF/gtfs-realtime-validator/blob/master/RULES.md#E052