Skip to end of banner
Go to start of banner

SIRI-ET - Changed platform

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »


XML

See complete examples:

When any platform (Quay) is changed, the entire sequence of stops must be re-confirmed in the dataset.

Original dataset

In the original SIRI dataset (or the planned data) the last stop of the vehicle is <StopPointRef>NSR:Quay:1078</StopPointRef> (See the last EstimatedCall of the dataset).

<EstimatedCall>
	<StopPointRef>NSR:Quay:1078</StopPointRef>
	<Order>8</Order>
	<StopPointName>Trondheim</StopPointName>
	<RequestStop>false</RequestStop>
	<AimedArrivalTime>2018-04-18T14:32:00+02:00</AimedArrivalTime>
	<ExpectedArrivalTime>2018-04-18T14:32:00+02:00</ExpectedArrivalTime>
	<ArrivalStatus>onTime</ArrivalStatus>
	<ArrivalBoardingActivity>alighting</ArrivalBoardingActivity>
</EstimatedCall>

After the platform is changed

The last stop <StopPointRef>NSR:Quay:1078</StopPointRef> is replaced by <StopPointRef>NSR:Quay:1081</StopPointRef> (both are Trondheim).

<EstimatedCall>
	<StopPointRef>NSR:Quay:1081</StopPointRef>
	<Order>8</Order>
	<StopPointName>Trondheim</StopPointName>
	<RequestStop>false</RequestStop>
	<AimedArrivalTime>2018-04-18T14:32:00+02:00</AimedArrivalTime>
	<ExpectedArrivalTime>2018-04-18T14:32:00+02:00</ExpectedArrivalTime>
	<ArrivalStatus>onTime</ArrivalStatus>
	<ArrivalBoardingActivity>alighting</ArrivalBoardingActivity>
</EstimatedCall>
  • No labels