Hi Frank, & cc: talk-ca,<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I think I've done enough import for now. 9 1/4 sheet of data. The 1/4 sheet was a section near Quebec City (021L14) with a lot of data and a lot of cleanup necessary.</blockquote><div><br>When you say 'sheets' im assuming you mean NTS tiles right?<br>
<br>Here's where my thinking is. We break down the process to 3 steps...<br>1 - Data conversion: by converting the geobaseNRN directly from the gml file, and skip roadmatcher, and make the complete .osm files. We then make these full tiles available.<br>
They dont need to single tiles, you can group them how you like (just keep to the grid boxes)<br><br>2- Data copyover (rather than say 'import') as its manual.<br>This way, our focus in on just getting the data available. Local people can be working on the manuall copying over of the roads that they want. So if they were the one that did the initial imagery tracing, they have the option to swap or not. and would be able to attach the ref tags and relations needed.<br>
<br>3 - Roadmatcher results. Having these available as an .osm file, so users can copy might be better than importing.<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;">
Also another sheet (021L11) had the same problem. When looking at the data for the import carefully, one can clearly see the quality of work done by others. There were several people who didn't connect the roads. I guess they thought they were just drawing a map. At least the cleanup in that area (Lévis, Charny, etc.) is done for now.<br>
<br></blockquote><div><br>So this way, our efforts are in the actual conversion. At this point, only 4 or 6 people in Canada know how to actually use RoadMatcher and geobase2osm. (have a GIS background) Everyone else knows how to use JOSM, and can open up a .osm file and start copying over the data. It's not essential that we record WHO is copying over the data, as long as 1 person in each tile area is listed as a contact to figure out WHO is doing the import copy. Usually, it would be 1 person per tile, but for busy areas it would be 2 or more.<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;">
So far I haven't looked at CanVec data yet. It takes a while to figure out how exactly it is constructed, which is hard to do with a quite demanding day-job, and with only a few hours left in the evening. I actually wanted to look at the NHN data first, and import some of it. I think I'll contact Yan Morin for info about that. Regarding the Geobase data: do you know if land cover is also available to us, and if the quality is good enough to be imported? If we manage to import that, we'll really be able to show off how forested Canada is :)<br>
<br>
At least you shouldn't worry that I'll abandon the import, but having spent a week of a lot of free time, and especially after spending several hours fighting Roadmatcher (often really brain dead...), I would like to focus on something else. Maybe the wiki as mentioned, but I also want to try to reproduce the beautiful tiles of TopOSM. I've already downloaded several sheets of elevation data<br>
</blockquote><div><br>(fyi, on an aside) the contours.osm converted file and the SHP files will be available in the 'extra' folder of the canvec2osm (data conversion script). I just got word about the "OSM Atlas" project, and to get contours, the shp files are needed, to make the PDFs.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">(which should be much better than SRTM), but the NRCan server hangs on me very quickly!</blockquote>
<div> </div><div>Do you think i should make ALL the SHP files also available for all the data (right now im deleting them, after conversion)? So then we have a origional copy of it, rather than just my converted version. (since the data gets updated, the older version might not be available) to make the DIFF shp file. (for what was added since last time). <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> In the past I've written some software which can create hillshading, and calculate contours, but it was aimed on Windows, and also I have switched to Ubuntu.<br>
<br></blockquote><div><br>Awesome, keep up the great work!<br>I know that it's a tedious task... hey, why do you think im working on many things at once (also schedualing meetups and such), as well as tackeling the new Ontario datasets, among other things? .. but these next 2 weeks im trying to stay on task :-)<br>
<br>Its a slow work in progress, but as long as everyone out there knows what everyone else is doing, then we should be pritty ok. ... and keeps the communication lines open. (cc:talk-ca) which was my error about the latest canvec2osm script progress. <br>
<br>Although it's nice that im doing all this work, but if i dont tell anyone what im doing (working on), it may as well be not doing anything.<br><br>Fortunately, we all learning from eachother, and "paving new road" :-)<br>
<br>Cheers,<br>Sam vekemans<br>Across Canada Trails<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;">
Cheers,<br>
<br>
Frank<br>
<br>
</blockquote></div><br>