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? | 2021-06-06 | 2021-06-20 | ||
---|---|---|---|---|
Visual display | shapes.txt | |||
Navigation | levels.txt | |||
pathways.txt | ||||
Fares | fare_leg_rules.txt | |||
fare_rules.txt | ||||
Technical contacts | feed_info.txt | |||
Cal-ITP validation errors observed | Number of errors | |||
Error Name | Error Description | 2021-06-06 | 2021-06-20 | |
same_name_and_description_for_route | The GTFS spec requires that a route_description is distinct from both the route short and long names. | 11 | 11 | |
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). | 2 | 2 |