Complex type
TargetedCallStructure
Defined in SIRI/xsd/siri_model/siri_targetedVehicleJourney.xsd:129
Type for a targeted call.
Used by elements
Content model
Type structure
-
Elements for a targeted call.
-
Reference to a SCHEDULED STOP POINT. Normally this will omitted as will be the same as the monitoring 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.
-
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'.
-
Elements classifying the Service or journey. Values for these elements can be specified on a timetabled schedule and will be inherited, unless overriden, onto the production timetable and then onto the individul dated VEHICLE JOURNEYs of the timetable. Each monitored journey takes its values from the dated VEHICLE JOURNEY that it follows. The absence of a value on an entity at a given level 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.
-
Information that classifies journey.
-
OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh.
-
Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl.
-
Classification of service into arbitrary Service categories, e.g. school bus. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package. Corresponds to NeTEX TYPE OF SERVICe.
-
-
Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package.
-
-
-
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.
-
-