Global element

DatedVehicleJourney

Defined in OpRa/SIRI/xsd/siri_model/siri_datedVehicleJourney.xsd:100

Transmodel concept DATED VEHICLE JOURNEY

A planned VEHICLE JOURNEY taking place on a particular date.

Type

DatedVehicleJourneyStructure

Content model

Element structure

12 top-level

DatedVehicleJourneyCode 0..1 DatedVehicleJourneyCodeType

Identifier for a VEHICLE JOURNEY.
groupTimetableAlterationGroup 0..1

If the journey is an alteration to a timetable, indicates the original journey, and the nature of the difference.
- choice 0..1
  
  Use of simple reference is deprecated
  - FramedVehicleJourneyRef 1..1 FramedVehicleJourneyRefStructure
    
    Refecence to a VEHICLE JOURNEY framed by the day. SIRI 2.0
  - VehicleJourneyRef 1..1 VehicleJourneyRefStructure
    
    Reference to a VEHICLE JOURNEY.
- choice 1..1
  - ExtraJourney 0..1 xsd:booleandefault false
    
    Whether this journey 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.
  - Cancellation 0..1 xsd:booleandefault false
    
    Whether this journey is a cancellation of a journey in the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the journey is not cancelled.
groupJourneyPatternInfoGroup 1..1

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.
- JourneyPatternRef 0..1 JourneyPatternRefStructure
  
  Identifier of JOURNEY PATTERN that journey follows.
- JourneyPatternName 0..1 NaturalLanguageStringStructure
  
  Name of Joruney Pattern
- VehicleMode 0..unbounded VehicleModesEnumeration
  
  A means of transportation such as bus, rail, etc.
- RouteRef 0..1 RouteRefStructure
  
  Identifier of ROUTE that journey follows.
- PublishedLineName 0..unbounded NaturalLanguageStringStructure
  
  Name or Number by which the LINE is known to the public. (Unbounded since SIRI 2.0)
- GroupOfLinesRef 0..1 GroupOfLinesRefStructure
  
  Reference to a GROUP OF LINEs to which journey belongs. SIRI 2.0
- DirectionName 0..unbounded NaturalLanguageStringStructure
  
  Description of the DIRECTION. May correspond to a DESTINATION DISPLAY. (Unbounded since SIRI 2.0)
- ExternalLineRef 0..1 LineRefStructure
  
  Alternative identifier of LINE that an external system may associate with journey.
- choice 1..1
  - BrandingRef 0..1 BrandingRefStructure
    
    Reference to a BRANDING. (since SIRI 2.1)
  - Branding 0..1 BrandingStructure
    
    An arbitrary marketing classification. (since SIRI 2.1)
groupJourneyEndNamesGroup 1..1

End names for journey.
- OriginRef 0..1 JourneyPlaceRefStructure
  
  Reference to the origin SCHEDULED STOP POINT of the journey.
- OriginName 0..unbounded NaturalLanguagePlaceNameStructure
  
  Name of the origin of the journey. (Unbounded since SIRI 2.0)
- OriginShortName 0..unbounded NaturalLanguagePlaceNameStructure
  
  Short name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as Origin Name.
- DestinationDisplayAtOrigin 0..unbounded NaturalLanguagePlaceNameStructure
  
  DIRECTION name shown for jurney at the origin. (since SIRI 2.0)
- Via 0..unbounded ViaNameStructure
  
  Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested.
- DestinationRef 0..1 DestinationRefStructure
  
  Reference to a DESTINATION.
- DestinationName 0..unbounded NaturalLanguageStringStructure
  
  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)
- DestinationShortName 0..unbounded NaturalLanguagePlaceNameStructure
  
  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)
- OriginDisplayAtDestination 0..unbounded NaturalLanguagePlaceNameStructure
  
  Origin name shown for jourey at the destination (since SIRI 2.0)
groupServiceInfoGroup 1..1

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.
- groupBasicServiceInfoGroup 1..1
  
  Information that classifies journey.
  - OperatorRef 0..1 OperatorRefStructure
    
    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.
  - ProductCategoryRef 0..1 ProductCategoryRefStructure
    
    Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl.
  - ServiceFeatureRef 0..unbounded ServiceFeatureRefStructure
    
    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.
- VehicleFeatureRef 0..unbounded VehicleFeatureRefStructure
  
  Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package.
groupJourneyInfoGroup 1..1

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.
- VehicleJourneyName 0..unbounded NaturalLanguageStringStructure
  
  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)
- JourneyNote 0..unbounded NaturalLanguageStringStructure
  
  Additional descriptive text associated with journey. Inherited property.
- PublicContact 0..1 SimpleContactStructure
  
  Contact details for use by members of public. (since SIRI 2.0)
