<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 18/03/19 21:32, Lorenzo Stucchi
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:D87FAF8C-599A-4166-A394-3FB0DBE7D391@outlook.it">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div class="">Hi all,</div>
<div class=""><br class="">
</div>
<div class="">Since no more doubts were presented we can think to
propose this tag. </div>
<div class=""><br class="">
</div>
<div class="">Should be better to have 4 different tag proposal
one for every different landcover, one just one considering that
are all connected and there are just the key landcover and 4
different value.</div>
<div class=""><br class="">
</div>
<div class="">Which idea is the best for the proposal?</div>
</blockquote>
4 different.<br>
<br>
I will be voting against most of it. <br>
<br>
In particular<br>
<br>
landcover=cultivation.. it is not a land cover but a human activity.
There is an existing OSM tag of landuse=farmland that looks to me to
be what is being mapped. <br>
<br>
landcover=barren .. does not say what is there. And the proposal
states 3 'equivalent' tags that already inuse and are fairly easy to
map. Why not use them? <br>
<br>
landcover=artificial .. does not say what is there. <br>
<br>
<br>
For the deforestation the above do not contribute to the
documentation of the existence of trees so they have no impact on
the deforestation itself. They may contribute to theorising on the
causes of deforestation.<br>
I think these tags are simply to ease the task, to make it easier
... OSM is not about easier, it is about mapping. <br>
<br>
<blockquote type="cite"
cite="mid:D87FAF8C-599A-4166-A394-3FB0DBE7D391@outlook.it">
<div class=""><br class="">
</div>
<div class="">Best,</div>
<div class="">Lorenzo</div>
<div class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">Il giorno 16 mar 2019, alle ore 09:07, Lorenzo
Stucchi <<a href="mailto:lorenzostucchi95@outlook.it"
class="" moz-do-not-send="true">lorenzostucchi95@outlook.it</a>>
ha scritto:</div>
<br class="Apple-interchange-newline">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode:
space; line-break: after-white-space;" class="">
Hi,
<div class=""><br class="">
</div>
<div class="">The idea is for sure to check the date of
the imagery and map when new imagery are available and
we can consider also the time step between the
different satellite imagery.</div>
<div class=""><br class="">
</div>
<div class="">The fact that some contributor modify the
data is not a problem because they will done adding
new information and this is just an improvement in the
data.</div>
<div class=""><br class="">
</div>
<div class="">Think like they are highway, I can’t known
what is the type of the highway but I can cleary see
that its a road, so I can map it as highway=road with
all the problem of this case. But un other user with
better knowledge can identify which type of highway. </div>
<div class="">In a similar way there is just a different
structure of classification, and when better imagery
or generally better info are available the tag
landcover will be improved with the more detailed tag.</div>
<div class=""><br class="">
</div>
<div class="">For what regards the history I’m agree
with Martin.</div>
<div class=""><br class="">
</div>
<div class="">Best,</div>
<div class="">Lorenzo</div>
<div class=""><br class="">
<div class=""><br class="">
<blockquote type="cite" class="">
<div class="">Il giorno 15 mar 2019, alle ore
08:32, Joseph Eisenberg <<a
href="mailto:joseph.eisenberg@gmail.com"
class="" moz-do-not-send="true">joseph.eisenberg@gmail.com</a>>
ha scritto:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
<div
style="word-wrap:break-word;line-break:after-white-space"
class="">
<div class="">> “The idea is to have
mapathon in </div>
</div>
</blockquote>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
<div
style="word-wrap:break-word;line-break:after-white-space"
class="">
<div class="">> different time, when
new imagery are</div>
</div>
</blockquote>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
<div
style="word-wrap:break-word;line-break:after-white-space"
class="">
<div class="">> available and after
check what</div>
</div>
</blockquote>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
<div
style="word-wrap:break-word;line-break:after-white-space"
class="">
<div class="">> changed searching in
the database</div>
</div>
</blockquote>
<div dir="auto" class=""><br class="">
</div>
<div dir="auto" class="">In this case you only
need to map the area of woodland or forest
now, and it’s no problem to leave other
landuse and natural areas unmapped.</div>
<div dir="auto" class=""><br class="">
</div>
<div dir="auto" class="">But it may be
difficult to use the OSM database for
checking changes over time, if you would
like scientific, publishable results.</div>
<div dir="auto" class=""><br class="">
</div>
<div dir="auto" class="">To properly compare
the current woodland area with the area in a
couple of years, you will need to make sure
that the aerial imagery that you use now is
all from the same year. </div>
<div dir="auto" class=""><br class="">
</div>
<div dir="auto" class="">Then, when you repeat
the project in 1 or 2 years, you need to
have new imagery from around the same time,
and you should map the woodland or forested
areas using the same standard and methods as
they first time. This will be easiest if you
remap everything from scratch the second
time as well.</div>
<div dir="auto" class=""><br class="">
</div>
<div dir="auto" class="">If you try to use the
OSM database both times, you may find that
other mappers have changed things in the
meantime. Perhaps they have changed some of
your landuse=forest to natural=wetland
wetland=mangrove, because they know the area
better. Perhaps they have mapped a new palm</div>
<div dir="auto" class="">oil plantation based
on local information, but it isn’t visible
in the aerial imagery. How will you deal
with such changes?</div>
<div dir="auto" class=""><br class="">
</div>
<div dir="auto" class="">So it is great to add
the forest or wood areas to OSM right now
based on the latest aerial imager. </div>
<div dir="auto" class=""><br class="">
</div>
<div dir="auto" class="">But you should plan
to keep your own copy of the database to
compare with and edit in the future. If you
do this right it could be
professionally-quality data for
environmental research, but that means you
need to keep a copy of the data that won’t
change, and use that for comparison in the
future.</div>
<div dir="auto" class=""><br class="">
</div>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
<div
style="word-wrap:break-word;line-break:after-white-space"
class="">
</div>
</blockquote>
</div>
_______________________________________________<br
class="">
Tagging mailing list<br class="">
<a href="mailto:Tagging@openstreetmap.org"
class="" moz-do-not-send="true">Tagging@openstreetmap.org</a><br
class="">
<a
href="https://lists.openstreetmap.org/listinfo/tagging"
class="" moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/tagging</a><br
class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
_______________________________________________<br
class="">
Tagging mailing list<br class="">
<a href="mailto:Tagging@openstreetmap.org" class=""
moz-do-not-send="true">Tagging@openstreetmap.org</a><br
class="">
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/tagging">https://lists.openstreetmap.org/listinfo/tagging</a><br
class="">
</div>
</blockquote>
</div>
<br class="">
</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>
<p><br>
</p>
</body>
</html>