This repository has been archived by the owner on May 27, 2024. It is now read-only.
StopTimeUpdate.ScheduleRelationship must not be SCHEDULED or SKIPPED for frequency type 0 trips #334
Labels
frequency-type-0
Related to GTFS trips defined in frequencies.txt with exact_times=0 or empty
GTFS(-rt) spec clarification
new rule
your-first-pr
Issues that are a good place to start contributing to the project
Summary:
For trips defined in frequencies.txt with exact_times=0, TripUpdates feeds should not have stop_time_updates with a schedule_relationship of
SCHEDULED
orSKIPPPED
- these are only relevant for schedule-based transit (trips not defined in frequencies.txt or in frequencies.txt but with exact_times=1).So, the following feed should not be valid:
Related - I'm proposing adding an StopTimeUpdate.ScheduleRelationship UNSCHEDULED enumeration value in GTFS-realtime spec here:
google/transit#102
EDIT - Actually, considering that
SCHEDULED
is the default value, it shouldn't really be empty either, although until the above issue is clarified in GTFS-rt, I suppose empty is the best option.Steps to reproduce:
Run TransitClock on USF Bull Runner data:
https://github.com/CUTR-at-USF/bullrunner-gtfs-realtime-generator
Expected behavior:
Flag
stop_time_update
with the values of SCHEDULED or SKIPPPED as an error for trips that are defined in frequencies.txt with exact_times=0 (or empty)Observed behavior:
Validator does not flag
stop_time_updates
with the values of SCHEDULED or SKIPPPED as an error for trips that are defined in frequencies.txt with exact_times=0 (or empty)Platform:
N/A
cc @scrudden
The text was updated successfully, but these errors were encountered: