stop_without_zone_id: GTFS validation rule (stops.txt) Info
A platform (location_type=0 or empty) has no zone_id. Recommended for feeds that use fare zoning.
What the rule checks
A platform (location_type=0 or empty) has no zone_id. Recommended for feeds that use fare zoning.
Severity: information
An information notice marks a feature of the GTFS that does not affect its conformity. It helps to understand the data and asks for no correction.
Where it applies
The rule applies to stops.txt. This file describes the stops, stations, their entrances and platforms, with their coordinates.
Finding and correcting it
Open the GTFS in GTFS Express. Reading is free, and the validation, by the MobilityData validator and the rules of GTFS Express itself, lists the occurrences of stop_without_zone_id with the file and rows involved. The correction is made in a draft, by hand or from a brief, with the licence: the corrected GTFS is validated again before it is delivered, and the change can be undone.
In the MobilityData validator
The MobilityData GTFS validator uses the same code, stop_without_zone_id. Its documentation describes each rule: MobilityData validator rules.
Rules of the same domain
- location_without_parent_station
- missing_stop_name
- platform_without_parent_station
- same_name_and_description_for_stop
- same_stop_and_agency_url
- same_stop_and_route_url
- station_with_parent_station
- stop_lat_out_of_range
- stop_lon_out_of_range
- stop_without_location
- unused_parent_station
- unused_station
- All the validation rules