Complex type

MonitoredVehicleJourneyStructure

Defined in SIRI/xsd/siri_model/siri_monitoredVehicleJourney.xsd:112

Transmodel concept MONITORED VEHICLE JOURNEY

Type for Monitored VEHICLE JOURNEY.

Used by elements

Content model

Type structure

7 top-level
  • groupMonitoredJourneyIdentityGroup 1..1

    Elements identifying a VEHICLE JOURNEY. LINE and DIRECTION will be same as for journey unless overridden.

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

  • groupDisruptionGroup 1..1

    Elements describing nature of disruption.

  • groupJourneyProgressGroup 1..1

    Elements describing the real-time progress of a monitored VEHICLE JOURNEY.

    • Monitored 0..1 xsd:booleandefault true

      Whether there is real-time information available for journey. Default is 'true'. It is recommended to specify a MonitoringError if Monitored is set to 'false'.

    • MonitoringError 0..1 xsd:NMTOKENS

      If Monitored is 'false', a (list of) reason(s) for non-availability of real-time data. Examples are "GPS", "GPRS", "Radio" etc. MonitoringError must not be used if Monitored is omitted or set to 'true'.

    • groupProgressDataQualityGroup 1..1

      Elements describing the qua;ity of real-time progress data of a journey.

      • InCongestion 0..1 xsd:boolean

        Whether the VEHICLE iis in traffic congestion. If not, present, not known.

      • InPanic 0..1 xsd:booleandefault false

        Whether the panic alarm on the VEHICLE is activated. This may lead to indeterminate predictions. If absent, default is 'false'.

      • PredictionInaccurate 0..1 xsd:booleandefault false

        Whether the prediction for a specific stop or the whole journey is considered to be of a useful accuracy or not. Default is 'false', i.e. prediction is considered to be accurate. If prediction is degraded, e.g. because of a situation, PredictionInaccurate is used to indicate a lowered quality of data. Inherited property. PredictionInaccurate can be used in combination with InCongestion, but is more general.

      • Can be used to inform the passenger about the reason for a change of the prediction (in)accuracy in case PredictionInaccurate is set to 'true'. (since SIRI 2.1)

      • DataSource 0..1 xsd:string

        System originating real-time data. Can be used to make judgements of relative quality and accuracy compared to other feeds.

      • ConfidenceLevel 0..1 QualityIndexEnumerationdefault reliable

        Confidence QUALITY LEVEL of data. Default is 'reliable'.

    • groupProgressDataGroup 1..1

      Elements describing the real-time progress of a journey.

      • VehicleLocation 0..1 LocationStructure

        Current geospatial location of VEHICLE. Measured to front of vehicle.

      • LocationRecordedAtTime 0..1 xsd:dateTime

        Time at which location was recorded. If not present assume that the recorded at time on the containing delivery.

      • Bearing 0..1 AbsoluteBearingType

        Bearing in compass degrees in which VEHICLE is heading.

      • ProgressRate 0..1 ProgressRateEnumeration

        Rate of progress of VEHICLE. Default is 'normal'

      • Velocity 0..1 VelocityType

        Velocity of VEHICLE. Either actual speed or average speed may be used. (since SIRI 2.0)

      • EngineOn 0..1 xsd:booleandefault true

        Whether the engine of the vehicle is on. Default is 'true' (since SIRI 2.0)

      • An approximate figure of how occupied the journey is after departing from a given stop, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. If omitted: Passenger load is unknown. Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRAIN, can also be specified in more detail for the departure on CALL level.

      • Delay 0..1 DurationType

        Delay of VEHICLE against schedule, to a precision in seconds. Early times are shown as negative values.

      • ProgressStatus 0..unbounded NaturalLanguageStringStructure

        An arbitrary textual status description of the running of this VEHICLE JOURNEY. (Unbounded 0:* since SIRI 2.0)

      • VehicleStatus 0..1 VehicleStatusEnumeration

        An classification of the progress state of running of this VEHICLE JOURNEY. (since SIRI 2.0)

  • groupTrainOperationalInfoGroup 1..1

    Operational information about the monitored VEHICLE JOURNEY.

  • groupMonitoredCallingPatternGroup 1..1

    The service pattern of a monitored VEHICLE JOURNEY. CALLs should be assigned to one of three groups according to the vehicle's current position.

    • PreviousCalls 0..1 PreviousCallsStructure

      Information on stops called at previously, origin and all intermediate stops up to but not including the current stop, in order or visits. Should only be included if the detail level was requested.

    • MonitoredCall 0..1 MonitoredCallStructure

      Monitored CALL at the current stop. For SIRI-SM this is the stop for which data is requested. For SIRI-VM this is the most recent stop visited by the VEHICLE.

    • OnwardCalls 0..1 OnwardCallsStructure

      Information on CALLs at the intermediate stops beyond the current stop, up to and including the destination, in order of visits. Should only be included if the detail level was requested.

    • IsCompleteStopSequence 0..1 xsd:booleandefault false

      Whether the above CALL sequence is complete, i.e. represents every CALL of the ROUTE and so can be used to replace a previous CALL sequence. Default is 'false'.