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

Unexpected objects in search results for a building address #3603

Closed
rpahut opened this issue Dec 2, 2024 Discussed in #3602 · 2 comments · Fixed by #3615
Closed

Unexpected objects in search results for a building address #3603

rpahut opened this issue Dec 2, 2024 Discussed in #3602 · 2 comments · Fixed by #3615

Comments

@rpahut
Copy link

rpahut commented Dec 2, 2024

Discussed in #3602

Searching for some building addresses with layer=ADDRESS in a DB imported with NOMINATIM_IMPORT_STYLE=address yields, on top of the building at the address, other unexpected POI-like objects.

Examples:
N5266350421, N5266417321 for address (now removed).
N4682629046 for address.

The expected behavior is for POIs to be absent in a DB imported with NOMINATIM_IMPORT_STYLE=address, or if they has to be present, not be returned alongside the exact address match when there is one, or if they has to be returned, to be practically distinguishable from the exact address match.

@lonvia
Copy link
Member

lonvia commented Dec 12, 2024

As already discussed in #3602: the presence of these objects when using the address import style is entirely expected. The POIs have an address mapped and therefore need to be imported. Nominatim cannot know in advance if the address will also be present on a building. The duplicates are filtered on output.

What should not happen is that the name of the POI object spills over into the address point. Without the POI type being set, the name is unrelated.

@rpahut
Copy link
Author

rpahut commented Dec 12, 2024

I thought the name is a part of the address, it kinda makes sense.
Will removing it relieve the issue in some way?

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.

2 participants