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.

Sign up for GitHub

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

Jump to bottom

Historic boundary causes incorrect city within address details #90

Closed
lm opened this issue Oct 14, 2013 · 2 comments
Closed

Historic boundary causes incorrect city within address details #90

lm opened this issue Oct 14, 2013 · 2 comments

Comments

@lm
Copy link

lm commented Oct 14, 2013

Nominatim returns incorrect city for address u hriste 13 brno:
http://nominatim.openstreetmap.org/search/u%20hriste%2013%20brno?format=json&addressdetails=1

city contains Lískovec, but the correct value is Brno. It looks like city is deduced from this node http://www.openstreetmap.org/browse/relation/3188947 instead of http://www.openstreetmap.org/browse/relation/438171.
@lonvia
Copy link
Member

lonvia commented Oct 14, 2013

The combination of boundary and admin_level tag messes things up. It's about time to ignore admin_level on anything but boundary=administrative.

@lonvia lonvia closed this as completed in 71429b9 Oct 15, 2013
@lonvia
Copy link
Member

lonvia commented Oct 15, 2013

Fix is now live on osm.org. I've forced a reindex on the example boundary, others will follow when they are next modified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lm @lonvia