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|
|Cal-ITP validation errors observed||Number of errors|
|Error Name||Error Description||2022-01-02||2022-01-16||2022-01-30|
|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.||40||40||40|
|route_short_and_long_name_equal||Short and long name should not be identical.||17||17||17|
|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.||4||4||4|
|same_name_and_description_for_route||The GTFS spec requires that a route_description is distinct from both the route short and long names.||34||34||34|