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-09-05 | |||
|---|---|---|---|---|
| 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-09-05 | 2021-09-19 | |
| block_trips_with_overlapping_stop_times | Trips within the same block have overlapping stop times, which is not allowed. | 6 | 6 | |
| 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. | 97 | 97 | |
| duplicate_key | The values of the given key and rows are duplicates. | 52 | 52 | |
| same_name_and_description_for_route | The GTFS spec requires that a route_description is distinct from both the route short and long names. | 3 | 3 | |
| stop_time_with_arrival_before_previous_departure_time | The departure_time must not precede the arrival_time in stop_times.txt if both are given. | 48 | 48 | |