Complex type abstract
AbstractServiceJourneyInterchangeStructure
Defined in SIRI/xsd/siri_model/siri_datedVehicleJourney.xsd:248
A planned SERVICE JOURNEY INTERCHANGE between two journeys. (since SIRI 2.0)
Derived types
Content model
Type structure
-
-
Identifier of SERVICE JOURNEY INTERCHANGE. (since SIRI 2.0)
-
Reference to a SERVICE JOURNEY INTERCHANGE.
-
-
Reference to a CONNECTION link
-
-
Whether this interchange is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not an addition. (since SIRI 2.1)
-
-
The data producer must provide a reason, e.g. type of error and description, in case he wants to silently remove (instead of cancel) a journey or an interchange from the plan. (since SIRI 2.1)
-
Reference to a feeder VEHICLE JOURNEY. (since SIRI 2.0)
-
SCHEDULED STOP POINT at which feeder journey arrives. (since SIRI 2.0)
-
Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN.
-
For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1)
-
Planned time at which feeder VEHICLE is scheduled to arrive. (since SIRI 2.1)
-
Reference to a feeder VEHICLE JOURNEY. (since SIRI 2.0)
-
SCHEDULED STOP POINT at which distributor journet departs. (since SIRI 2.0)
-
Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN.
-
For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1)
-
Planned time at which distributor VEHICLE is scheduled to depart. (since SIRI 2.1)
-
Properties of SERVICE JOURNEY INTERCHANGE.
-
Whether the passenger can remain in VEHICLE (i.e. BLOCKlinking). Default is 'false': the passenger must change vehicles for this connection.
-
Whether the SERVICE JOURNEY INTERCHANGE is guaranteed. Default is 'false'; SERVICE JOURNEY INTERCHANGE is not guaranteed.
-
Whether the SERVICE JOURNEY INTERCHANGE is advertised as a connection. Default is 'false'.
-
-
Time Elements for SERVICE JOURNEY INTERCHANGE.
-
Elements for INTERCHANGE WAIT TIME.
-
Standard wait time for INTERCHANGE. SIRI v2,0
-
Maximum time that Distributor will wait for Feeder for INTERCHANGE. SIRI v1.0
-
Maximum automatic wait time that Distributor will wait for Feeder for INTERCHANGE. (since SIRI 2.0)
-
-
Elements for INTERCHANGE TRANSFER duration.
-
Standard transfer duration for INTERCHANGE. SIRI v2,0
-
Minimum transfer duration for INTERCHANGE. SIRI v2,0
-
Maximum transfer duration for INTERCHANGE. SIRI v2,0
-
-
-
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).