[Talk-ca] Simplifying CanVec imports

[Samuel Longiaru]

I haven't seen any issues with the simplify tool breaking joins or any
errors introduced by its use in the data sets I've been importing but
then I've only been applying it to water features... again, just to get
the data size for streams down to something reasonable.  No other
features seem to need it.  

Maybe I don't understand the process, but I can't see how simplifying
now would have any effect on future imports.  If future versions of
CanVec were provided only as some sort of diff file, and new ways relied
on the existence of certain nodes in a previous data set, then I could
see a potential problem developing.  But otherwise, I don't see how it
would cause any problems for future updating.

Sam


-----Original Message-----
From: Adam Dunn <dunnadam at gmail.com>
To: Samuel Longiaru <longiaru at shaw.ca>
Cc: talk-ca at openstreetmap.org
Subject: Re: [Talk-ca] Simplifying CanVec imports
Date: Sun, 13 Feb 2011 11:37:40 -0800


Does simplifying like this cause issues where one feature joins up
with another feature? I'm assuming that JOSM won't move end nodes of
ways during simplification, so rivers connecting to lakes should be
okay, but what about places where there is a common node in the middle
of a way? Are there instances of this in Canvec, or does the Canvec
conversion process always split ways where there are nodes common to
more than one object?

If you simplify ways today, how will that affect imports in the
future, when the next version of Canvec comes out?

Adam

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