Global element
RecordedCall
Defined in OpRa/SIRI/xsd/siri_model/siri_estimatedVehicleJourney.xsd:416
Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY. Only used if observed stop data is being recorded. (SIRI 2.0)
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)
-
-
-
Information relating to real-time properties of call.
-
Whether the prediction for a specific stop or the whole journey is considered to be of a useful accuracy or not. Default is 'false', i.e. prediction is considered to be accurate. If prediction is degraded, e.g. because of a situation, PredictionInaccurate is used to indicate a lowered quality of data. Inherited property. PredictionInaccurate can be used in combination with InCongestion, but is more general.
-
Can be used to inform the passenger about the reason for a change of the prediction (in)accuracy in case PredictionInaccurate is set to 'true'. (since SIRI 2.1)
-
An approximate figure of how occupied the journey is after departing from a given stop, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. If omitted: Passenger load is unknown. Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRAIN, can also be specified in more detail for the departure on CALL level.
-
-
Information relating to recorded real-time properties of call.
-
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.
-
-
Annotations of the CALL.
-
Text annotation that applies to this CALL.
-
-
Elements describing nature of disruption.
-
Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. (since SIRI 2.1)
-
Information about a change of Equipment availability at stop or on vehicle that may affect access or use.
-
This sequence is here only for compatibility reasons between Siri 1.0 and Siri 1.1
-
Reference to a ControlAction having possible consequences on the EstimatedVehicleJourney. Note that if the ControlAction is the master ControlAction of a GroupOfControlActions it is assumed that the refence is valid for all the ControlActions of the group.
-
-
Target arrival time of VEHICLE at stop according to latest working timetable.
-
Estimated time of arriival of VEHICLE at stop .
-
Observed time of arrival of VEHICLE at stop.
-
Elements describing the arrival status of a VEHICLE at a stop.
-
Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus.
-
Text annotation to be used in cases where ArrivalStatus is set to 'cancelled'. (since SIRI 2.1)
-
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'.
-
Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1) Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving at sector A first when approaching the QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving at this reference point first when approaching the QUAY. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). It is advised to specify a reference point that is meaningful for passengers on location.
-
OPERATORs of of service up until arrival. May change for departure. (since SIRI 2.0).
-
-
Target departure time of VEHICLE from stop according to latest working timetable.
-
Estimated time of departure of VEHICLE from stop, most likely taking into account all control actions such as waiting.
-
Departure QUAY (bay or platform) name. Default taken from planned timetable.
-
Observed time of departure of VEHICLE from stop.
-
Classification of the timeliness of the departure part of the CALL, according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times.
-
Text annotation to be used in cases where DepartureStatus is set to 'cancelled'. (since SIRI 2.1)
-
Arbitrary text string to show to indicate the status of the departure of the vehicle, for example, “Boarding”, “GatesClosed”. (since SIRI 2.0)
-
Nature of boarding allowed at stop. Default is 'Boarding'.
-
Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1) Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle departing in the direction of this reference point. If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). It is advised to specify a reference point that is meaningful for passengers on location.
-
Actually recorded/counted occupancies of a VEHICLE and reserved seats after departing from a given stop. (since SIRI 2.1)
-
Actually recorded/counted capacities of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1)
-
OPERATORs of service for departure and onwards. May change from that for arrival. (since SIRI 2.0).
-
Elements describing the HEADWAY INTERVALs.
-
For frequency based services, target interval between vehicles at stop.
-
For frequency based services, expected interval between vehicles at stop.
-
-
For frequency based services, observed interval between vehicles at stop.
-
-
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).