[Talk-ca] Simplifying CanVec imports

[Bégin, Daniel]

Bonjour Samuel, and all
 
Samuel wrote: "If future versions of Canvec were provided only as some sort of diff file..."
 
I'm still working on the application that will generate differences between Osm and Canvec. It will be based on node/way association probability. So, removing/displacing a node (even many nodes) wont make any difference on the overall probability.
 
There is no plan to provide a diff file that shows differences between two version of a Canvec file
 
Cheers,
Daniel
________________________________

From: Samuel Longiaru [mailto:longiaru at shaw.ca] 
Sent: February 13, 2011 17:31
To: talk-ca
Subject: Re: [Talk-ca] Simplifying CanVec imports


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 <mailto:Adam%20Dunn%20%3cdunnadam at gmail.com%3e> >
To: Samuel Longiaru <longiaru at shaw.ca <mailto:Samuel%20Longiaru%20%3clongiaru at shaw.ca%3e> >
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/20110214/065bce84/attachment.html>