Diagnosis
What this notice means
The stop is used by a route with zone-dependent legacy fare rules, but its zone_id is empty.
Operational effect
Why it matters
Apps may be unable to determine the applicable fare.
Scope
Files to check and report fields
stops.txtOpen GTFS specificationstop_times.txtOpen GTFS specificationtrips.txtOpen GTFS specificationroutes.txtOpen GTFS specificationfare_rules.txtOpen GTFS specification
| Report field | Type | Meaning |
|---|---|---|
csvRowNumber | integer | The row number of the faulty record. |
stopId | string | The faulty record's id. |
stopName | string | The faulty record's `stops.stop_name`. |
Repair
How to fix it
- 1
Trace the stop's trips and routes to the relevant
fare_rules.txtrows. - 2
Assign its actual fare zone in
stops.txt, consistent with the fare rules. Do not assign every stop to one zone merely to fill the field. - 3Check the result
After a repair, rebuild the archive and validate it again. Confirm that the affected records are correct and that no new related notices appeared. A reviewed warning or informational notice may remain when it describes intentional, supported data.
Re-check your feed in the browserFree, no upload for a file you pick.
Sources
References
- MobilityData validator ruleCanonical notice metadata and rule details
- GTFS Schedule Reference — fare_rules.txtOfficial GTFS documentation
- GTFS Schedule Reference — routes.txtOfficial GTFS documentation
- GTFS Schedule Reference — stop_times.txtOfficial GTFS documentation
- GTFS Schedule Reference — stops.txtOfficial GTFS documentation
- GTFS Schedule Reference — trips.txtOfficial GTFS documentation