Innhold
Table of Contents |
---|
Info | ||
---|---|---|
| ||
Se komplette eksempler for datainnsending Før avgangSee complete examples:
|
Tog som er innstilt mellom Dombås og Trondheim
Datainnsending før avgang
Siste betjente stoppested
...
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>
, men but <DepartureStatus>cancelled</DepartureStatus>
.
Kansellerte stoppesteder
...
Cancelled stops
The successive stops are cancelled by setting <Cancellation>true</Cancellation>
in addition to <ArrivalStatus>cancelled</ArrivalStatus>
and <DepartureStatus>cancelled</DepartureStatus>
.
Unntaket er siste stopp, Trondeheim, som ikke har avgangsinformasjon. Dvs naturligvis ikke The exception is the final stops, Trondheim, which does not have departure information and subsequently cannot have <DepartureStatus>cancelled</DepartureStatus>
.
Datainnsending etter avgang
Om et kjøretøy blir delinnstilt etter det har begynt å kjøre, sendes endringene som EstimatedCalls på samme måte som ved kansellering før avgang.
...
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.