- OperationsContact 0..1 SimpleContactStructure
  
  Contact details for use by operational staff. (since SIRI 2.0)
groupDatedServiceInfoGroup 1..1

General info elements that apply to all journeys of timetable version unless overriden.
- OriginDisplay 0..unbounded NaturalLanguageStringStructure
  
  Description of the origin stop (vehicle signage) to show on vehicle, Can be overwritten for a journey, and then also section by section by the entry in an Individual Call. (since SIRI 2.0)
- DestinationDisplay 0..unbounded NaturalLanguageStringStructure
  
  Description of the destination stop (vehicle signage) to show on vehicle, Can be overwritten for a journey, and then also section by section by the entry in an Individual Call. (Unbounded since SIRI 2.0)
- LineNote 0..unbounded NaturalLanguagePlaceNameStructure
  
  Additional Text associated with LINE. (Unbounded since SIRI 2.0)
- FirstOrLastJourney 0..1 FirstOrLastJourneyEnumerationdefault unspecified
  
  Whether journey is first or last jouurney of day. (since SIRI 2.0)
groupTimetableRealtimeInfoGroup 1..1

Additional descriptive properties of service.
- HeadwayService 0..1 xsd:boolean
  
  Whether this is a Headway Service, that is, one shown as operating at a prescribed interval rather than to a fixed timetable.
- Monitored 0..1 xsd:booleandefault true
  
  Whether VEHICLE JOURNEYs of LINE are normally monitored. Provides a default value for the Monitored element on individual journeys of the timetable.
groupDatedTrainOperationalInfoGroup 1..1

Operational information about the monitored VEHICLE JOURNEY.
- TrainBlockPart 0..unbounded TrainBlockPartStructure
  
  If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses.
- groupDatedOperationalInfoGroup 1..1
  
  Operational information about the monitored VEHICLE JOURNEY.
  - groupOperationalBlockGroup 1..1
    
    Operational information about the monitored VEHICLE JOURNEY.
    - BlockRef 0..1 BlockRefStructure
      
      BLOCK that VEHICLE is running.
    - CourseOfJourneyRef 0..1 CourseOfJourneyRefStructure
      
      COURSE OF JOURNEY ('Run') that VEHICLE is running.
  - VehicleRef 0..1 VehicleRefStructure
    
    Reference to a VEHICLE.
- TrainNumbers 0..1
  
  TRAIN NUMBERs for journey. (since SIRI 2.0)
  - TrainNumberRef 1..unbounded TrainNumberRefStructure
    
    TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0
- JourneyParts 0..1
  
  JOURNEY PARTs making up JOURNEY +SIRIv2.0 e.
  - JourneyPartInfo 1..unbounded DatedJourneyPartInfoStructure
    
    Information about Parts of JOURNEY (since SIRI 2.0)
- groupJourneyFormationGroup 1..1
  
  Groups relevant elements of the formation model that are used on JOURNEY level. The TRAIN conceptual model represents VEHICLE TYPE properties that are peculiar to TRAINs. A TRAIN may comprise not just a single VEHICLE but a chain of carriages, TRAIN ELEMENTS, assembled as TRAIN COMPONENTs. Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN made up of multiple TRAIN IN COMPOUND TRAIN, for example in a train that joins or splits. (since SIRI 2.1)
  - TrainElements 0..1
    - choice 1..unbounded
      - TrainElementRef 1..1 TrainElementRefStructure
        
        Reference to a TRAIN ELEMENT. (since SIRI 2.1)
      - TrainElement 1..1 TrainElementStructure
        
        An elementary component of a TRAIN, e.g. wagon or locomotive. (since SIRI 2.1)
  - Trains 0..1
    - choice 1..unbounded
      - TrainRef 1..1
      - Train 1..1 TrainStructure
        
        A vehicle composed of TRAIN ELEMENTs assembled in a certain order (so called TRAIN COMPONENTs), i.e. wagons assembled together and propelled by a locomotive or one of the wagons. (since SIRI 2.1)
  - CompoundTrains 0..1
    - choice 1..unbounded
      - CompoundTrainRef 1..1
      - CompoundTrain 1..1 CompoundTrainStructure
        
        Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN, for example if a TRAIN joins (or splits from) another TRAIN. (since SIRI 2.1) TRAINs within a COMPOUND TRAIN may have different origins and destinations due to joining/splitting. A COMPOUND TRAIN may be stable for one or multiple JOURNEY PARTs and change at a certain STOP POINT due to planned joining/splitting, despatching alterations or a situation.
DatedCalls 1..1

Complete sequence of stops along the route path, in calling order.
- DatedCall 2..unbounded DatedCallStructure
  
  Complete sequence of stops along the route path, in calling order.
JourneyRelations 0..1 JourneyRelationsStructure

Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc.
Extensions 0..1 ExtensionsStructure

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