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

Jump to bottom

state missing in reverse geocoding #121

Closed
RazAlon opened this issue Mar 23, 2014 · 1 comment
Closed

state missing in reverse geocoding #121

RazAlon opened this issue Mar 23, 2014 · 1 comment
Labels
bug Indexing Test needed

Comments

@RazAlon
Copy link

RazAlon commented Mar 23, 2014

I was told it's a good idea to report it, see last few comments in:

https://help.openstreetmap.org/questions/31439/state-is-missing-in-reverse-geocoding
@lonvia
Copy link
Member

lonvia commented Aug 8, 2015

The example query was: http://nominatim.openstreetmap.org/reverse?lat=39.062966597302903&lon=-94.608148997737700

The address hierarchy should actually contain both states and choose one of the two for the address.

lonvia added a commit to lonvia/Nominatim that referenced this issue Mar 18, 2017
@lonvia
for roads add all intersecting boundaries to address list
b3186d0 
When roads cross boundaries, both administrative entities should
be added to the address list, so that both entities can be used
for searching. Also allows in a second step to better sort out
addresses of POIs on such roads.

Fixes osm-search#121.
@lonvia lonvia mentioned this issue Mar 18, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Indexing Test needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lonvia @RazAlon