Sarah Hoffmann

This is an awfully difficult problem because it requires concatenating two words into one. There are many names with hyphens. Would we want to do it for all of them...

Now that I think about it, the `refresh --importance` function will update the placex table but not the search_name table. That means that you can see the new importances but...

The only actionable item here is the part about postcodes. Might be worth pushing them into their own layer. They are currently part of the `address` layer but that might...

Lets just take example 1: the documentation says "zoom=13" returns suburb-like object and "zoom=14" returns neighbourhood-like objects. Your complaint: I get a `place=neighbourhood` at zoom=14. Essentially, this issue seems to...

The simple implementation would be to just interpret the value as an an alternative to `addr:housenumber` but that doesn't give you the optional unit. I've been looking through the existing...

May I suggest that you move the discussion to https://community.openstreetmap.org/t/rfc-feature-proposal-addr-milestone/121295/10? This is a wider tagging discussion and all highly relevant for the larger OSM community.

The `addr:conscriptionnumber`/`addr:housenumber` double tagging has been a long-standing open issue. It is not easy to fix because Nominatim's design is not made for splitting an address in this way. For...

The problem isn't that Nominatim doesn't handle `addr:conscriptionnumber` and `addr:streetnumber`. It already does that fine when looking at them separately. It will use `addr:street` with `addr:streetnumber` and `addr:place` with `addr:conscriptionnumber`....

Closing as this is rather a data issue.

I don't quite understand what you believe is wrong about the result. When searching for a name, Nominatim will return all matching results. The order in which they are returned...