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-05-01||2022-05-15||2022-05-29|
|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|
|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.||ERROR|
|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|
|same_name_and_description_for_route||The GTFS spec requires that a route_description is distinct from both the route short and long names.||ERROR|