Complex type
TargetedVehicleJourneyStructure
Defined in SIRI/xsd/siri_model/siri_targetedVehicleJourney.xsd:95
Type for a targeted VEHICLE JOURNEY.
Used by elements
Content model
Type structure
-
Elements identifying VEHICLE JOURNEY.
-
Reference to a LINE.
-
Reference to a DIRECTION, typically outward or return.
-
A reference to the dated VEHICLE JOURNEY that the VEHICLE is making.
-
-
Elements describing the LINE, ROUTE and DIRECTION of a VEHICLE JOURNEYwhich are derived from the JOURNEY PATTERN associated with the journey. Values for these elements can be specified on an annual 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.
-
Identifier of JOURNEY PATTERN that journey follows.
-
Name of Joruney Pattern
-
A means of transportation such as bus, rail, etc.
-
Identifier of ROUTE that journey follows.
-
Name or Number by which the LINE is known to the public. (Unbounded since SIRI 2.0)
-
Reference to a GROUP OF LINEs to which journey belongs. SIRI 2.0
-
Description of the DIRECTION. May correspond to a DESTINATION DISPLAY. (Unbounded since SIRI 2.0)
-
Alternative identifier of LINE that an external system may associate with journey.
-
-
Reference to a BRANDING. (since SIRI 2.1)
-
An arbitrary marketing classification. (since SIRI 2.1)
-
-
-
Common information about a VEHICLE JOURNEY. (Similar to VDV TripInfo)
-
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.
-
-
End names for journey.
-
Reference to the origin SCHEDULED STOP POINT of the journey.
-
Name of the origin of the journey. (Unbounded since SIRI 2.0)
-
Short name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as Origin Name.
-
DIRECTION name shown for jurney at the origin. (since SIRI 2.0)
-
Reference to a DESTINATION.
-
Description of the destination stop (vehicle signage), Can be overwritten for a journey, and then also section by section by the entry in an individual CALl. (Unbounded since SIRI 2.0)
-
Short name of the DESTINATION.of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as DestinationName. (Unbounded since SIRI 2.0)
-
Origin name shown for jourey at the destination (since SIRI 2.0)
-
-
Elements describing a VEHICLE JOURNEY. Values for these elements can be specified on an annual schedule and will be inherited, unless overriden, onto the production timetable and then onto the individul DATED VEHICLE JOURNEYs of the timetable. Each real-time journey (e.g. ESTIMATED VEHICLE JOURNEY or MONITORED VEHICLE JORUNEY) 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.
-
For train services with named journeys. Train name, e.g. “West Coast Express”. If omitted: No train name. Inherited property. (Unbounded since SIRI 2.0)
-
Additional descriptive text associated with journey. Inherited property.
-
Contact details for use by members of public. (since SIRI 2.0)
-
Contact details for use by operational staff. (since SIRI 2.0)
-
Allows to flag if the VehicleJourney is a dead run. It helps notify to passenger information systems, especially if they do not leverage dead runs and/or have a different process for them. +v2.3
-
-
Call times for journey.
-
Whether this is a Headway Service, that is shown as operating at a prescribed interval rather than to a fixed timetable. Default is 'false'.
-
Timetabled departure time from Origin.
-
Timetabled arrival time at Destination.
-
Whether journey is first or last journey of day. (since SIRI 2.0)
-
-
-
Information about the call at the stop.