Fix: a stop sits far from the route line
Published: . Last reviewed: .
Code: stop_too_far_from_shape (MobilityData validator)
What this means
Some stops sit far from the route line (the shapes.txt path) they belong
to, based on the geometric distance between the stop and the shape.
Why it matters
Trip planners use the shape to draw the route on the map. When a stop sits far from it, the map can draw the bus detouring to reach the stop, or point riders to the wrong corner to wait.
How to fix it
Check the flagged stops' coordinates and the route shape in your scheduling software, then re-snap whichever one is misplaced:
- If the stop's location is wrong, correct
stop_lat/stop_lonto where the stop actually is. - If the shape doesn't actually pass the stop, fix or re-generate
shapes.txtso it follows the real path the bus drives.
See a stop far from the shape by its distance measurement
for the related case where shape_dist_traveled values, not the raw
geometry, are what disagree with the stop's location.
How long it usually takes
A few minutes per flagged stop, checking the coordinates against the map.
Authoritative rule
stop_too_far_from_shape is a canonical MobilityData GTFS Validator notice used in validator reports across the GTFS ecosystem. Read the authoritative rule for stop_too_far_from_shape in the GTFS Validator rules. (opens on an external site)
After you republish
Once the changed feed is live at your published URL, the next scorecard run checks it again. When the same complete producer contract no longer reports this finding, it can be recorded as a dated finding clearance. That confirms the later feed state, not who changed the feed or why.