<div dir="ltr">I tend to agree. I would suggest that anyone contemplating importing CanVec land cover data should first spend some time picking any arbitrary area of land cover in northern Canada and spend time fixing errors and aligning the polygons to what's on the map. After spending a few hours banging your head against the wall trying to fix geometry errors and nonsensical polygons, THEN let's have the conversation about what makes sense :)</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Aug 31, 2022 at 12:36 PM Nate Wessel <<a href="mailto:bike756@gmail.com">bike756@gmail.com</a>> wrote:<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>
<p>John, that's bad advice. An import that introduces new errors is
not a good import. I do hope we can all agree on that. It's an
importer's job to resolve errors, not to leave a mess for others
to clean up. <br>
</p>
<p>...</p>
<p>I was meaning to reply to this anyway. I would tend to be on the
side of not importing CanVec data; the gaps are ugly, yes, but
maybe those imports never should have been done in the first
place; I don't have a strong position on that. Regardless, as
these areas aren't really getting filled in by many actual
editors, it seems quite likely that the imported data will just
continue to grow stale over the years. Better to know what we
don't know than to think we know what we don't.<br>
</p>
<p>Also, if anyone wants to make a map with a bunch of natural
landcover data, they're probably better off using raster sources
than vector data, especially outside of urban areas. IMO, OSM was
never going to be well suited to Canada's north. That's raster
data territory and OSM has a vector data model. <br>
</p>
<p>That said, I have actually been editing a bit up north lately,
and making some actual progress adding rivers and lakes and
whatnot - I'd definitely welcome some manual help!<br>
</p>
<p>Cheers,<br>
</p>
<div>
<p> Nate Wessel<br>
<small> Cartographer, Planner, Transport Nerd<br>
<a href="https://www.natewessel.com" style="text-decoration:none" target="_blank"> NateWessel.com </a> </small>
</p>
</div>
<div>On 2022-08-31 12:14, John Whelan wrote:<br>
</div>
<blockquote type="cite">
I'd tend to just import and ignore the errors. An area can be
both wetland and wood. Errors do get sorted out over time.<br>
<br>
Cheerio John<br>
<br>
<span>William Davis via Talk-ca wrote on 8/31/2022 11:56 AM:</span><br>
<blockquote type="cite">On
2022-08-31 03:02, William Davis via Talk-ca wrote: <br>
<blockquote type="cite">I've been looking at the osm homepage a
lot recently and the big blocks of white space next to the
green CanVec imports look really ugly, especially when
compared to New Brunswick. I've tried importing CanVec data in
the past (about 2 years ago), which did not end well since I
had barely used JOSM before then. People also seemed to always
be complaining about how hard and annoying it was to import
CanVec data, even in completely blank areas, such as up north.
<br>
<br>
So I guess my question is whether it is worth trying to import
CanVec data over improving my local area, especially since it
seems the OSM Canada community as a whole has given up on that
idea.
<br>
<br>
-- <br>
William Davis
<br>
<br>
_______________________________________________
<br>
Talk-ca mailing list
<br>
<a href="mailto:Talk-ca@openstreetmap.org" target="_blank">Talk-ca@openstreetmap.org</a>
<br>
<a href="https://lists.openstreetmap.org/listinfo/talk-ca" target="_blank">https://lists.openstreetmap.org/listinfo/talk-ca</a>
<br>
</blockquote>
I've tried importing some data, but I'm just not experienced
enough to know what to do with all the different errors that the
CanVec data contains, especially when I try and do something
outside of the north. <br>
Does anyone here have experience importing canvec? The error I
get most often that I don't know how to solve is when there are
duplicate ways with different tags (e.g. natural=wood and
natural=wetland). <br>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Talk-ca mailing list
<a href="mailto:Talk-ca@openstreetmap.org" target="_blank">Talk-ca@openstreetmap.org</a>
<a href="https://lists.openstreetmap.org/listinfo/talk-ca" target="_blank">https://lists.openstreetmap.org/listinfo/talk-ca</a>
</pre>
</blockquote>
<br>
<div>-- <br>
<div>Sent from <a href="https://www.postbox-inc.com" target="_blank"><span style="color:rgb(0,157,247)">Postbox</span></a></div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
Talk-ca mailing list
<a href="mailto:Talk-ca@openstreetmap.org" target="_blank">Talk-ca@openstreetmap.org</a>
<a href="https://lists.openstreetmap.org/listinfo/talk-ca" target="_blank">https://lists.openstreetmap.org/listinfo/talk-ca</a>
</pre>
</blockquote>
</div>
_______________________________________________<br>
Talk-ca mailing list<br>
<a href="mailto:Talk-ca@openstreetmap.org" target="_blank">Talk-ca@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-ca" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-ca</a><br>
</blockquote></div>