Opened 4 years ago

Closed 3 years ago

#5335 closed defect (wontfix)

seperate node addr:housenumber is not found in nominatim search

Reported by: robertfloor@… Owned by: geocoding@…
Priority: minor Milestone:
Component: nominatim Version:
Keywords: Cc:

Description

When I use the search nominatim using the term "fire station, uden, netherlands" in the search field I get a result, but I don't get the house number returned, which I would like. The object of interest is a separate node on a building. There is another separate node nearby with a tag"addr:housenumber=4" but this value is not returned. It would be nice to get this value returned. Would this be possible?

Change History (3)

comment:1 Changed 4 years ago by Sarah Hoffmann

This is tricky because there are three objects involved in the computation. First, Nominatim has to figure out that the fire station node is inside a building and then that there is also a house number node in the building that might be related. It gets even more tricky if there are multiple house numbers. Then it would have to find all of them and decide which one is closest. All not impossible but unlikely to happen in the near future.

One thing does already work, though: if the house number is tagged on the building outline, then all POIs inside (including that fire station in the example) will inherit that house number if they don't have already one of their own.

comment:2 Changed 4 years ago by pnorman

I would say that there is somewhat of a data error here - if the address belongs to the entire building, it should be tagged on the building way. Trying to move addresses up from nodes to enclosing ways is likely to be fraught with problems, some of which lonvia has mentioned.

comment:3 Changed 3 years ago by Sarah Hoffmann

Resolution: wontfix
Status: newclosed

Agreeing with pnorman here. You should either tag the house number on the outline or add a housenumber tag to each POI in the building.

Note: See TracTickets for help on using tickets.