<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 6/5/22 23:26, Peter Elderson wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAKf=P+s1dMF=r==kkwFXOyTYcW8efVz_Ds5Qtc3OPyXfUKjAcA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">I'm not suggesting any deprecation. Just an idea to
add a natural, intuïtive and easy way to tag existing land use
with different land cover. Say, grass on a railway area. I'm
running into this kind of issue every time I do some tagging in
my neighbourhood.
<div><br>
</div>
<div>Without adding new keys, using elements already present. no
deprecations or retaggings, just a refinement, and not
requiring any intricate handling. </div>
<div><br>
</div>
<div>I see even this revives several trench wars. Sorry I asked!</div>
</div>
</blockquote>
<p><br>
</p>
<p>Unfortunately most are fixed into their trenches and won't
consider change. <br>
</p>
<p><br>
</p>
<p>landuse=grass is one that is stuck firmly in a very deep hole! If
that can be moved I'd be very impressed. It is a far larger
obstacle and leads to other covers being accidentally tagged as
land use, and then repeated by that mapper. Teaching new mappers
landuse=grass but not to use it for other land covers just
confuses them. <br>
</p>
<p><br>
</p>
<p>I don't see much to be gained by adding natural=trees when
natural=wood looks to be much the same thing - trees.</p>
<p><br>
</p>
<p>I don't see the landcover key being much of a problem - most of
these would be dual tagged - landcover as a sensible key the other
is simply tagging for the render. <br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:CAKf=P+s1dMF=r==kkwFXOyTYcW8efVz_Ds5Qtc3OPyXfUKjAcA@mail.gmail.com">
<div dir="ltr">
<div>
<div>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature"><br>
</div>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">Peter Elderson</div>
</div>
<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Op vr 6 mei 2022 om 14:16
schreef Mateusz Konieczny via Tagging <<a
href="mailto:tagging@openstreetmap.org"
moz-do-not-send="true" class="moz-txt-link-freetext">tagging@openstreetmap.org</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>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>May 6, 2022, 12:24 by <a
href="mailto:pelderson@gmail.com" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">pelderson@gmail.com</a>:<br>
</div>
<blockquote style="border-left:1px solid
rgb(147,163,184);padding-left:10px;margin-left:5px">
<div dir="ltr">
<div>It's going off in all directions again...<br>
</div>
<div><br>
</div>
<div>I asked: <br>
</div>
<div>What about the idea of supporting the proposed
landcover values to the natural key?<br>
</div>
<div><br>
</div>
<div>That is: for the natural key, support the values
grass and trees.<br>
</div>
</div>
</blockquote>
<div dir="auto">deprecating landuse=grass and replacing it
with natural=grass?<br>
</div>
<div dir="auto">I see no real benefit here.<br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">The same goes to adding third confusing
synonym to landuse=forest<br>
</div>
<div dir="auto">and natural=wood (to close to natural=tree)<br>
</div>
<div dir="auto"><br>
</div>
<blockquote style="border-left:1px solid
rgb(147,163,184);padding-left:10px;margin-left:5px">
<div dir="ltr">
<div>It just solves the issue that you can't map land
cover and land use for the same feature if landuse is
used for land cover. <br>
</div>
</div>
</blockquote>
<div dir="auto">there is no such issue, you can map this
with overlapping areas<br>
</div>
<div dir="auto"><br>
</div>
</div>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></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>