<div dir="ltr"><div class="gmail_quote"><br><div dir="ltr"><div>Hi Simon,</div><div><br></div><div>Yes I'm aware of the dangers of just breaking things with a mass of automated data.</div><div><br></div><div>I was going to start with one boundary, and potentially just trace it to avoid importing problems. But I assume all those IP issues also apply to tracing? The problem with boundaries is they are pure data. You can't see them on the ground or from the air. So surely they are impossible to do without accessing government data.</div><div><br></div><div>Russell</div><span class="HOEnZb"><font color="#888888"><div><br></div></font></span></div><div class="gmail_extra"><div class="gmail_quote"><div><div class="h5">On Mon, Dec 14, 2015 at 8:34 PM, Simon Poole <span dir="ltr"><<a href="mailto:simon@poole.ch" target="_blank">simon@poole.ch</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<div bgcolor="#FFFFFF" text="#000000"><span>
<br>
<br>
<div>Am 14.12.2015 um 03:17 schrieb Russell
Edwards:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi,
<div><br>
</div>
<div>I just wanted to double check before I do this as people
seem to talk casually about using Vicmap Lite data but the OSM
Wiki has a long process to go through with the community
before doing any imports.</div>
</div>
</blockquote>
<br></span>
It should be pointed out that the rules are there for a reason: a
decade of experience that imports are in general screwed up and the
people responsible for them then vanish leaving a mess behind for
others to clean up.<span><br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div><br>
</div>
<div>I have downloaded "Statewide Public Land Classification
boundaries, polygon - 1:250,000 to 1 :2 million. Vicmap Lite".
It is CC BY-4.0-International.</div>
<div><br>
</div>
</div>
</blockquote>
<br></span>
Currently the status of CC BY-4.0 licensed data is unclear, this is
due to some quirks in how the 4.0 version of CC BY works. We are
waiting for CC to get back to the OSMF to clarify. which might
happen in this decade or not. In other words: such data will need
explicit permission for an import.<span><br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div>I want to add boundaries of some local state forests I
frequent, using this data. My questions are</div>
<div><br>
</div>
<div>* Can I just go ahead and do it?</div>
<div>* I haven't done boundaries before, do I need a shared node
where roads and waterways cross the boundary?</div>
<div>* What if there is an existing overlapping area
natural=wood that follows the aerial tree extent (which
doesn't exactly match the boundary)? Leave them both there? Do
I need natural=wood on the state forest boundary area to, to
make it display green? What about the conflict there?</div>
<div>* Anything else to watch for?</div>
<br>
</div>
</blockquote></span>
Landuse imports are notoriously difficult to do correctly, matter of
fact I'm fairly sure that we have never had one which wasn't a
failure in one way or another. If you have never done boundaries
before then you should be doing boundaries before. That will give
you some idea of what you are getting in to and will give you
answers to your questions.<span><font color="#888888"><br>
<br>
Simon<br>
</font></span></div>
<br></div></div><span class="">_______________________________________________<br>
Talk-au mailing list<br>
<a href="mailto:Talk-au@openstreetmap.org" target="_blank">Talk-au@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-au" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-au</a><br>
<br></span></blockquote></div><br></div>
</div><br></div>