Interesting ideas.<br><br>Great to see i diagram explaining the different approaches.<br>I also want to point out that the WMS layer for all of this data is available, so it is possable to trace over it, so to get the map features that way. This option is handy for working on areas of high density, where loading the .osm file would make it harder to see exactly what features are needed.<br>
<br>
I would go for the 3rd option<br><br><i>Partial integration model</i>: all geometries are complete by
themselves. Integration at coordinate level eliminates duplicate nodes.
Overlapping lines segments are duplicated. The model however allows the
selection of a subset of entities for data import.<br><br><div class="gmail_quote">As this allows for more maneuverability, and deeper the integration with other features. We know that most of the road network has already been imported, as that requires a different process. For roads that are missing, it seems just as easy to trace over.<br>
<br>When importing on Vancouver island i found that having the features separate was best, since we like to have room to expand & add in more features. ie. if there is a fence around a wooded area & between the water, we would want to map out those also.<br>
<br>Because these are 2 seperatate features, they should not be joined at the hips. And it's OK to have the polygons lined up end to end.<br><br>Im working a little bit in Princeton, BC<br><a href="http://www.openstreetmap.org/?lat=49.45842&lon=-120.50942&zoom=15&layers=B000FTF">http://www.openstreetmap.org/?lat=49.45842&lon=-120.50942&zoom=15&layers=B000FTF</a><br>
Where you can see that i was tracing from the Toporama WMS layer. Once the number of ways started to get to big, i connected it across the river to make a full polygon. <br><br>Remembering that we 'dont map for the renderer' you can see that you cant tell were it was that i made the plit. I still wanted to get the detail, but having it all as 1 big huge river polygon wouldn't make sence. I only wanted to map the in-town portion of it. Once the .osm files become available, then i can select only that large polygon & slice it so it doesnt interfer with my tracing work. <br>
<br>The fact that there is the river-bank area & some sand areas along, it will be fine to copy those polygons directly onto the map.<br><br>So in sum, regarding duplicate ways/nodes. I only see it as a duplicate when the way/node is part of the SAME feature. If it is connected to another feature, then i dont see that as a duplicate.<br>
... but that's just me. .. unless someone else has a better explaination?<br><br><br>Cheers,<br>Sam<br><br>On Wed, Mar 10, 2010 at 6:04 AM, Bégin, Daniel <span dir="ltr"><<a href="mailto:Daniel.Begin@rncan-nrcan.gc.ca">Daniel.Begin@rncan-nrcan.gc.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div><font size="2" face="Arial"><span>Bonjour tout le
monde,</span></font></div>
<div><font size="2" face="Arial"><span></span></font> </div>
<div><font face="Arial"><span><font size="2">I've started
to document the Canvec.osm product in the wiki. <span>I'll use the Canvec related pages to do it
</span></font></span></font><font face="Arial"><a href="http://wiki.openstreetmap.org/wiki/CanVec" target="_blank"><font size="2">http://wiki.openstreetmap.org/wiki/CanVec</font></a><font size="2">.</font></font></div>
<div><font face="Arial"><font size="2"></font></font> </div>
<div><font face="Arial"><font size="2">T<span>he geometric data model is open for discussion <a href="http://wiki.openstreetmap.org/wiki/CanVec:_Geometric_Model" target="_blank">http://wiki.openstreetmap.org/wiki/CanVec:_Geometric_Model</a></span></font></font></div>
<div><font face="Arial"><font size="2"><span></span></font></font> </div>
<div><font face="Arial"><font size="2"><span>The proposed
tagging will be updated soon in the corresponding Canvec:* pages
</span></font></font></div>
<div><font face="Arial"><font size="2"><span></span></font></font> </div>
<div><font face="Arial"><font size="2"><span>I'm inviting
you to look at the documentation and comment on appropriate discussion pages on
via this mailling list.</span></font></font></div>
<div><font face="Arial"><font size="2"><span></span></font></font> </div>
<div><font face="Arial"><font size="2"><span>Cheers,</span></font></font></div>
<div><font face="Arial"><font size="2"><span></span></font></font> </div>
<div><font face="Arial"><font size="2"><span>Daniel</span></font></font></div>
<div><font face="Arial"><font size="2"><span></span></font></font> </div>
<div><font size="2" face="Arial"></font> </div>
<div><font size="2" face="Arial"></font> </div>
<div><font size="2" face="Arial"></font> </div></div>
<br>_______________________________________________<br>
Talk-ca mailing list<br>
<a href="mailto:Talk-ca@openstreetmap.org">Talk-ca@openstreetmap.org</a><br>
<a href="http://lists.openstreetmap.org/listinfo/talk-ca" target="_blank">http://lists.openstreetmap.org/listinfo/talk-ca</a><br>
<br></blockquote></div><br><input id="gwProxy" type="hidden"><input onclick="jsCall();" id="jsProxy" type="hidden"><div id="refHTML"></div>