<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Yes, you didn't misread it, it's about a Boundary import aka
boundary=protected_area.<br>
</p>
<p>As it reads in the dataset description, "Last Revised in 2020 for
USGS's Protected Areas Database, a subset of the National Gap
Analysis project." So it means I'm gonna work with pretty decent
data which is a good thing, and i checked the quality of the
dataset, I only need to do some minor multipolygon editing, i
already set up the tagging, so yeah, i'm not gonna import it like
an idiot but like i have proper knowledge how to, after some
research of how the taggings work. The taggings of the dataset is
based on the PAD US scheme, for which WV GIS TC provided a PDF
file to explain what tag does what.</p>
<p>I haven't started it yet, but i guess you all say that i should
be good to go if I do it carefully, but that's why I wanted to
hear from you.</p>
<p>I created a <a moz-do-not-send="true"
href="https://www.openstreetmap.org/user/ottwiz_import">separate
account </a>just for the import itself so it's distinguished
from my main one.<br>
</p>
<div class="moz-cite-prefix">On 8/12/2021 4:52 PM, Adam Franco
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAMN3sBf31G_9yswczpXrTSvVs53bM0f5i-t8ZECXEr2UcAd+sg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
> On 12 Aug 2021, at 08:38, Mateusz Konieczny via Imports
<<a href="mailto:imports@openstreetmap.org"
target="_blank" moz-do-not-send="true">imports@openstreetmap.org</a>>
wrote:<br>
I disagree. For simple polygons (few nodes), overlapping
ways might be the easiest to maintain representation, but as
an editor I would always prefer a multipolygon to tens or
hundreds of reused/overlapping nodes in overlapping ways.<br>
</blockquote>
<div>As a heavy land-cover mapper I agree that multipolygons
are vastly easier to improve over time than to try to
disconnect overlapping ways.</div>
<div><br>
</div>
<div>That said, unless I'm misreading the wiki the i<a
href="https://wiki.openstreetmap.org/wiki/Import/West_Virginia_State_Forests_Import"
moz-do-not-send="true">mport being discussed</a> is about
State Forest (protected area) boundaries not
land-cover/land-use. I'd rather not have folks doing
land-cover/land-use imports from poor data, but I'm of the
opinion that protected area boundaries are often a very good
candidate for [careful] importing if the data are of good
quality.<br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Imports mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Imports@openstreetmap.org">Imports@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/imports">https://lists.openstreetmap.org/listinfo/imports</a>
</pre>
</blockquote>
</body>
</html>