stadtnavi / stadtnavi_app

The model project for networked mobility in Herrenberg
https://stadtnavi.de/
GNU General Public License v3.0
6 stars 2 forks source link

Upcoming GBFS feed id changes #353

Open hbruch opened 6 months ago

hbruch commented 6 months ago

Is your feature request related to a problem? Please describe. For some GBFS feeds, the feed_id will change as the data source will be switched to https://api.mobidata-bw.de/sharing/gbfs/.

RegioRad will change from de.mfdz.flinkster.cab.regiorad_stuttgart to regiorad_stuttgart, car-sharing to presumably stadtmobil_stuttgart.

Describe the solution you'd like Please prepare the app to reflect these upcoming changes, ideally by supporting both, old and new version, so the switch can be done asynchronously.

Describe alternatives you've considered Probably it would be best to avoid hard coded dependencies on the OTP configuration and rather have a remote stadtnavi app configuration which allows configuration changes without a new app rollout.

stadtnavimanager commented 5 months ago

Denis, can you please update us on the status?

GustavoTCh commented 1 month ago

@hbruch, @Denis306

Proposal:

I propose creating a JSON configuration file on the server for the mobile app. This file would allow us to dynamically retrieve data and apply this configuration each time the app is launched. We could define elements such as URLs that need to be handled dynamically. Additionally, it would be necessary to maintain separate configuration files for different instances, specifically one for Herrenberg and another for Ludwigsburg.

Denis306 commented 1 week ago

@hbruch Can you provide feedback here? Is this approach okay for you?