Reference to the Line in question (ID to the corresponding object in the timetable data)

Direction reference (i.e. reference to Direction element describing general course/heading for current Journey)

Please note that the field is implemented as mandatory, but is not used as a free standing data type in the Norwegian SIRI profile. If it is not used, this value can be set to 0 (zero).

DatedVehicleJourneyRef

Reference to DatedServiceJourney-ID for the corresponding object in the timetable data.

Unplanned replacement departures must be given a new codespace-unique ID.

For example: RUT:ServiceJourney:51-108833-11872056-00 / RUT:DatedServiceJourney:1234-1234-1234

The VehicleJourney in question is a replacement departure.

Must be 'true' if it is a replacement departure.

Reference to JourneyPattern in question (ID to the corresponding object in the timetable data).

Transport type.

Must be defined for replacement departures!

Possible values:

• air
• bus
• coach
• ferry (mapped to "water")
• metro
• rail
• tram

Reference to Route in question (ID to the corresponding object in the timetable data).

Must be defined for replacement departures!

Public number or name of the line. 

Is only used when replacement departures reference a new LineRef that is not already defined in timetable data. It will then be used to represent the added Line.

Reference to Network/GroupOfLines in question (ID to the corresponding object in the timetable data).

Must be defined for replacement departures!

Reference to Line in question (ID to the corresponding object in the timetable data) that the departure replaces. If not provided, the value from LineRef will be used.

Must be defined for replacement departures!

Name of the first stop of the departure (not used due to the reference to the national stop place registry, however can be included to make the XML easier to read).

Name of the last stop of the departure (not used due to the reference to the national stop place registry, however can be included to make the XML easier to read).

Reference to Operator in question (ID to the corresponding company in the timetable data)

Must be defined for replacement departures where the operator has been changed!

Contact point for the public (if different from original timetable information).

At least one field must be filled out.

Administrative contact details (if different from original timetable information).

At least one field must be filled out.

SIRI-ET#SituationRefStructure

Unique reference to one or more SituationNumber which link to earlier published Situation elements (SIRI-SX) when these provide supplementary information for the current EstimatedVehicleJourney.

Whether the vehicle is currently reporting real-time data or not (for example set to true when the driver of the vehicle logs on to the system before departing).

Whether the VehicleJourney is affected by traffic jams or other circumstances which lead to uncertainty around the time estimates.

Open seats-status.

Possible values:

• unknown
• manySeatsAvailable (more than ~50% of seats available)
• seatsAvailable (less than ~50% of seats available)
• standingAvailable (less than ~10% of seats available)
• full (close to or at full capacity)
• notAcceptingPassengers (if vehicle/carriage is not in use / unavailable, or passengers are only allowed to alight due to e.g. crowding)

This status should reflect the allowed occupancy level, not necessarily physical spacing available.

If the operator runs with reduced capacity, e.g. in order to maintain a certain service level, social distancing etc., the occupancy status must be set in accordance with current limitation i.e. "full" when all seats assigned for use are occupied (regardless of disallowed seating/standing still being physically available).

Reference to block (trip pattern)

Internal (non-public) information.

Reference to other affected VehicleJourneys.

The full sequence of already served stops in the order they were served by the VehicleJourney.

Please note that all stops in the sequence must be in chronological order. (Except if the recording of a call is missed, then this call may be kept in the sequence as a correspondingly labeled EstimatedCall even after passed.)

The full sequence of affected stops in the order they will be served by the VehicleJourney.

Please note that all stops in the sequence must be in chronological order.

Should always be 'true' as a confirmation that the sequence of RecordedCalls/EstimatedCalls is complete (contains all the stops) for the current EstimatedVehicleJourney.

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

SIRI v2.1 feature, awaiting approval of standard revision

Phone number

Reference to TRAIN

References to the QUAY on which the particular VEHICLE, i.e., component of the formation, arrives or departs from.

If a QUAY is divided into sub-QUAYs or sectors (with the help of STOP ASSIGNMENTs), and a TRAIN COMPONENT spans over multiple sectors of the QUAY, the FORMATION ASSIGNMENT must reference all of them (in multiple STOP ASSIGNMENTs).

Reference to TRAIN