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-09-05|
|Validation errors observed||Number of errors|
|Error Name||Error Description||2021-09-05||2021-09-19|
|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.||177||209|
|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||25||23|
|feed_expiration_date||At any time, the published GTFS dataset should be valid for at least the next 7 days, and ideally for as long as the operator is confident that the schedule will continue to be operated. If possible, the GTFS dataset should cover at least the next 30 days of service.||1|
|invalid_row_length||A row in the input file has a different number of values than specified by the CSV header.||3|