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.||9233||18677||9205|
|duplicate_fare_rule_zone_id_fields||Each of the following fields should be unique in fare_rules.txt: fare_rules.route_id, fare_rules.origin_id, fare_rules.contains_id and fare_rules.destination_id||293||293||293|
|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.||1||1||1|
|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||4||2|