<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#333399" bgcolor="#FFFFFF">
<p><font face="Verdana">Seems a nice option. We all know, that
addresses due to their numerous local variants can be a very
complicated matter. What we have so far is very solid. I
propose to extend the examples in the wiki with confusing or
complicated challenges and how they can be viable and creatively
solved, like was done in the proposal page for the Vietnamese
addressing. So users, also the ones who don't contact any of our
help or communication channels find better guidance.</font></p>
<p><font face="Verdana">Greetings to all,</font></p>
<p><font face="Verdana">Bert Araali</font><br>
</p>
<div class="moz-cite-prefix">On 16/02/2021 14:46, Niels Elgaard
Larsen wrote:<br>
</div>
<blockquote type="cite"
cite="mid:5adee878-51da-9626-b26e-9aaae4a0ca12@agol.dk">Bert
-Araali- Van Opstal:
<br>
<blockquote type="cite">Can you give an example how a complete
address is written ? Don't focus to much on the key
descriptions, they are defined to cover as much as possible
cases worldwide.
<br>
<br>
So far I understand you have a street with a site that has a
single number, related to street numbering. On this site you
have several buildings with every building it's own building
nr., related to the site numbering Then each building has
several units or flats or apartments each with their own label,
name or number relate to the building numbering ?
<br>
</blockquote>
<br>
It is common with e.g. hospitals, universities, large companies,
etc. Usually tagged with "name" or "ref"
<br>
Which is used by data consumers, but not very well.
<br>
<br>
Bispebjerg Hospital:
<br>
<a class="moz-txt-link-freetext" href="https://www.openstreetmap.org/#map=18/55.71317/12.54046">https://www.openstreetmap.org/#map=18/55.71317/12.54046</a>
<br>
<br>
Building 10 has house:number 10.
<br>
But building 6 has house:number 5 and building 5 has house number
3.
<br>
<br>
Buildings could be named "Building 5". Or "Bygning 5",
localization would be a complication. And it is too verbose.
<br>
<br>
It just is confusing.
<br>
On their own map
<br>
<a class="moz-txt-link-freetext" href="https://publikationer.regionh.dk/pdf/full-715/kort-over-bispebjerg-hospital.pdf">https://publikationer.regionh.dk/pdf/full-715/kort-over-bispebjerg-hospital.pdf</a>
<br>
they show entrances based on both building numbers and house
numbers. So 20D is 23B and 20B is 23C, etc.
<br>
<br>
<br>
NBI:
<br>
<a class="moz-txt-link-freetext" href="https://www.openstreetmap.org/way/218541784">https://www.openstreetmap.org/way/218541784</a>
<br>
Uses letters for buildings. That works much better
<br>
<br>
SSI:
<br>
<a class="moz-txt-link-freetext" href="https://www.openstreetmap.org/way/28074637">https://www.openstreetmap.org/way/28074637</a>
<br>
Here building names are tagged with "ref"
<br>
It looks OK with Osmand because there are almost no addresses.
<br>
<br>
Gadehavegård:
<br>
<a class="moz-txt-link-freetext" href="https://www.openstreetmap.org/way/568142421">https://www.openstreetmap.org/way/568142421</a>
<br>
Have building names as "ref" and multiple addresses per building.
<br>
Osmand only show addresses at larger zoom leves. And then show
building names in a smaller font.
<br>
<br>
<br>
I think that "ref" is more appropriate. It gives data consumers a
change to handle it better. E.g. to show ref on buildings inside a
house icon. And a building could have both a name and a building
number.
<br>
<br>
</blockquote>
</body>
</html>