Is your feature request related to a problem? Please describe.
In the last months, most of mfdz/OpenTripPlanner's features have been integrated in upstream opentripplanner/opentripplanner. For stadtnavi Herrenberg, we already transitioned to this version, currently deployed at api.dev.stadtnavi.eu.
Describe the solution you'd like
All stadtnavi apps should be migrated to the new version, temporarily deployed at api.dev.stadtnavi.eu. As soon as this transition has been completed, we'll switch api.stadtavi.de to this top version and the apps should be switched to this server again.
Describe alternatives you've considered
Additional context
Note: especially the parking graphql API part changed a bit and will need to be adapted.
Is your feature request related to a problem? Please describe. In the last months, most of mfdz/OpenTripPlanner's features have been integrated in upstream opentripplanner/opentripplanner. For stadtnavi Herrenberg, we already transitioned to this version, currently deployed at api.dev.stadtnavi.eu.
Describe the solution you'd like All stadtnavi apps should be migrated to the new version, temporarily deployed at api.dev.stadtnavi.eu. As soon as this transition has been completed, we'll switch api.stadtavi.de to this top version and the apps should be switched to this server again.
Describe alternatives you've considered
Additional context Note: especially the parking graphql API part changed a bit and will need to be adapted.