Complex type

DatedVehicleJourneyStructure

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

Transmodel concept DATED VEHICLE JOURNEY

Type for Planned VEHICLE JOURNEY (Production Timetable Service).

Used by elements

Content model

Type 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

    • 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.

  • groupJourneyEndNamesGroup 1..1

    End names for journey.

  • 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.

    • 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.

  • 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.

  • DatedCalls 1..1

    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 to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators).