<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.hps
{mso-style-name:hps;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I have wondered about setting up a snapshot-server and loading CanVec on it then setting up a P2 deployment pointing at it.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The problem with splitting by layers is that OSM data is not divided by layers (including planet files). In general if you have interdependent layers and you want to use them with OSM the first step is to merge the layers into one. Now although CanVec appears as multiple independent layers (one .osm file) the underlying data comes from multiple sources (NRN, NHN, etc) so some layer splitting would be possible.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>If I get time I’ll merge together some subtiles to a NTS tile and throw them on my hetzner server. It’s not ideal since it’s in Europe and doesn’t have the disks I’d want, but it’s good enough to serve as a proof of concept.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Pierre Béland [mailto:infosbelas-gps@yahoo.fr] <br><b>Sent:</b> Tuesday, November 13, 2012 12:02 PM<br><b>To:</b> talk-ca@openstreetmap.org<br><b>Cc:</b> Paul Norman; Nicolas Gariépy<br><b>Subject:</b> Import Canvec : micro-tâches / Canvec imports micro-tasking<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal style='margin-bottom:12.0pt;background:white'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>Data import is essential to cover all of Canada, But it is complex to import Canvec files in areas were data already exist. Both unexperienced and experienced people may make errors. Import process is often too complex and too long to realize. <o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>Micro-tasking presently consist of dividing a a NTS grid area in smaller zones. If this micro-tasking was based on layers, I think that this would reduce the complexity of Canvec imports, reduce errors and encourage more people to import. But if necessary because of size, some NTS grids could be subdivided by smaller zones.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>The OSM import files would be divided by layers like it is done for planet files. There could be layers such as roads, poi, landuse, water, forest, coastlines, administrative boundaries, other...). This way, the individual import tasks would be less complex to realize, easier to compare with what already exist. Also, the task would be realized more rapidly.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>When certain type of data such as forests seems less appropriate for a specific area, it would be easy for the mapper to skip this layer. Also, the administrative boundaries and coastlines should be reserved to more experienced people. They could be grouped in a distinct directory and cover larger zones.<o:p></o:p></span></p></div><p class=MsoNormal style='background:white'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><br>I think that we need more than the Google doc to monitor the mapping.<o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>The New Zealand linz2osm tool seems too complex to me. But it can give us some clue about how to develop such a tool.<o:p></o:p></span></p></div><p class=MsoNormal style='background:white'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><br>See linz2osm New Zealand project.<br><a href="http://linz2osm.openstreetmap.org.nz/">http://linz2osm.openstreetmap.org.nz/</a><o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>See Glen Barnes discussion on Import list.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><a href="http://web.archiveorange.com/archive/v/2u2n5O1bELI3yg2ULjry">http://web.archiveorange.com/archive/v/2u2n5O1bELI3yg2ULjry</a><o:p></o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt;background:white'><b><i><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#0000BF'>Pierre </span></i></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><o:p></o:p></span></p></div></div></div></div></body></html>