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-02-06 | 2022-02-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 | 2022-02-06 | 2022-02-20 | |
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. | 9 | 9 | |
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. | 8 | 8 | |
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. | 15416 | 15416 | |
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. | 1 | 1 |