Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SIRI references pointing to ScheduledStopPoint instead of Quay #6340

Open
leonardehrenfried opened this issue Dec 17, 2024 · 0 comments
Open

Comments

@leonardehrenfried
Copy link
Member

leonardehrenfried commented Dec 17, 2024

Background

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:

ScheduledStopPoint-Page-1 drawio

Here is a diagram showing the NeTEx data model and its closest equivalent in the OTP model.

classmodel

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

cc @rcavaliere @t2gran

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant