same_stop_and_agency_url: GTFS validation rule (stops.txt) Warning
A stop's stop_url equals an agency's agency_url. Likely a default-fill bug.
What the rule checks
A stop's stop_url equals an agency's agency_url. Likely a default-fill bug.
Severity: warning
A warning marks data the specification allows but that looks doubtful, or recommended information that is missing. The GTFS can still be published, but riders may see the effect, so each case deserves a look.
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 same_stop_and_agency_url 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, same_stop_and_agency_url. 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_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