transfer_with_suspicious_mid_trip_in_seat: GTFS validation rule (transfers.txt) Warning
transfer_type=4 (in-seat continuation) between two trips without a shared block_id: likely modelling error.
What the rule checks
transfer_type=4 (in-seat continuation) between two trips without a shared block_id: likely modelling error.
Severity: warning
A warning marks data the specification allows but that looks doubtful, or recommended information that is missing. The GTFS can still be published, but riders may see the effect, so each case deserves a look.
Where it applies
The rule applies to transfers.txt. This file describes the transfers between stops, routes or trips.
Finding and correcting it
Open the GTFS in GTFS Express. Reading is free, and the validation, by the MobilityData validator and the rules of GTFS Express itself, lists the occurrences of transfer_with_suspicious_mid_trip_in_seat with the file and rows involved. The correction is made in a draft, by hand or from a brief, with the licence: the corrected GTFS is validated again before it is delivered, and the change can be undone.
In the MobilityData validator
The MobilityData GTFS validator uses the same code, transfer_with_suspicious_mid_trip_in_seat. Its documentation describes each rule: MobilityData validator rules.