SIRI-ET - Cancelled before departure
XML
See complete examples:
- Before departure: https://github.com/entur/profile-norway-examples/blob/master/siri/estimated-timetable/siri-et-partial-cancellation-last-stops.xml
- After departure: https://github.com/entur/profile-norway-examples/blob/master/siri/estimated-timetable/siri-et-partial-cancellation-last-stops-after-departure.xml
Example: Train is cancelled between Dombås and Trondheim
Published data before departure
Last served stop:
Dombås status has not been set to <Cancellation>true</Cancellation>
, but <DepartureStatus>cancelled</DepartureStatus>
.
Cancelled stops
The successive stops are cancelled by setting <Cancellation>true</Cancellation>
in addition to <ArrivalStatus>cancelled</ArrivalStatus>
and <DepartureStatus>cancelled</DepartureStatus>
.
The exception is the final stops, Trondheim, which does not have departure information and subsequently cannot have <DepartureStatus>cancelled</DepartureStatus>
.
Published data after departure
If a vehicle becomes partially cancelled after it has begun its journey, the changes are sent as EstimatedCalls in the same way as when cancelling before departure.
The example "after departure" shows the vehicle has passed Otta and been partially cancelled from Dombås and onward. The vehicles final stop is now Dombås.