Open barbeau opened 2 years ago
Comment by barbeau
Friday Jul 07, 2017 at 21:09 GMT
Note that there are a few existing rules/issues related to this, but that don't cover this issue exactly:
stop_sequence
(for stop_time_updates that include stop_sequence, and https://github.com/CUTR-at-USF/gtfs-realtime-validator/issues/159 for stop_time_updates that don't include stop_sequence)stop_time_updates
have the same stop_sequence
stop_time_updates
have the same stop_id
stop_time_update
stop_sequence
and stop_id
do not match GTFSSo it seems that a good implementation for a new rule here would be to implement a HashMap used to check that each stop_sequence
appears only once for all stop_time_updates
in a trip (to be implemented in StopTimeUpdateValidator
). We can do the same with stop_id
, but only for routes that don't include loops that visit a stop_id
more than once (i.e., if the trip_id
key doesn't exist in GtfsMetadata.getTripsWithMultiStops()
HashMap
). It seems like this could actually replace E036 and E037 if it covers those scenarios.
For TripUpdate. This would generate an error. See https://groups.google.com/d/msg/gtfs-realtime/qNc7ButQbW8/tDwanvClBQAJ.