This interface is used to represent a point or location where a transfer start from or end.
There are 4 different Transfer points:
This is the least specific type, and is overridden if a more specific type exist.
The specificity-ranking is above StationTransferPoints and less than RouteStationTransferPoint.
The specificity-ranking is above StopTransferPoints and less than RouteStopTransferPoint.
The specificity-ranking is above RouteStationTransferPoints and less than TripTransferPoint.
stopPositionInPattern instead. There is two
reasons for this. In NeTEx the an interchange is from a trip and stop-point, so this model
fits better with NeTEx. The second reason is that real-time updates could invalidate the
trip-transfer-point, since the stop could change to another platform(common for railway
stations). To account for this the RT-update would need to patch the trip-transfer-point.
We simplify the RT-updates by converting the stop to a stop-position-in-pattern.
This is the most specific point type.
| name | data type | constraints | description |
|---|---|---|---|
| stopTransferPoint | boolean | required | is a Stop specific transfer point (no Trip or Route) |
| tripTransferPoint | boolean | required | is a Trip specific transfer point |
| routeStopTransferPoint | boolean | required | is a Route specific transfer point |
| routeStationTransferPoint | boolean | required | is a Route specific transfer point |
| stationTransferPoint | boolean | required | is a Station specific transfer point (no Trip or Route) |
| specificityRanking | number | required | Specificity of a transfer |
Example
{
"stopTransferPoint" : true,
"tripTransferPoint" : true,
"routeStopTransferPoint" : true,
"routeStationTransferPoint" : true,
"stationTransferPoint" : true,
"specificityRanking" : 12345
}