When adding traffic information on part of a trip it is not possible to know what part of the trip the message concerns if the trip in question has a loop.
A trip that visits stops A-B-C-D-E-A-F-G-H-I will hava a ambiguity for stop A when message is intended for part of trip
Both case A-D and case A-H will have AffectedStopPoint with reference to same StopPlace A
Resulting in the message being shown for travellers on both parts of the loop if any message is created for part including stop A
<Affects>
<VehicleJourneys>
<AffectedVehicleJourney>
<FramedVehicleJourneyRef>
[Ref_OF_VehicleJourney]
</FramedVehicleJourneyRef>
<LineRef>SE:276:Line:[ID_FOR_LINE]</LineRef>
<Route>
<StopPoints>
<AffectedStopPoint>
<AffectedStopPoint>
<StopPointRef>SE:276:StopPlace:[ID_FOR_STOP_A]</StopPointRef>
</AffectedStopPoint>
It would be preferable to add optional Order element, similar to how it is for SiriET, so that the two cases can be
<AffectedStopPoint>
<StopPointRef>SE:276:StopPlace:[ID_FOR_STOP_A]</StopPointRef>
<Order>1</Order>
</AffectedStopPoint>
and
<AffectedStopPoint>
<StopPointRef>SE:276:StopPlace:[ID_FOR_STOP_A]</StopPointRef>
<Order>6</Order>
</AffectedStopPoint>
When adding traffic information on part of a trip it is not possible to know what part of the trip the message concerns if the trip in question has a loop.
A trip that visits stops A-B-C-D-E-A-F-G-H-I will hava a ambiguity for stop A when message is intended for part of trip
Both case A-D and case A-H will have AffectedStopPoint with reference to same StopPlace A
Resulting in the message being shown for travellers on both parts of the loop if any message is created for part including stop A
It would be preferable to add optional Order element, similar to how it is for SiriET, so that the two cases can be
and