search

CUTR-at-USF / gtfs-realtime-validator

Java-based tool that validates General Transit Feed Specification (GTFS)-realtime feeds. See https://github.com/MobilityData/gtfs-realtime-validator for the latest!
Other
92 stars 40 forks source link

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

Open barbeau opened 8 years ago

barbeau commented 8 years ago

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 7 years ago

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 7 years ago

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

barbeau commented 4 years ago

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