<br><div class="gmail_quote">On Sat, Sep 19, 2009 at 10:18 AM, Richard Weait <span dir="ltr"><<a href="mailto:richard@weait.com">richard@weait.com</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 class="im">On Fri, Sep 18, 2009 at 4:39 PM, Sam Vekemans<br>
<<a href="mailto:acrosscanadatrails@gmail.com">acrosscanadatrails@gmail.com</a>> wrote:<br>
> .... please dont import streams/rivers as they are WRONG... they will be<br>
> made available in the geobaseNHN conversion script. ... and Named features<br>
> file is WRONG (as duplicates exist with other imports)<br>
<br>
</div>Dear Sam,<br>
<br>
Please give me the details on why / how streams and rivers are wrong?<br>
<br></blockquote><div><br>This is explained in the README.txt file. It's available in canvec2osm0_9_1 onward. <br>It a copy of it should be in each of the 16 .zip files of the 020p area.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Please give me the details on where / which data sets duplicate the<br>
named features?<br></blockquote><div><br>The canvec rivers dont include the river names directly on the way, when the geobaseNHN rivers do. And the canvec river names are included as NODES in the named feature set, which is why they need to be omited. Also. the canvec rivers get chopped up at the NTS tile borders, where the GeoBaseNHN polygon is arranged into water basens to show the full length of all the rivers. Therefore it's better to use the geobaseNHN2osm conversion script for that. (which i will be updating after i (we) perfect this canvec2osm script).<br>
<br>I have also included a reference to the 2 GoogleDocs charts (the Import Progress Chart, and the canvec_map_features chart, which still needs community review). ... in the revision of the README.txt<br><br>Cheers,<br>
Sam<br>
<br>P.S. please cc: the talk-ca list so i dont loose my voice in explaining :-)<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Best regards,<br>
<font color="#888888">Richard<br>
</font></blockquote></div><br>