<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#333399" bgcolor="#FFFFFF">
<p><font face="Verdana">Thank you for the clarification Martin, so
if I understand you clearly, it is not a role, as we don't want
strict roles that restrict mappers, OSM needs to be as free as
possible.<br>
The one feature - one element is a "Guideline" or "Good
Practice"<br>
One main or top-level tag is also a "Guideline" or "Good
Practice", however not (yet) clearly as a separate guideline
defined in our wiki (volunteers to improve it ?)</font></p>
<p><font face="Verdana">And if you allow me to be bold a policy
statement regarding tagging proposals and wiki pages:<br>
We should define proposals and describe tagging and mapping
principles that support the "Guidelines" and "Good Practices" to
the maximum extend. However they are not strict roles,
proposals and wiki page text should be setup in this context to
promote or offer examples to support them to the maximum extend.
Proposals or descriptions that contradict these "guidelines" and
"Good Practice" are considered as less compliant and/or of less
quality and should be rephrased, rewritten or redesigned. It is
advised to always find a consensus from the community to
nominate a proposal or wiki page to be rewritten due to
non-compliance with these "Guidelines" or "Good Practices".<br>
Non-compliance with the "Guidelines" or "Good Practices" should
never be the reason to reject a proposal or delete a wiki page.
It should be a motivation or advise to rewrite a proposal and
non-compliant wiki pages can be marked as "not good practice"
description and thus be nominated (after community consensus)
for improvement.</font></p>
<p><font face="Verdana">Greetings, Bert Araali</font></p>
<p><font face="Verdana"><br>
</font></p>
<div class="moz-cite-prefix">On 15/02/2021 12:08, Martin
Koppenhoefer wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CABPTjTCynyhO1_bQbvpZnoTC5HvVchbT_+c2T0H=QXQT8c=aTA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr"><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Am So., 14. Feb. 2021 um
21:42 Uhr schrieb Bert -Araali- Van Opstal <<a
href="mailto:bert.araali.afritastic@gmail.com"
moz-do-not-send="true">bert.araali.afritastic@gmail.com</a>>:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p><font face="Verdana">Is this a role or a guideline
then, not clear to me, how do we call it?</font></p>
<p><a
href="https://wiki.openstreetmap.org/wiki/One_feature,_one_OSM_element"
target="_blank" moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/One_feature,_one_OSM_element</a></p>
</div>
</blockquote>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>I don't recall if this was discussed, but the requirement
to have only one "main" tag was introduced just "recently"
(less than 2 years ago) to this page: <br>
</div>
<div><a
href="https://wiki.openstreetmap.org/w/index.php?title=One_feature%2C_one_OSM_element&type=revision&diff=1873923&oldid=1873154"
moz-do-not-send="true">https://wiki.openstreetmap.org/w/index.php?title=One_feature%2C_one_OSM_element&type=revision&diff=1873923&oldid=1873154</a></div>
<div><br>
</div>
<div>The rule is "one feature should be represented only by one
element in OSM", and one element means a way, a node or a
relation. This rule still leaves a lot of room for
interpretation, for example you could still have the area of a
city mapped as place=city on a polygon and at the same time
have a node with place=city for the same city, if you argue
that this means the centre of a city. It all depends on what
we agree that the tags represent, and what we consider a
"feature". </div>
<div><br>
</div>
<div>Having only one main tag on an object would be a different
rule, and I find it somehow misleading to "hide" this under
the headline "one feature one element". <br>
</div>
<div><br>
</div>
<div>Clearly the one tag-rule is not currently followed, you can
find millions of objects tagged as building=* plus something
like amenity=* or shop=*, office=* etc. or barrier=* together
with tags for an area, like landuse, amenity etc.</div>
<div>If you look at the combinations of man_made=* there are
also 1,67% combinations with highway (what's that?). 0,89%
with natural, 0,85% with amenity, 0,77% with historic, 0,55%
with barrier, 0,52% with power, etc. <br>
</div>
<div><a
href="https://taginfo.openstreetmap.org/keys/man_made#combinations"
moz-do-not-send="true">https://taginfo.openstreetmap.org/keys/man_made#combinations</a>
To be fair, the paragraph says "ideally", so it is not a
strict rule, more a suggestion.<br>
</div>
<br>
<div>You could also say: "phone=*" means a telephone connection,
and then this tag, normally a property, becomes a "feature".
Or addr:housenumber could be seen as a property, or as a
feature, depending on your interpretation and on the context
(other tags).</div>
<div><br>
</div>
<div>Cheers,<br>
</div>
<div>Martin<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-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>
</body>
</html>