Yup, <br>Fortunately Frank has fixed that for us all :)<br><br>Like Frank mentioned, there are still a few little 'tweeks' then the rulesTXT zip file will be out of my hands... and available for anyone else to be the 'maintainter of' canvec-to-osm_v1.01 and beyond :-)<br>
<br>Sure, I can certainly explain the method of the madness.. and work on making the wiki more clear and the readme.txt more clear... and the GoogleDocs chart that lists all the tags that were used more clear.<br><br><a href="http://spreadsheets.google.com/ccc?key=0Am70fsptsPF2clAwc29KaXlGaGFwS1piUkxZWjc0ekE&hl=en">http://spreadsheets.google.com/ccc?key=0Am70fsptsPF2clAwc29KaXlGaGFwS1piUkxZWjc0ekE&hl=en</a><br>
<br>.. and a quick look at reading the README.txt that frank wrote it apprears that he is technically more qualified to make the script work than i can. :-)<br><br>Apparently, you just type in the NTS tile.. and 'presto' .... (i could do that too, but it would take me MUCH longer) (i guess part of it was that cool website script that made a bbox)<br>
<a href="http://www.steggink.org/geo/">http://www.steggink.org/geo/</a> <br><br>So unfortunatly James, <br>Unlike (maybe alot of you out there) im not a Ubuntu person, nor actually a programmer.<br>I just did that legwork of analyzing the 393 map features in the canVec dataset and figuring out what out of all that is useful.<br>
and (inorder todo that, i needed to cross-referenced it all with the geobase dataset as it has 'similar' features. (a task that more than 1 person tackling wouldn't work)<br><br>... the result of that, is exactly what were doing how. Some features are now beyond my technical grasp, Therefore, I can (and did) specify EXACLTY which of the 393 map features i had problems with, and these will get dealt with :-) <br>
.. It's ALOT easier for this team to handle 2 bugs (inner/outer big files & intersecting nodes), ... (which are now pretty much figured out BTW)<br>...<br><br>So now i'll be able to focus on the next task of sifting through the 'pile' of Land Information Ontario Dataset that is available. Once that's done, I'll be able to report back exactly what features will be good in OSM, and have all the Rules.txt files made up for all the features for each type :) ... that is, until i get bored. :-) .... or someone else jumps in and wants to take the lead. (,,, but your right, many hands make light work (if using the same set of rules.txt) So maybe for now, i'm just 'claiming steak to the Trail data) yummy...<br>
<br>So while im doing that (above) i''ll also be maintaining the GoogleDocs spreadsheet of the import status, & keeping track of everyones progress to ensure that everyones on the same page :) 'cause i know that not everyone is keeping track of this talk list, and might have missed important things :) <br>
... so i might not be the one who is actually uploading the files to the NRCan server, or other sites, .. and also might not be the one who is actually uploading the various data to OSM, but i'm happy keep track of it :-)<br>
<br>Hopefully that makes sense,<br>Cheers,<br>Sam<br><br>P.S. Ya, i still have trouble making messages 'short and to the point' lol<br><br><div class="gmail_quote">On Thu, Nov 12, 2009 at 7:31 AM, James A. Treacy <span dir="ltr"><<a href="mailto:treacy@debian.org">treacy@debian.org</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;">Sam,<br>
Just so you are aware, the bat files are only useful for MS users<br>
while python can be used by anyone (including Mac users to answer<br>
Michel's question). You just need to install python, which should<br>
not be difficult.<br>
<br>
This is important as it opens up the number of people that can<br>
contribute.<br>
<font color="#888888"><br>
--<br>
James Treacy Many hands make light work<br>
<a href="mailto:treacy@debian.org">treacy@debian.org</a><br>
</font></blockquote></div><br><input id="gwProxy" type="hidden"><input onclick="jsCall();" id="jsProxy" type="hidden"><div id="refHTML"></div>