A constrained transfer is a transfer which is restricted in one ore more ways by the transit data provider. It can be guaranteed or stay-seated, have a priority (NOT_ALLOWED, ALLOWED, RECOMMENDED, PREFERRED) or some sort of time constraint attached to it. It is applied to a transfer from a transfer-point to another point. A transfer point is a combination of stop and route/trip.
name | data type | constraints | description |
---|---|---|---|
id | FeedScopedId | In NeTEx an interchange have an id, in GTFS a transfer do not. We include it here to enable debugging, logging and system integration. Note! OTP do not use this id, and it is just passed through OTP. There is no service in OTP to look up a transfer by its id. | |
from | TransferPoint | ||
to | TransferPoint | ||
transferConstraint | TransferConstraint | The transfer constraint used for the transfer. | |
specificityRanking | number | required |
Specificity of a transfer
The ranking implemented here is slightly modified:
|
Example
{ "id" : { "feedId" : "...", "id" : "..." }, "from" : { "stopTransferPoint" : true, "tripTransferPoint" : true, "routeStopTransferPoint" : true, "routeStationTransferPoint" : true, "stationTransferPoint" : true, "specificityRanking" : 12345 }, "to" : { "stopTransferPoint" : true, "tripTransferPoint" : true, "routeStopTransferPoint" : true, "routeStationTransferPoint" : true, "stationTransferPoint" : true, "specificityRanking" : 12345 }, "transferConstraint" : { "priority" : "ALLOWED", "staySeated" : true, "guaranteed" : true, "facilitated" : true, "notAllowed" : true, "regularTransfer" : true, "maxWaitTime" : 12345, "minTransferTime" : 12345, "minTransferTimeSet" : true }, "specificityRanking" : 12345 }