<div dir="ltr"><div>You could draw a rectangle reusing all the nodes from the building, or make a relation with the building rectangle, type=multipolygon, role=outer, and put the tags there.<br><br></div>Janko<br></div><br><div class="gmail_quote"><div dir="ltr">sri, 1. srp 2015. u 14:58 André Pirard <<a href="mailto:A.Pirard.Papou@gmail.com">A.Pirard.Papou@gmail.com</a>> napisao je:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Hi,<br>
<br>
An OSM element is normally made of one "physical" object tag and a
number of tags describing the attributes of that object or of the
other attributes (such as (fictitious example)
building:tower:antenna:gsm=yes). This applies to areas and nodes.<br>
Some people prefer to tag the attributes to a node inside an area,
like a shop on a node.<br>
If the node represents a particular place (part) inside the area,
its object tag is simply that of the inside object, like a room, a
reception desk, whatever.<br>
The problem arises when they want their node to represent the whole
area. Supposing a building, they would tag a building=yes node
inside a building=yes area and QAs would complain about finding one
building inside another.<br>
Supposing that substituting another tag for building=yes would play
havoc, what is or would be an additional attribute tag meaning "I am
the same object as that of the area enclosing me", meaning that it's
a duplicate, an alias, you call it, such as:<br>
building=yes<br>
[building:]enclosing_area_alias=yes<br>
<br>
Cheers <br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
<br>
</div>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote></div>