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

Geocoding fails when searching for both name and house number #164

Closed
scaidermern opened this issue Jul 22, 2014 · 13 comments
Closed

Geocoding fails when searching for both name and house number #164

scaidermern opened this issue Jul 22, 2014 · 13 comments

Comments

@scaidermern
Copy link

As reported via help.openstreetmap.org the search yields no result when searching for both the name and the house number. Example:

@hohl
Copy link

hohl commented Jan 13, 2015

May be related to my bug: When searching for a full address (like "Sample Street 123") it always finds "Sample Street" but not the exact house. (But the exact house number is noted correctly in OSM) Seems to be related with how long the street is too.

@arvindkartik
Copy link

I came across a similar issue. Searching for "Upper Camden Street, Saint Kevin's, Dublin 2" would work, but adding a house number to the query would not give any results.

Search query up to street level succeeds

Search query with house number fails

@joy-yyd
Copy link
Contributor

joy-yyd commented Jun 17, 2020

Hello,
Regarding the problem mentioned in #1821, we've modified the tag to addr:place=place_name and load the data in local Nominatim, it seems still not able to find the place with House number. Is it possible to add more tags to the parent node?
Thanks a lot for your help!

@lonvia
Copy link
Member

lonvia commented Jul 1, 2020

There are no immediate plans for a fix. It's not exactly trivial.

@joy-yyd
Copy link
Contributor

joy-yyd commented Jul 8, 2020

Hello Sarah, I modified the address_rank as $aTerms[] = 'address_rank between 16 and 30'; in https://github.com/osm-search/Nominatim/blob/master/lib/SearchDescription.php#L660. Wit this change, it seems to have found the places by name with house number for the examples above in Austria. Then, I tested some addresses for the house number with the street and no house number search, the results are the same as the original code. I am wondering if there is a downside of this fix? Or I can ask for a pull request for the change. Many thanks!

@lonvia
Copy link
Member

lonvia commented Jul 8, 2020

This might work. I don't think there is too much overlap with streets and POI names here. Feel free to do a PR.

joy-yyd added a commit to joy-yyd/Nominatim that referenced this issue Jul 8, 2020
lonvia added a commit that referenced this issue Jul 18, 2020
@lonvia
Copy link
Member

lonvia commented Jul 27, 2020

Fixed by #1874.

@lonvia lonvia closed this as completed Jul 27, 2020
@joy-yyd
Copy link
Contributor

joy-yyd commented Sep 24, 2020

Hello Sarah,
As we are testing the Release 3.5.1, we found that the code seems not changed, though the pull request has been merged, as the following:

$aTerms[] = 'address_rank between 16 and 27';

Could you help us to merge it again if the code is reverted?
Thanks a lot!
Joy

@lonvia
Copy link
Member

lonvia commented Sep 24, 2020

#1874 is not in the 3.5.1 release as it was merged later.

@joy-yyd
Copy link
Contributor

joy-yyd commented Sep 24, 2020

ok, thank you Sarah!

@juanpelegrina
Copy link

#1874 is not in the 3.5.1 release as it was merged later.

any idea on when the next release is planned?

@lonvia
Copy link
Member

lonvia commented Sep 24, 2020

Tomorrow. However, this particular feature will only be included when we do the 3.6 release which is still a couple of months away.

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

No branches or pull requests

6 participants