-
Notifications
You must be signed in to change notification settings - Fork 0
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
Wrong address by default #542
Comments
Not sure whether I would call this a bug. With the API we get some data back and this says it's a village called Kleinseebach. We could make another call (over the network) to get some more information, and check whether it's a village or a kind of suburb of an area. In most cases the village identifier is correct as we have a isolated settlement in a larger area. As said we can make a second call to re-fine the data, but in most cases this would not give more information. In most cases where a village belongs to a town a separate field is given, which is called town or city. When this is given, then this identifier is taken over the village identifier. This seems to be special with the OSM data and I would question the OSM data (theoretically). |
Thanks for clarification! What can I report back to the user? That it's an OSM oddity? |
For now I would consider this an oddity, which can be solved with some extra logic + effort. Nevertheless we maybe can collect these "issues" in a separate issue with sub-issues to tackle them in a later release in one step. If I would write to the user the message would be: |
Great, thank you @Stift :) |
Process: when only "village" is shown, a second request is made, so more information is retrieved @Stift |
Describe the Bug
In the app, the posters and doors registered in Möhrendorf were marked with the town of Kleinseebach by default, although the posters were not hung up in Kleinseebach but in Möhrendorf.
Steps to Reproduce
The text was updated successfully, but these errors were encountered: