Global element
DatedCall
Defined in SIRI/xsd/siri_model/siri_datedVehicleJourney.xsd:448
Transmodel concept DATED CALL
Complete sequence of stops along the route path, in calling order.
Type
Content model
Element structure
-
Elements identifying an ordered visit to a SCHEDULED STOP POINT within a SERVICE PATTERN.
-
Reference to a SCHEDULED STOP POINT.
Reference to a STOP POINT.
-
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially.
-
For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful.
-
Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0)
-
-
-
Whether this DATED CALL is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to false: the journey is not an addition.
-
Whether this DATED CALL is a cancellation of a previously announced call (or planned according to the long-term timetable). Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the journey is not cancelled.
-
-
Elements describing the CALL Properties Values for these elements can be specified on an production VEHICLE JOURNEY CALL. Each real-time journey CALL takes its values from the corresponding dated VEHICLE JOURNEY CALL. The absence of a value on an real-time CALL l indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity.
-
Whether the stop is a TIMING POINT. Times for stops that are not timing points are sometimes interpolated crudely from the timing points, and may represent a lower level of accuracy. Default is 'true'.
-
Whether this is a Hail and Ride Stop. Default is 'false'.
-
Whether Vehicle stops only if requested explicitly by passenger. Default is 'false'.
-
Origin to show for the VEHICLE at the specific stop (vehicle signage), if different to the Origin Name for the full journey. (since SIRI 2.0)
-
Destination to show for the VEHICLE at the specific stop (vehicle signage), if different to the Destination Name for the full journey.
-
-
Text annotation that applies to this call.
-
-
Elements describing the arrival of a VEHICLE at a stop.
-
Target arrival time of VEHICLE at stop according to latest working timetable.
-
Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is: (i) any arrival platform on any related dated timetable element, (ii) any departure platform name on this estimated element; (iii) any departure platform name on any related dated timetable CALL.
-
Type of alighting allowed at stop. Default is 'Alighting'.
-
OPERATORs of of service up until arrival. May change for departure. (since SIRI 2.0).
-
-
Elements describing the departure of a VEHICLE from a stop.
-
Target departure time of VEHICLE from stop according to latest working timetable.
-
Departure QUAY (bay or platform) name. Default taken from planned timetable.
-
Nature of boarding allowed at stop. Default is 'Boarding'.
-
OPERATORs of service for departure and onwards. May change from that for arrival. (since SIRI 2.0).
-
-
Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. (since SIRI 2.0)
-
For frequency based services, target interval between vehicles at stop.
-
-
Information on any planned distributor connections (deprecated from SIRI V2.0 ... see 2 next attributes)
-
Information on any planned feeder connections. SIRI 2.0
-
Information on any planned distributor connections. SIRI 2.0
-
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).