missing_stop_name: GTFS validation rule (stops.txt) Error
stop_name is empty on a stop where the spec requires it (location_type 0, 1 or 2).
What the rule checks
stop_name is empty on a stop where the spec requires it (location_type 0, 1 or 2).
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 and the rules of GTFS Express itself, lists the occurrences of missing_stop_name 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, missing_stop_name. Its documentation describes each rule: MobilityData validator rules.
Rules of the same domain
- location_without_parent_station
- 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
- stop_without_zone_id
- unused_parent_station
- unused_station
- All the validation rules