TripTransferPoint Data Type

This interface is used to represent a point or location where a transfer start from or end.

There are 4 different Transfer points:

  1. StopTransferPoint This apply to all trip stopping at the given stop.

    This is the least specific type, and is overridden if a more specific type exist.

  2. StationTransferPoint This applies to all trips stopping at a stop part of the given station.

    The specificity-ranking is above StationTransferPoints and less than RouteStationTransferPoint.

  3. A RouteStationTransferPoint is a from/to point for a Route at the given stop. This only exists in GTFS, not in the Nordic NeTex profile.

    The specificity-ranking is above StopTransferPoints and less than RouteStopTransferPoint.

  4. A RouteStopTransferPoint is a from/to point for a Route at the given station. This only exists in GTFS, not in the Nordic NeTex profile.

    The specificity-ranking is above RouteStationTransferPoints and less than TripTransferPoint.

  5. TripTransferPoint A transfer from/to a Trip at the given stop position(not stop). The GTFS Transfers may specify a transfer from/to a trip and stop/station. But in OTP we map the stop to a stop position in pattern. The OTP model TripTransferPoint does NOT reference the stop/station, but the 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.

Implemented Interfaces
Serializable, TransferPoint
Properties
name data type constraints description
trip Trip  
stopPositionInPattern number required
specificityRanking number required Specificity of a transfer
tripTransferPoint boolean required is a Trip specific transfer point

Example

{
  "trip" : {
    "operator" : {
      "name" : "...",
      "url" : "...",
      "phone" : "...",
      "id" : { }
    },
    "tripOperator" : {
      "name" : "...",
      "url" : "...",
      "phone" : "...",
      "id" : { }
    },
    "route" : {
      "branding" : { },
      "agency" : { },
      "operator" : { },
      "shortName" : "...",
      "longName" : "...",
      "desc" : "...",
      "gtfsType" : 12345,
      "mode" : "TRAM",
      "url" : "...",
      "color" : "...",
      "textColor" : "...",
      "bikesAllowed" : "NOT_ALLOWED",
      "sortOrderSet" : true,
      "sortOrder" : 12345,
      "flexibleLineType" : "...",
      "name" : "...",
      "netexSubmode" : "...",
      "id" : { }
    },
    "serviceId" : {
      "feedId" : "...",
      "id" : "..."
    },
    "mode" : "BUS",
    "netexSubmode" : "...",
    "tripShortName" : "...",
    "internalPlanningCode" : "...",
    "tripHeadsign" : "...",
    "routeShortName" : "...",
    "direction" : "UNKNOWN",
    "blockId" : "...",
    "shapeId" : {
      "feedId" : "...",
      "id" : "..."
    },
    "wheelchairAccessible" : 12345,
    "bikesAllowed" : "NOT_ALLOWED",
    "fareId" : "...",
    "tripAlteration" : "CANCELLATION",
    "id" : {
      "feedId" : "...",
      "id" : "..."
    }
  },
  "stopPositionInPattern" : 12345,
  "specificityRanking" : 12345,
  "tripTransferPoint" : true
}