point_near_pole: GTFS validation rule (data quality) Error
A stop or shape point sits within 1° of either geographic pole (|lat| > 89.0°): almost certainly a coordinate-entry typo.
What the rule checks
A stop or shape point sits within 1° of either geographic pole (|lat| > 89.0°): almost certainly a coordinate-entry typo.
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 measures the quality of the data rather than strict conformity: it points at values that are allowed but unlikely.
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 point_near_pole 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, point_near_pole. Its documentation describes each rule: MobilityData validator rules.
Rules of the same domain
- feed_expiration_date_30_days
- feed_expiration_date_7_days
- feed_expired
- missing_recommended_field
- mixed_case_recommended_field
- non_ascii_or_non_printable_char
- point_near_origin
- route_without_trips
- start_and_end_range_equal
- stop_time_travel_distance_too_long
- stop_time_travel_speed_too_fast
- All the validation rules