[Talk-ca] Simplifying CanVec imports

[Samuel Longiaru]

Yes, the import seems to be quite a selective process!  Very tedious at
times.  And now that I am getting into areas where there actually is
some existing OSM data and I have spent so much time hand editing in the
past, I'm pretty careful to select the better data on a way-by-way
basis.  Sometimes the CanVec data wins out, sometimes not.

In regards to simplifying, however, I am quite pleased to note that I
have not seen displacement or removal of a node that sits at the edge of
a tile.  I'm sure they are just taken as end points. Simplifying a
feature that will ultimately run from one tile to the next still yields
duplicate nodes at the boundary when the next file is brought in.  The
stitching procedure is the exactly the same.  Merge nodes and combine
ways where appropriate.  I just think it is a great tool that admittedly
may only have limited applications.  But I think that this situation is
definitely one of them.

Sam




-----Original Message-----
From: john whelan <jwhelan0112 at gmail.com>
To: Talk-CA OpenStreetMap <talk-ca at openstreetmap.org>
Cc: Samuel Longiaru <longiaru at shaw.ca>
Subject: Re: [Talk-ca] Simplifying CanVec imports
Date: Sun, 13 Feb 2011 18:41:21 -0500

There are always issues when you want to replace one set of data with
another.  People may have added labels such as the name in French,
replace the import and you lose the French.

Where the CANVEC tiles meet ways are connected by overlapping points.
Any simplification at this point that moves a point on a way means the
way doesn't get joined where the tiles meet.

This is why it''s so tempting to start over from CANVEC 7 then add in
the detail, amenities, shops etc.  At least you can have confidence that
the road names are correct.

Cheerio John



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-ca/attachments/20110213/173eaeff/attachment.html>