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-03-06 | 2022-03-20 | ||
---|---|---|---|---|
Visual display | shapes.txt | |||
Navigation | levels.txt | |||
pathways.txt | ||||
Fares | fare_leg_rules.txt | |||
fare_rules.txt | ||||
Technical contacts | feed_info.txt | |||
Validation errors observed | ||||
Error Name | Error Description | Severity | ||
route_short_name_too_long | Short name of a route is too long (more than 12 characters). Note that major trip planning applications start truncating short names after seven characters. | WARNING | ||
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). | WARNING | ||
Cal-ITP validation errors observed | Number of errors | |||
Error Name | Error Description | 2022-03-06 | 2022-03-20 | |
route_short_name_too_long | Short name of a route is too long (more than 12 characters). Note that major trip planning applications start truncating short names after seven characters. | 4 | ||
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). | 73 | 73 |