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-12-05 | 2021-12-19 | ||
|---|---|---|---|---|
| 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 | Number of errors | |||
| Error Name | Error Description | 2021-12-05 | 2021-12-19 | |
| decreasing_or_equal_stop_time_distance | Two consecutive stop times in a trip should have increasing distance. If the values are equal, this is considered as an error. | 24 | ||
| empty_file | Empty csv file found in the archive: file does not have any headers, or is a required file and does not have any data. The GTFS specification requires the first line of each file to contain field names and required files must have data. | 3 | ||
| 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 | ||
| route_short_and_long_name_equal | Short and long name should not be identical. | 9 | 10 | |
| same_name_and_description_for_route | The GTFS spec requires that a route_description is distinct from both the route short and long names. | 1 | ||