unused_station: GTFS validation rule (stops.txt) Info
A station (location_type=1) is not referenced as parent_station by any platform/stop. Stations exist purely to group child stops.
What the rule checks
A station (location_type=1) is not referenced as parent_station by any platform/stop. Stations exist purely to group child stops.
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 unused_station 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, unused_station. 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
- stop_without_zone_id
- unused_parent_station
- All the validation rules