This is a monthly report, generated by the California Integrated Travel Project (Cal-ITP), summarizing issues discovered by MobilityData’s GTFS Validator. This report is available for viewing by the general public to support continuous improvement of GTFS data and the experience of transit passengers.
|Do the following files/fields exist?||2022-02-06||2022-02-20|
|Cal-ITP validation errors observed||Number of errors|
|Error Name||Error Description||2022-02-06||2022-02-20|
|duplicate_route_name||All routes of the same route_type with the same agency_id should have unique combinations of route_short_name and route_long_name.||12||12|
|feed_expiration_date||At any time, the published GTFS dataset should be valid for at least the next 7 days, and ideally for as long as the operator is confident that the schedule will continue to be operated. If possible, the GTFS dataset should cover at least the next 30 days of service.||1|
|too_fast_travel||As implemented in the original Google Python GTFS validator, the calculated speed between stops should not be greater than 150 km/h (42 m/s SI or 93 mph).||392|