Diagnosis
What this notice means
The final stop's cumulative distance exceeds the shape's maximum, but the endpoints are within the implementation's 11.1 m tolerance.
Operational effect
Why it matters
Rounding or inconsistent distance calculations may prevent reliable stop placement.
Scope
Files to check and report fields
shapes.txtOpen GTFS specificationstop_times.txtOpen GTFS specificationtrips.txtOpen GTFS specification
| Report field | Type | Meaning |
|---|---|---|
| This notice has no structured context fields. | ||
Repair
How to fix it
- 1
Compare the maximum distance values, units, and endpoint coordinates in the reported trip and shape.
- 2
Recalculate with a shared distance origin and sufficient precision. Preserve the real geometry rather than shifting coordinates to match a rounded number.
- 3Check the result
After a repair, rebuild the archive and validate it again. Confirm that the affected records are correct and that no new related notices appeared. A reviewed warning or informational notice may remain when it describes intentional, supported data.
Re-check your feed in the browserFree, no upload for a file you pick.
Sources
References
- MobilityData validator ruleCanonical notice metadata and rule details
- GTFS Schedule Reference — shapes.txtOfficial GTFS documentation
- GTFS Schedule Reference — stop_times.txtOfficial GTFS documentation
- GTFS Schedule Reference — trips.txtOfficial GTFS documentation
- Shapes Data GuidanceOfficial GTFS documentation
- GTFS Scorecard fix guidePlain-language repair steps and checks