Diagnosis
What this notice means
trip_headsign matches a stop before the trip's last stop.
Operational effect
Why it matters
Passengers boarding later may see a destination the vehicle has already passed.
Scope
Files to check and report fields
stop_times.txtOpen GTFS specificationstops.txtOpen GTFS specificationtrips.txtOpen GTFS specification
| Report field | Type | Meaning |
|---|---|---|
csvRowNumber | integer | The row number of the faulty record in `trips.txt`. |
stopId1 | string | The id of the intermediate stop whose name matches the headsign. |
stopId2 | string | The id of the actual last stop of the trip. |
stopSequence | integer | The stop_sequence value of the intermediate stop that matches the headsign. |
tripHeadsign | object | The headsign value that matches an intermediate stop name. |
tripId | string | The id of the trip with the problematic headsign. |
Repair
How to fix it
- 1
Compare the headsign with the actual vehicle display and the complete stop sequence.
- 2
Correct a mistaken trip headsign. If the display legitimately changes during the trip, represent the changes with appropriate
stop_headsignvalues; do not assume every headsign must equal the final stop name. - 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