[Talk-ca] NRCan lakes

[Adam Martin]

As mentioned by Daniel, this is due to the nature of the CANVEC data
import.  CANVEC shapefile data is based on tiles and these will chop
practically anything into pieces - lakes are just ones of the more
noticeable.  I have corrected some of these myself as I've come across
them.  Just be careful in cases where the lake pieces are part of different
relations in the area - you will need to adjust those to make sure nothing
breaks.

Adam

On Tue, Jul 7, 2020 at 2:33 AM Hannes Röst <hannesroest at gmx.ch> wrote:

> Hello
>
> I am a contributor from Toronto and I have a question regarding how to
> treat some of the CanVec 6.0 - NRCan imports, specifically for lakes.
> I came across this lake here:
>
> https://www.openstreetmap.org/way/69275451
> https://www.openstreetmap.org/way/69277932
> https://www.openstreetmap.org/way/69745752
>
> Which is strangely split up into 3 parts and I wonder how to proceed:
> should we fix this and create a single way out of these 3 parts or is
> it beneficial (for comparison to future NRCan database entries) to
> keep them that way and create a relation out of the three? Also, does
> somebody know why the NRCan dataset does this, is this an import
> artefact (splitting into tiles?) and should be corrected when encountered
> or is it part of the original dataset?
>
> Best
>
> Hannes Rost
>
> _______________________________________________
> Talk-ca mailing list
> Talk-ca at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ca
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-ca/attachments/20200707/77761600/attachment.htm>