Diagnosis
What this notice means
The trip's final shape_dist_traveled exceeds the shape's maximum distance, and the endpoint separation exceeds the implementation's 11.1 m threshold.
Operational effect
Why it matters
The stop distances and route geometry do not describe the same endpoint reliably.
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
maxTripDistanceTraveled,maxShapeDistanceTraveled, the units, and the reported endpoint separation. - 2
Correct the trip's shape assignment, extend an incomplete shape to the real endpoint, or recompute distances from accurate geometry. Do not just increase the shape's final 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