Diagnosis
What this notice means
The distance and elapsed time between consecutive stops imply a speed above the rule's threshold for this transport type.
Operational effect
Why it matters
A wrong stop location or time can produce misleading journey durations.
Scope
Files to check and report fields
routes.txtOpen GTFS specificationstop_times.txtOpen GTFS specificationstops.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 reported stop IDs, coordinates, departure time, arrival time, and
speedKphwith the actual journey. - 2
Correct the mistaken coordinate, stop reference, time, or route type. For travel after midnight, preserve the service-day time, such as
25:10:00. Keep verified unusual services unchanged. - 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 — routes.txtOfficial GTFS documentation
- GTFS Schedule Reference — stop_times.txtOfficial GTFS documentation
- GTFS Schedule Reference — stops.txtOfficial GTFS documentation
- GTFS Schedule Reference — trips.txtOfficial GTFS documentation
- GTFS Scorecard fix guidePlain-language repair steps and checks