Fix stops_match_shape_out_of_order in GTFS

Diagnosis

What this notice means

Stops appear in one order in stop_times.txt but match the shape in another order.

Operational effect

Map and journey information may follow the wrong direction or wrong pass through a loop.

Scope

Report field	Type	Meaning
`match1`	array<number, 2>	Latitude and longitude pair of the first matching location.
`match2`	array<number, 2>	Latitude and longitude pair of the second matching location.
`shapeId`	string	The id of the shape that is referred to.
`stopId1`	string	The id of the first stop that is referred to.
`stopId2`	string	The id of the second stop that is referred to.
`stopName1`	string	The name of the first stop that is referred to.
`stopName2`	string	The name of the second stop that is referred to.
`stopTimeCsvRowNumber1`	integer	The row number of the first faulty record from `stop_times.txt`.
`stopTimeCsvRowNumber2`	integer	The row number of the second 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

1
Compare the two reported stops, trip stop_sequence, shape direction, and any distance values.
2
Correct the wrong stop order or shape assignment. For loops, use cumulative distances to distinguish repeated visits without reordering a correct timetable.
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.

Sources