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|
|Validation errors observed|
|Error Name||Error Description||Severity|
|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.||ERROR|
|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.||WARNING|
|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.||WARNING|
|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).||WARNING|