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
Structured Query returns wrong result: Nürnberg #774
Comments
|
That 's a known issue with German 'Kreisstädte' which cannot be found reliably with structured queries. (The problem being that they are mapped as counties in OSM not as a town.) I thought this was reported before but I can't see to find any older issue. |
|
I found this Issue: |
|
I will add one more to the list of issues. |
|
Hi @RedBaron2. Can you submit this as a new issue? You use |
|
@mtmail |
|
The problem with the German "Kreisstädte" still exists, for example for Augsburg:
...and for Nuremberg:
It would be nice if this issue could be fixed. It's surprising that a city like Augsburg is replaced with a small village like Augsberg. |
|
Please be aware that the fix will only gradually take effect on nominatim.openstreetmap.org because the database has not been reimported. There are also some boundary relations in OSM that still need an appropriate hint regarding their city status (either a place=city tag on the relation or linking of the place=city node as a member with a 'label' role). |
|
@lonvia Could you trigger a forced update for Nürnberg to verify that fix? |
This query: https://nominatim.openstreetmap.org/search.php?city=N%C3%BCrnberg&country=Deutschland
delivers the wrong location: Nürnberg, Tann (VGem), Landkreis Rottal-Inn, Lower Bavaria, Bavaria, Germany (Hamlet)
Otherwise by using query string, the web service return the correct city:
https://nominatim.openstreetmap.org/search.php?q=N%C3%BCrnberg&country=Deutschland
Any explanation or suggestion (if the case) how to fix this?
Thanks
The text was updated successfully, but these errors were encountered: