Content Comparison

version

Timestamp for when the dataset was created/published.

CreationTime

Unique situation-ID for PtSituationElement.

Format:
CODESPACE:SituationNumber:ID
e.g.: ABC:SituationNumber:123

Information on the source of the message.

1: 1

Status of a situation message.

Possible values:

• open
• closed (the situation is over and traffic has returned to normal)

Please note that when Progress is set to 'closed' the message is considered expired and should not be presented to the public.

Reason should always be <UndefinedReason/>.

The field is mandatory due to format specification, but is not used.

How severely the situation affects public transport services.

Possible values:

• noImpact
• verySlight
• slight
• normal (default)
• severe
• verySevere

Number value from 1 to 10 indicating the priority (urgency) of the situation message. 

1 - First (i.e. highest) message priority. Equivalent to DATEX2 urgency level "extremelyUrgent"
2 - 10 - Urgent, of various priority. Equivalent to DATEX2 urgency level "urgent" with added priority order.

Left blank (default) is equivalent to DATEX2 urgency level "normal urgency".

Type of situation report. The field is required in order to differentiate general information from incidents.

Possible values:

• general (used for public information not impacting the actual operation of the PT-service. eg. "No food service on this journey")

• incident (used for public information impacting the operation of the PT-service. eg. "expect delays due to road construction work") 

Whether the situation in question is due to planned events, or an unexpected incident.

1: *

(Can be 0 when Progress = "closed") 

Expanded textual description (if more than one, the xml:lang attribute must be set) of the situation (do not repeat information from Summary, or structured data).

Please do not add advice on how to avoid the situation, as this should be presented in the Advice field.

Textual advice (if more than one, the xml:lang attribute must be set) on how a passenger should react/respond to the situation.

Link to a website which has further information on the situation.

A description of what the situation affects.

Only allowed to be blank (have no content) when message progress is set to "closed".

AffectedOperator

Reference to the affected operator.

Affected modality.

Possible values:

• all
• air
• bus
• coach
• funicular (please note: does not have a corresponding submode)
• metro
• rail
• taxi (please note: does not have a corresponding submode)
• telecabin (mapped to til cableway) (please note: does not have a corresponding submode)
• tram
• water
• selfDrive

Modes must be specified together with corresponding submode (when applicable), whenever the situation does not affect all modalities in the affected planned data.

Possible values:

• domesticFlight
• helicopterService
• internationalFlight

Possible values:

• airportLinkBus
• expressBus
• localBusService (mapped to localBus)
• nightBus
• railReplacementBus
• regionalBus
• schoolBus
• shuttleBus
• sightseeingBus

Possible values:

• internationalCoachService (mapped to internationalCoach)
• nationalCoachService (mapped to nationalCoach)
• touristCoachService (mapped to touristCoach)

Possible values:

• metro
• urbanRailway

Possible values:

• interbational [sic]. Please note, the typo is incorrectly implemented in the official standard. Mapped to 'international'.
• interRegionalRailService (mapped to interregionalRail)
• local
• longDistanceTrain (mapped to longDistance)
• sleeperRailService (mapped to nightRail)
• regionalRail
• specialTrainService (mapped to airportLinkRail)
• touristRailway

Possible values:

• localTramService (mapped to localTram)

Possible values:

• highSpeedPassengerService
• highSpeedVehicleService
• internationalCarFerryService (mapped to internationalCarFerry)
• internationalPassengerFerry
• localCarFerryService (mapped to localCarFerry)
• localPassengerFerry
• nationalCarFerryService (mapped to nationalCarFerry)
• sightseeingService

Reference(s) to affected line(s).

Must be stated explicitly AffectedLine or AllLines due to technical demands on the element in the SIRI standard.

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

Reference to Route(s) in question (ID to the corresponding object in the timetable data), when the situation does not apply to the entire Line.

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

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

Reference to the Quay in question (ID corresponding to objects in the national stop place registry).

If the quay is currently unknown, or the message applies to all quays, a reference to StopPlace may be used instead.

Specifies which passengers the message applies to, for example, people who are disembarking at an affected stop.

Possible values:

• exceptionalStop (for passengers expecting an interchange)
• destination (for passengers expecting to disembark, of at the last stop)
• notStopping (when passing a stop)
• requestStop (when a passenger must request the serving of a stop)
• startPoint (at departure or when passengers expect to board)
• stop (default - affects all interactions with the stop (boarding, alighting, arrival, departure, interchanges)

If this field is left blank or omitted the message will be interpreted as affecting boarding and alighting.

Specifies whether the object is still available for users with special needs.

Reference to StopPlace or specific Quay (ID corresponding to objects in the national stop place registry).

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

Reference(s) to which part(s) of the stop(s) are being affected.

Reference to the Quay in question (ID corresponding to objects in the national stop place registry).

Used if ComponentType is "quay"

Possible values:

• accessSpace
• boardingPosition (only for trains)
• entrance
• quay

Possible values:

• escalator
• lift
• narrowEntrance
• ramp
• stairs

Used when it necessary to specify limitations for users with special mobility needs.

Reference to affected VehicleJourney (ID to the corresponding object in the timetable data).

Reference with date to affected VehicleJourney (ID to the corresponding object in the timetable data).

Reference to affected Operator (ID to the corresponding object in the timetable data).

Not used, but may be set to increase human readability.

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

Not used, but may be set to increase human readability.

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

Mandatory field (due to format implementation), but can be blank if the situation affects all stops in AffectedVehicleJourney.

Originally planned departure time (per time table) from the first stop of the departure.