You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
South Tyrol in Italy has a SIRI feed where the <StopPointRef> elements point to ScheduledStopPoint and not Quay.
After a lot of discussions with the NeTEx authors as well as the Entur authors, we agreed that OTP should support ScheduledStopPoint references in SIRI as well as Quay.
Design
To achieve this I propose the following design:
Here is a diagram showing the NeTEx data model and its closest equivalent in the OTP model.
Here are the key data flows:
TimetableRepository will have a new map from ScheduledStopPointId to QuayId
This collection is filled during the graph build
TimetableRepository is then is then injected into TransitService which is injected into the SIRI updaters
Background
South Tyrol in Italy has a SIRI feed where the
<StopPointRef>
elements point toScheduledStopPoint
and notQuay
.After a lot of discussions with the NeTEx authors as well as the Entur authors, we agreed that OTP should support
ScheduledStopPoint
references in SIRI as well asQuay
.Design
To achieve this I propose the following design:
Here is a diagram showing the NeTEx data model and its closest equivalent in the OTP model.
Here are the key data flows:
TimetableRepository
will have a new map fromScheduledStopPointId
toQuayId
TimetableRepository
is then is then injected intoTransitService
which is injected into the SIRI updaterscc @rcavaliere @t2gran
The text was updated successfully, but these errors were encountered: