Fix stop_time_with_arrival_before_previous_departure_time in GTFS

Diagnosis

What this notice means

For one trip, a stop's arrival_time is earlier than the previous stop's departure_time.

Operational effect

The trip appears to travel backwards in time, which can break journey planning.

Scope

Report field	Type	Meaning
`arrivalTime`	object	Arrival time at the faulty record.
`csvRowNumber`	integer	The row number of the faulty record.
`departureTime`	object	Departure time at the previous stop time.
`prevCsvRowNumber`	integer	The row of the previous stop time.
`tripId`	string	The trip_id associated to the faulty record.

Repair

1
Compare the two reported stop-time rows in stop_sequence order.
2
Correct the wrong time or stop order. If the trip crosses midnight, represent next-day service-day times with hours above 24, for example 24:15:00 instead of 00:15:00.
3
Check 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.

Worked example

Assume the trip starts before midnight and reaches the next stop 20 minutes after midnight in the same service day.

previous departure_time: 23:55:00
next arrival_time: 00:20:00

previous departure_time: 23:55:00
next arrival_time: 24:20:00

Illustrative excerpt, not a complete GTFS feed. Keep all other required records and fields.

Sources