<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 2017-03-18 14:16, Martin
Koppenhoefer wrote:<br>
</div>
<blockquote
cite="mid:FED80F82-EAC4-4DBD-966E-05A0559D8BA7@gmail.com"
type="cite">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div>if there's a whole building or area with one housenumber you
can put the feature inside and it can inherit the address from
the area,</div>
</blockquote>
There are two ways to tag multiple features (or a single one) of the
same building:<br>
<ul>
<li>name space tags, but it's complicated, not well formalized, a
number of people don't like namespace although it's widely used
and others don't understand it well</li>
<li>use separate feature elements inside the buildings</li>
</ul>
<p>I polled several people near me and separate features are by far
preferred.<br>
On the other hand, I'm tagging many buildings (very precisely) and
very often the features are already there and I tag the building
around (or, most often, I move the feature inside :-)).<br>
</p>
<p>I see it almost the same way as you, except that because a
feature is not an object (visible "on the ground" etc.) it is not
normally allowed to stand alone on OSM and it has to conceptually
be merged with the building so that the building inherits the
features too to achieve the same as method #1.<br>
</p>
<p>So, indeed, a feature can be tagged with the same street address
as one of the building, not only because it can be multiple on the
building but because, even with a single address, <b>someone
listing the feature tags will not see the address</b> and may
well not think of finding it in the building tags.<br>
</p>
<b>So, the wiki should clearly state and Osmose should be notified
that forbidding to use the same address twice holds between
buildings (objects) and not between features (non objects) and
other elements.</b><br>
The tags of the features are the tags of the object they belong to
and, BTW, having the same street address as the object is a good way
to show to which object (or entrance thereof) they belong.<br>
<br>
Cheers
<br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
<blockquote
cite="mid:FED80F82-EAC4-4DBD-966E-05A0559D8BA7@gmail.com"
type="cite">
<div> it seems like a good way to map, but in many cases this is
not possible. In Italy in general, every entrance and even some
potential entrances get their own number. Features on the ground
floor can easily be accessible by several numbers (store fronts
tend to get a number for each window), even <br>
on different streets (if they're on a street <span
style="background-color: rgba(255, 255, 255, 0);">corner). But
often the shops only use some of these numbers (often their
main entrance). It makes sense to add address information to
those features (the address they use) rather or in addition to
adding the address to the entrance (alternatively we could
associate the entrance with a relation to the feature, but
this seems less stable and more complicated for less
experienced mappers).</span></div>
<div><br>
</div>
<div>This practice isn't reflected by the current documentation of
Addresses:</div>
<div><a moz-do-not-send="true"
href="https://wiki.openstreetmap.org/wiki/Addresses">https://wiki.openstreetmap.org/wiki/Addresses</a></div>
<div><br>
</div>
<div>I would like to add it, but I'm unsure if this is
Italy-specific or if we could recommend to map like this in
general.</div>
<div><br>
</div>
<div>What is your opinion?</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Martin </div>
<div><br>
</div>
<div><br>
<div>sent from a phone</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Tagging mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Tagging@openstreetmap.org">Tagging@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/tagging">https://lists.openstreetmap.org/listinfo/tagging</a>
</pre>
</blockquote>
<br>
</body>
</html>