Block transfer, also called in-seat transfer, is available when a set of trips meets the following conditions:
- The trips are consecutive.
- The same vehicle operates both trips.
- The trips are provisioned with the same
block_idvalue in the trips.txt file in the transit feed.
block_id to enable block transfers¶
Block transfers can be made between consecutive trips on different routes or on the same route if the route is a loop line. Use the
block_id field to specify which trips are in one block and where in-seat transfers are an available option.
In this example:
- A user who searches for a route from stop A to stop E is directed to embark at stop A at 12:00 on Route A and to stay on the vehicle when it reaches stop C after the end of
RouteATrip1. This is because the same vehicle services
RouteBTrip1for Route B.
- Passengers on
RouteATrip1who want to continue on to a stop on
RouteBTrip1can stay on the vehicle for this transfer.
- Passengers of other trips on other vehicles along these same routes don't have this option because they use different vehicles for each trip.
Block transfer in a loop line¶
In a loop line, the first stop and the last stop of a trip are the same and have the same
stop_id. Provided that consecutive loop trips have the same
block_id, block or in-seat transfer is enabled, which lets passengers of the first trip remain on the vehicle when it continues on the next loop.