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-12-05||2021-12-19|
|Validation errors observed||Number of errors|
|Error Name||Error Description||2021-12-05||2021-12-19|
|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||66|
|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.||2||2|
|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|
|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.||3||3|