Diagnosis
What this notice means
The same stop location has many possible matches along the trip's shape.
Operational effect
Why it matters
Apps may place the stop on the wrong pass of a loop or overlapping route section.
Scope
Files to check and report fields
stop_times.txtOpen GTFS specificationstops.txtOpen GTFS specificationtrips.txtOpen GTFS specification
| Report field | Type | Meaning |
|---|---|---|
match | array<number, 2> | Latitude and longitude pair of the location. |
matchCount | integer | The number of matches for the stop that is referred to. |
shapeId | string | The id of the shape that is referred to. |
stopId | string | The id of the stop that is referred to. |
stopName | string | The name of the stop that is referred to. |
stopTimeCsvRowNumber | integer | The row number of the faulty record from `stop_times.txt`. |
tripCsvRowNumber | integer | The row number of the faulty record from `trips.txt`. |
tripId | string | The id of the trip that is referred to. |
Repair
How to fix it
- 1
Inspect the reported stop, shape, and trip direction on a map.
- 2
Correct inaccurate coordinates or a wrong shape assignment. For a genuine repeated pass, supply consistent cumulative
shape_dist_traveledvalues that identify the intended occurrence. - 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 — stop_times.txtOfficial GTFS documentation
- GTFS Schedule Reference — stops.txtOfficial GTFS documentation
- GTFS Schedule Reference — trips.txtOfficial GTFS documentation
- Shapes Data GuidanceOfficial GTFS documentation