GTFS.guru
Home/Notice codes/transfer_with_suspicious_mid_trip_in_seat
WARNINGGTFS Schedule notice

A stay-on-board transfer occurs in the middle of a trip

transfer_with_suspicious_mid_trip_in_seat
Severity
WARNING
Files to check
3
Report fields
5
Documentation
Curated

Diagnosis

What this notice means

An in-seat transfer uses a stop that is not at the expected end of the arriving trip or start of the departing trip.

Operational effect

Why it matters

The connection may be misunderstood by consumers with limited support for mid-trip transfers.

Scope

Files to check and report fields

Report fieldTypeMeaning
csvRowNumberintegerThe row number from `transfers.txt` for the faulty entry.
stopIdstringThe referenced stop id.
stopIdFieldNamestringThe name of the stop id field (e.g. `from_stop_id`) referencing the stop.
tripIdstringThe referenced trip id.
tripIdFieldNamestringThe name of the trip id field (e.g. `from_trip_id`) referencing a trip.

Repair

How to fix it

  1. 1

    Compare both trips in stop_sequence order and confirm where passengers actually remain on board.

  2. 2

    Correct a mistaken trip or stop reference. If the mid-trip transfer is intentional, retain it after checking support in the target apps.

  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