SIRI-ET - Changed platform

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:1079</StopPointRef> (See the last EstimatedCall of the dataset). In <ArrivalStopAssignment> the values for <AimedQuayRef> and <ExpectedQuayRef> are equal.

<EstimatedCall>
    <StopPointRef>NSR:Quay:1079</StopPointRef>
    <Order>5</Order>
    <StopPointName>Trondheim</StopPointName>
    <RequestStop>false</RequestStop>
    <AimedArrivalTime>2019-08-16T22:49:00+02:00</AimedArrivalTime>
    <ExpectedArrivalTime>2019-08-16T22:49:00+02:00</ExpectedArrivalTime>
    <ArrivalStatus>onTime</ArrivalStatus>
    <ArrivalPlatformName>2</ArrivalPlatformName>
    <ArrivalBoardingActivity>alighting</ArrivalBoardingActivity>
    <ArrivalStopAssignment>
        <AimedQuayRef>NSR:Quay:1079</AimedQuayRef>
        <ExpectedQuayRef>NSR:Quay:1079</ExpectedQuayRef>
    </ArrivalStopAssignment>
</EstimatedCall>

After the platform is changed

The last stop <StopPointRef>NSR:Quay:1079</StopPointRef> is replaced by <StopPointRef>NSR:Quay:1078</StopPointRef> (both are Trondheim). Also <ExpectedQuayRef>NSR:Quay:1079</ExpectedQuayRef> is replaced by <ExpectedQuayRef>NSR:Quay:1078</ExpectedQuayRef> in <ArrivalStopAssignment>.

<EstimatedCall>
    <StopPointRef>NSR:Quay:1078</StopPointRef>
    <Order>5</Order>
    <StopPointName>Trondheim</StopPointName>
    <RequestStop>false</RequestStop>
    <AimedArrivalTime>2019-08-16T22:49:00+02:00</AimedArrivalTime>
    <ExpectedArrivalTime>2019-08-16T22:49:00+02:00</ExpectedArrivalTime>
    <ArrivalStatus>onTime</ArrivalStatus>
    <ArrivalPlatformName>1</ArrivalPlatformName>
    <ArrivalBoardingActivity>alighting</ArrivalBoardingActivity>
    <ArrivalStopAssignment>
        <AimedQuayRef>NSR:Quay:1079</AimedQuayRef>
        <ExpectedQuayRef>NSR:Quay:1078</ExpectedQuayRef>
    </ArrivalStopAssignment>
</EstimatedCall>