RemovedServiceJourneyInterchangeStructure

Reference to a SERVICE JOURNEY INTERCHANGE.

Reference to a CONNECTION link

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)

Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).