<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=us-ascii">
<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin-top:0cm;
margin-right:0cm;
margin-bottom:10.0pt;
margin-left:0cm;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
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.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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-CA" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Bonjour groupe,<o:p></o:p></p>
<p class="MsoNormal">The pre-processing procedure has been tested for the Squamish (BC) area. Squamish has a small number of buildings (6K) with a good Esri World imagery which need to be aligned with ODB data. A large number of ODB buildings show an inaccurate
delineation (shaky drawing with too many nodes). Orthogonalization worked great but the result is not perfect because of the quality of the data. About 10% of the nodes were removed from the dataset. It contains all the problems we may encounter during this
import. Consequently, I suggest that the import procedure be discussed and documented in detail using this case.<o:p></o:p></p>
<p class="MsoNormal">I could identify myself as the local import manager, but I would much prefer someone from the area to volunteer. When the local contributors have been contacted, and as long as there are no objections, we could start an import project in
the OSMCanada task manager. Pre-processed data are available. We only have to make it available to the task manager. We also have to provide the task manager with the working areas (tasks) adjusted to 200 buildings per task. I am currently working to define
these working areas, but if someone else can build it in the meantime it would be great.
<o:p></o:p></p>
<p class="MsoNormal">Once the import project has been configured in the task manager, interested contributors will have to identify themselves in talk-ca in order to add them as authorized contributors (James, am I right?)<o:p></o:p></p>
<p class="MsoNormal">Would it be fun to try this?<o:p></o:p></p>
<p class="MsoNormal">Daniel<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>