stop_access_specified_for_incorrect_location: GTFS validation rule (stops.txt) Error
A station, an entrance, a generic node or a boarding area of stops.txt fills stop_access. The field is for a stop or platform (location_type=0) that belongs to a station.
What the rule checks
A station, an entrance, a generic node or a boarding area of stops.txt fills stop_access. The field is for a stop or platform (location_type=0) that belongs to a station.
Severity: error
An error marks data that breaks the GTFS specification. A journey planner or a rider app may refuse the file, or show a wrong version of it. Correct it before publishing the GTFS.
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, lists the occurrences of stop_access_specified_for_incorrect_location 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
stop_access_specified_for_incorrect_location is the code of the MobilityData GTFS validator, the one its report carries. Its documentation describes the rule: stop_access_specified_for_incorrect_location on the MobilityData site.
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_access_specified_for_stop_with_no_parent_station
- stop_without_location
- stop_without_zone_id
- unused_parent_station
- unused_station
- All the validation rules