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.

Sign up for GitHub

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

Jump to bottom

VVM ambiguouity #41

Closed
alexander-albers opened this issue Sep 9, 2021 · 1 comment
Closed

VVM ambiguouity #41

alexander-albers opened this issue Sep 9, 2021 · 1 comment
Labels
question Further information is requested

Comments

@alexander-albers
Copy link
Owner

Previously, the VVM Mittelfranken provider has been used in VvmProvider.swift. The old endpoint was no longer reachable, and when I migrated the url to the current one, I confused VVM Mittelfranken with VVM Mainfranken and added the endpoint for the latter. Both providers use https://www.bayern-fahrplan.de on their website and are probably connected to DEFAS, but the VVM Mittelfranken app does not use the Efa or Hafas API. The question is how to move forward from now on.

As some station ids seem to be interoperable, I tend to just keep the current implementation of the VVM and continue only supporting the VVM Mainfranken for now..

see schildbach/public-transport-enabler#400
@alexander-albers alexander-albers added the question Further information is requested label Sep 9, 2021
@alexander-albers alexander-albers mentioned this issue Sep 9, 2021
Closed
@alexander-albers
Copy link
Owner Author

Using VVM Mainfranken for now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@alexander-albers