nucleus-ffm
incorrect ARS for some places
Describe the bug
When refreshing the warnings (and on automatic refresh), the following error pops up:
Also, in the app "No server connection is shown".
To Reproduce Steps to reproduce the behavior:
- Install the app in the latest GitHub release version (although the current F-Droid version has the same issue)
- Add one location
- Drag down to refresh, or wait for automatic refresh
Expected behavior No error messages appear and/or warnings are loaded.
Device :
- Device: Pixel 7a
- OS: GrapheneOS latest (Android 14)
- App-version: 0.7.0
- Battery optimization: false
App Settings All defaults except for adding one location.
Does this happen for every location selected or just for one? It looks like some information is missing from the API result.
You're right, it does work for other locations. I've just tested it with a variety of locations and it seems to be related to Berlin districts. For example, selecting "Mitte (B)" will cause the error.
It seems that this is an incorrect data entry which comes from the list of the geocodes. The geocode for "Mitte (B)" is 110010001001 which is mapped to the geocode on district level 110010000000 which does not exist. It actually should have the same geocode as Berlin 110000000000.
The API only returns data on district level ("Kreisebene") so it would actually do not make any difference if you select "Berlin" or "Mitte".
But thanks for the hint, one more reason to speed up the migration to the new dataset prepared in https://github.com/nucleus-ffm/foss_warn/tree/allowUseOfCurrentLocation