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

4 top-level
  • groupJourneyIdentityGroup 1..1

    Elements identifying VEHICLE JOURNEY.

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

  • groupVehicleJourneyInfoGroup 1..1

    Common information about a VEHICLE JOURNEY. (Similar to VDV TripInfo)

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

    • groupJourneyEndNamesGroup 0..1

      End names for journey.

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

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

      • IsDeadRun 0..1 xsd:boolean

        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

    • groupJourneyEndTimesGroup 0..1

      Call times for journey.

      • HeadwayService 0..1 xsd:booleandefault false

        Whether this is a Headway Service, that is shown as operating at a prescribed interval rather than to a fixed timetable. Default is 'false'.

      • OriginAimedDepartureTime 0..1 xsd:dateTime

        Timetabled departure time from Origin.

      • DestinationAimedArrivalTime 0..1 xsd:dateTime

        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.