Reverse geocoding - deal better with building / address points

[freyfogle]

Here is a good example where we currently do a bad job with reverse geocoding.

Coordinates 47.31576, 10.83486
https://nominatim.openstreetmap.org/ui/reverse.html?lat=47.31576&lon=10.83486&zoom=18

we return the nearest building "Altersheim via Claudia"
https://www.openstreetmap.org/way/466470232
which has no address details

But if you look at the map, you see there is an address point (node) inside the way
https://www.openstreetmap.org/node/5737187056
which has all the address info.

I unterstand why this is, the node and the way are not connected in any data relationship sense.
Is there some way nominatim can nevertheless retrieve this information?

Or is there some tagging change needed to enable nominatim to become aware that the address of the node "belongs" to the building?

As you can guess it's very frustrating to have the correct information so tantelizingly close.

[lonvia]

The solution for that is implementing #1469.

[freyfogle]

fantastic, but ideally the response would return the name AND the address, not just the address. Both are relevant, they are just split across two OSM objects

[lonvia]

Ah, sorry that was about address inheritance. Nominatim already does that from building to inner POIs. The other way around is more challenging because there can be multiple house numbers in the building. Although we could do at least the simple cases like this one.

Where we really have to draw the line is where an address node and a POI node are within the same building outline. Nominatim doesn't have the data (simple building=yes outlines) to resolve such a situation.

[lonvia]

I gave this a quick try and number->outline inheritance it is rather expensive, simply because there are so many objects.

[Zverik]

JFYI, I clicked the first link, and the result contained an address. The closest building with an address is returned, so the result is still incorrect (12a building is closer), but at least we get some address.