INFOGTFS Schedule notice

Stop-time rows are not grouped and ordered by trip

unsorted_stop_times
Severity
INFO
Files to check
1
Report fields
3
Documentation
Curated

Diagnosis

What this notice means

Rows for a trip are not contiguous or do not appear in stop_sequence order.

Operational effect

Why it matters

Some tools process grouped, ordered records more efficiently; the notice does not mean the service sequence itself is necessarily wrong.

Scope

Files to check and report fields

Report fieldTypeMeaning
endCsvRowNumberintegerCSV row number of the last stop_times entry for this trip.
startCsvRowNumberintegerCSV row number of the first stop_times entry for this trip.
tripIdstringThe faulty record's trip_id.

Repair

How to fix it

  1. 1

    Check whether the data is correct when grouped by trip_id and sorted numerically by stop_sequence.

  2. 2

    Export in that order while keeping each row's values unchanged. Do not renumber a correct sequence merely to match an accidental file order.

  3. 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

References