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-01-02 | 2022-01-16 | 2022-01-30 | |
|---|---|---|---|---|
| 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 | 2022-01-02 | 2022-01-16 | 2022-01-30 |
| block_trips_with_overlapping_stop_times | Trips within the same block have overlapping stop times, which is not allowed. | 1075 | 1075 | 1075 |
| decreasing_or_equal_shape_distance | Two consecutive points in shapes.txt should have increasing values for shape_dist_traveled. If the values are equal, this is considered as an error. | 3431 | 3628 | 3774 |
| 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. | 111 | 111 | 111 |
| 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. | 17 | 17 | 17 |
| foreign_key_violation | The values of the given key and rows of one table cannot be found with values of the given key in another table. | 2 | ||
| route_short_and_long_name_equal | Short and long name should not be identical. | 7 | 7 | 7 |
| 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. | 13 | 13 | 13 |
| stop_time_timepoint_without_times | Any record with stop_times.timepoint set to 1 should define a value for stop_times.arrival_time and stop_times.departure_time fields. | 194 | 194 | 132 |
| stop_too_far_from_trip_shape | Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. | 39 | 51 | 55 |
| 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). | 798 | 1239 | 786 |