Skip to content
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

Closed
elcid opened this issue Jul 17, 2017 · 8 comments · Fixed by #1702
Closed

Structured Query returns wrong result: Nürnberg #774

elcid opened this issue Jul 17, 2017 · 8 comments · Fixed by #1702

Comments

@elcid
Copy link

elcid commented Jul 17, 2017

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

@lonvia
Copy link
Member

lonvia commented Jul 23, 2017

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.

@elcid
Copy link
Author

elcid commented Jul 28, 2017

I found this Issue:
https://trac.openstreetmap.org/ticket/5300

@RedBaron2
Copy link

I will add one more to the list of issues.
Query for Austin, MN
This returns
<city>Austin</city>
<county>Travis County</county>
<state>Texas</state>
<country>USA</country>
<country_code>us</country_code>
You change the Query
Austin, Minnesota
<city>Austin</city>
<county>Mower County</county>
<state>Minnesota</state>
<country>USA</country>
<country_code>us</country_code>
I had thought that it was a coding issue on my end, but after plugging in the city, state directly. The same buggy return is presented.
My guess is that the query is not passing a secondary check to verify the State Abbreviation, and instead is going on the most popular search for that City.

@mtmail
Copy link
Collaborator

mtmail commented Feb 21, 2019

Hi @RedBaron2. Can you submit this as a new issue? You use q= which isn't a structured query (e.g. city=...&state=...) so it seems unrelated.

@RedBaron2
Copy link

@mtmail
I will submit it as a new issue then

@FelHell
Copy link

FelHell commented May 27, 2019

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.

@lonvia
Copy link
Member

lonvia commented Mar 4, 2020

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).

@micw
Copy link

micw commented Mar 10, 2020

@lonvia Could you trigger a forced update for Nürnberg to verify that fix?
That could cause https://nominatim.openstreetmap.org/search?format=json&addressdetails=1&featuretype=city&q=90411%20N%C3%BCrnberg to return a record, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants