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-10-03||2021-10-17||2021-10-31|
|Validation errors observed||Number of errors|
|Error Name||Error Description||2021-10-03||2021-10-17||2021-10-31|
|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.||18038||18038||18038|
|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.||2||2||2|
|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).||90||90||90|