<html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:10pt"><div>Voir discussion en français / See English discussion below</div><div><br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: arial,helvetica,sans-serif; background-color: transparent; font-style: normal;"><font face="Arial" size="2"> Paul Norman,<font size="2"><font size="2"> s<font size="2">at.</font></font></font> november 2012 6h37<br><b><span style="font-weight: bold;"></span></b></font> Subject : Internal CanVec conflicts<br>> Is it the communities view that it is okay to import CanVec without<br>> reconciling the internal differences between the layers?<br><br>> My view is that importing data without resolving conflicts of this type<br>> where it conflicts with either existing data or internally is not an<br>> acceptable import and indicates the importer did not sufficiently
review<br>> what they were uploading.<br></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: Arial; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: Arial; background-color: transparent; font-style: normal;">---------------------------------------------------------------------------------------------------</div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: Arial; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: Arial; background-color: transparent; font-style: normal;">L'import de données est essentiel, si l'on veut couvrir toute la surface du Canada. Cependant, il est complexe d'importer des fichiers CanVec dans les zones où les données existent déjà. Autant les contributeurs inexpérimentés qu'expérimentés sont susceptibles de faire des erreurs. Le processus
d'importation est souvent trop complexe et trop long à réaliser.<br></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: Arial; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: Arial; background-color: transparent; font-style: normal;"><span id="result_box" class="" lang="fr"><span class="hps">Les micro</span><span class="">-tâches</span> sont <span class="hps">actuellement</span> basées sur les zones géographiques ,chaque<span class="hps"></span> <span class="hps">grille</span> <span class="hps">NTS</span> étant subdivisée en plus petites <span class="hps">zones.</span> En subdivisant par <span class="hps">couche thématique</span><span>, je pense que</span> <span class="hps">cela permettrait de réduire</span> <span class="hps">la complexité</span> <span class="hps">des importations</span> <span class="hps">CanVec</span><span>, de réduire les
erreurs</span> <span class="hps">et d'encourager</span> <span class="hps">plus de gens</span> <span class="hps">à importer.</span></span> Si nécessaire en raison de la taille, certaines grilles pourraient aussi être subdivisée en zones plus petites.<br><br>Tout comme pour les fichiers Planet, les fichiers d'import OSM pourraient être subsiviés par couches telles que routes, poi, landuse, forest, coastlines, limites administratives, autres ...). De cette façon, chaque tâche d'importation serait moins complexe à réaliser, plus facile à comparer avec ce qui existe déjà. En outre, la tâche serait réalisée plus rapidement.<br><br>Lorsque une couche telle que les forêts semble moins approprié pour une région donnée, il serait facile pour le contributeur d'ignorer cette couche. Aussi, les limites administratives et les côtes devraient être réservés à des gens plus expérimentés. Les fichiers pourraient être regroupés
dans un répertoire distinct et couvrir de plus grandes zones.</div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: Arial; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: Arial; background-color: transparent; font-style: normal;">Je pense que nous avons besoin de plus que le fichier Google doc actuel pour assurer le suivi des imports.<br></div>L'outil linz2osm de Nouvelle-Zélande me semble trop complexe. Cependant, il peut nous donner des idées sur la façon de développer un tel outil.<br><br>Voir linz2osm New Zealand project.<br>http://linz2osm.openstreetmap.org.nz/<br><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: Arial; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: Arial; background-color: transparent; font-style: normal;">voir discussion de Glen Barnes,
Import list.</div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: Arial; background-color: transparent; font-style: normal;">http://web.archiveorange.com/archive/v/2u2n5O1bELI3yg2ULjry<br></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: Arial; background-color: transparent; font-style: normal;">---------------------------------------------------------------------------------------------------</div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: Arial; background-color: transparent; font-style: normal;"><br></div>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. <br><br><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: Arial; background-color: transparent; font-style: normal;">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.</div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: Arial; background-color: transparent; font-style: normal;"> <br></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: Arial; background-color: transparent; font-style: normal;">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.</div><div style="color: rgb(0, 0,
0); font-size: 13px; font-family: Arial; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: Arial; background-color: transparent; font-style: normal;">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.<br></div><br>I think that we need more than the Google doc to monitor the mapping.<br><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: Arial; background-color: transparent; font-style: normal;">The New Zealand linz2osm tool seems too complex to me. But it can give us some clue about how to develop such a tool.</div><br>See linz2osm New Zealand project.<br>http://linz2osm.openstreetmap.org.nz/<br><div style="color:
rgb(0, 0, 0); font-size: 13px; font-family: Arial; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: Arial; background-color: transparent; font-style: normal;">See Glen Barnes discussion on Import list.</div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: Arial; background-color: transparent; font-style: normal;">http://web.archiveorange.com/archive/v/2u2n5O1bELI3yg2ULjry<br></div><div> </div><div><span style="font-style:italic;color:rgb(0, 0, 191);font-weight:bold;">Pierre </span><br> <br></div> </div></body></html>