<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Thumbs up for this idea. I didn't think about it before.<br>
      <br>
      Alright, if any of you can take the chance to look at my data
      prep, please do it then, and say what should i improve based on
      the info I provided, I'd be grateful to hear. Sterling hasn't
      taken the chance to check it out, probably because he is busy with
      college business but he reacted with 'aye-aye' in private messages
      when i told him that he is also gonna check the files (i sent him
      the exact same instructions and description what's what)<br>
    </p>
    <p>But most of you are experienced mappers so it should be easy to
      sort it out.<br>
    </p>
    <div class="moz-cite-prefix">On 8/13/2021 9:40 AM, Mateusz Konieczny
      via Imports wrote:<br>
    </div>
    <blockquote type="cite" cite="mid:MgySEXo--3-2@tutanota.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div>Or add extra changeset tag <br>
      </div>
      <div dir="auto">wiki_documentation=LINK TO WIKI<br>
      </div>
      <div><br>
      </div>
      <div><br>
      </div>
      <div>Aug 12, 2021, 18:55 by <a class="moz-txt-link-abbreviated" href="mailto:clifford@snowandsnow.us">clifford@snowandsnow.us</a>:<br>
      </div>
      <blockquote class="tutanota_quote" style="border-left: 1px solid
        #93A3B8; padding-left: 10px; margin-left: 5px;">
        <div dir="ltr">I like to point the changeset source to the wiki
          import page. <br>
        </div>
        <div><br>
        </div>
        <div class="">
          <div class="" dir="ltr">On Thu, Aug 12, 2021 at 8:59 AM Attila
            Kun <<a href="mailto:attila@attilakundev.com"
              rel="noopener noreferrer" target="_blank"
              moz-do-not-send="true">attila@attilakundev.com</a>>
            wrote:<br>
          </div>
          <blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px
            solid rgb(204,204,204);padding-left:1ex" class="">
            <div>
              <p>Also i got the question in mind, what should be the
                source tagging?<br>
              </p>
              <p>I set up a long tagging for the exact source for the
                changesets(<span class="font"
                  style="font-family:monospace">source="<a
                    target="_blank"
                    href="https://wvgis.wvu.edu/data/dataset.php?ID=58"
                    rel="noopener noreferrer" moz-do-not-send="true">https://wvgis.wvu.edu/data/dataset.php?ID=58</a>
                  discussed with #local-west-virginia on OSM US Slack
                  and imports mailing list" </span>), but shouldn't I
                just  write<span class="font"
                  style="font-family:monospace"> source=WV GIS Tech
                  Center; WVDoF</span> instead of it?<br>
              </p>
              <p>Because that would make everything easier, and it's
                gonna be documented on wiki nevertheless...<br>
              </p>
              <div>On 8/12/2021 5:26 PM, Attila Kun wrote:<br>
              </div>
              <blockquote type="cite">
                <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.<br>
                </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.<br>
                </p>
                <p>I created a <a target="_blank"
                    href="https://www.openstreetmap.org/user/ottwiz_import"
                    rel="noopener noreferrer" moz-do-not-send="true">separate
                    account </a>just for the import itself so it's
                  distinguished from my main one.<br>
                </p>
                <div>On 8/12/2021 4:52 PM, Adam Franco wrote:<br>
                </div>
                <blockquote type="cite">
                  <div dir="ltr">
                    <div class="">
                      <blockquote style="margin:0px 0px 0px
                        0.8ex;border-left:1px solid
                        rgb(204,204,204);padding-left:1ex" class="">
                        <div>> On 12 Aug 2021, at 08:38, Mateusz
                          Konieczny via Imports <<a target="_blank"
                            href="mailto:imports@openstreetmap.org"
                            rel="noopener noreferrer"
                            moz-do-not-send="true">imports@openstreetmap.org</a>>
                          wrote:<br>
                        </div>
                        <div> 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>
                        </div>
                      </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.<br>
                      </div>
                      <div><br>
                      </div>
                      <div>That said, unless I'm misreading the wiki the
                        i<a target="_blank"
href="https://wiki.openstreetmap.org/wiki/Import/West_Virginia_State_Forests_Import"
                          rel="noopener noreferrer"
                          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>
                  <div><br>
                  </div>
                  <pre>_______________________________________________
Imports mailing list
<a target="_blank" href="mailto:Imports@openstreetmap.org" rel="noopener noreferrer" moz-do-not-send="true">Imports@openstreetmap.org</a>
<a target="_blank" href="https://lists.openstreetmap.org/listinfo/imports" rel="noopener noreferrer" moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/imports</a>

</pre>
                </blockquote>
                <div><br>
                </div>
                <pre>_______________________________________________
Imports mailing list
<a target="_blank" href="mailto:Imports@openstreetmap.org" rel="noopener noreferrer" moz-do-not-send="true">Imports@openstreetmap.org</a>
<a target="_blank" href="https://lists.openstreetmap.org/listinfo/imports" rel="noopener noreferrer" moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/imports</a>

</pre>
              </blockquote>
            </div>
            <div>_______________________________________________<br>
            </div>
            <div> Imports mailing list<br>
            </div>
            <div> <a target="_blank"
                href="mailto:Imports@openstreetmap.org" rel="noopener
                noreferrer" moz-do-not-send="true">Imports@openstreetmap.org</a><br>
            </div>
            <div> <a target="_blank" rel="noopener noreferrer"
                href="https://lists.openstreetmap.org/listinfo/imports"
                moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/imports</a><br>
            </div>
          </blockquote>
        </div>
        <div><br>
        </div>
        <div><br>
        </div>
        <div>-- <br>
        </div>
        <div class="" dir="ltr">
          <div dir="ltr">
            <div>
              <div dir="ltr">
                <div>
                  <div dir="ltr">
                    <div>@osm_washington<br>
                    </div>
                    <div><a target="_blank"
                        href="https://www.snowandsnow.us" rel="noopener
                        noreferrer" moz-do-not-send="true">www.snowandsnow.us</a><br>
                    </div>
                    <div>OpenStreetMap: Maps with a human touch<br>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </div>
        </div>
      </blockquote>
      <div dir="auto"><br>
      </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>