<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html;
      charset=windows-1252">
  </head>
  <body>
    <p>Responding to point C below,<br>
      I would strongly suggest that we not confuse the process of
      importing new data with that of updating/modifying existing data
      in the OSM database. One of the things I really disliked about the
      initial building import was that it overwrote existing data at the
      same time that new data was brought in. These are really two
      separate import processes and require very different
      considerations. <br>
    </p>
    <p>We can certainly consider using this dataset to improve/update
      existing building geometries, but I think that is a separate
      process from the import we are discussing here. To keep things
      simple for this import, I would suggest removing any building from
      the import dataset that intersects with an existing building in
      the OSM database. That is, let's not worry about conflation for
      now, and come back and do that work later if we still feel there
      is a strong need for it. <br>
    </p>
    <p>I see the main point of this effort as getting more complete
      coverage - it we want to use the dataset to do quality assurance
      on existing data, that is a whole other discussion.</p>
    <p>Best,<br>
    </p>
    <div class="moz-signature">
      <p> Nate Wessel<small>, PhD<br>
          Planner, Cartographer, Transport Nerd<br>
          <a href="https://www.natewessel.com"
            style="text-decoration:none;">NateWessel.com</a></small>
      </p>
    </div>
    <div class="moz-cite-prefix">On 2020-01-15 12:55 p.m., Daniel
      @jfd553 wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:YTBPR01MB2461E4E01FBF9874544B544A94370@YTBPR01MB2461.CANPRD01.PROD.OUTLOOK.COM">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <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:Consolas;
        panose-1:2 11 6 9 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;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0cm;
        mso-margin-bottom-alt:auto;
        margin-left:0cm;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0cm;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Courier New";}
p.MsoNoSpacing, li.MsoNoSpacing, div.MsoNoSpacing
        {mso-style-priority:1;
        margin:0cm;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";
        mso-fareast-language:EN-US;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0cm;
        margin-right:0cm;
        margin-bottom:10.0pt;
        margin-left:36.0pt;
        line-height:115%;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";
        mso-fareast-language:EN-US;}
span.EmailStyle20
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.EmailStyle21
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle22
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle23
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:"Consolas","serif";
        mso-fareast-language:EN-US;}
span.EmailStyle26
        {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:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
        {page:WordSection1;}
/* List Definitions */
@list l0
        {mso-list-id:1448114280;
        mso-list-type:hybrid;
        mso-list-template-ids:1889989176 269025303 269025305 269025307 269025295 269025305 269025307 269025295 269025305 269025307;}
@list l0:level1
        {mso-level-number-format:alpha-lower;
        mso-level-text:"%1\)";
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level2
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level3
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
@list l0:level4
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level5
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level6
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
@list l0:level7
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level8
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level9
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
ol
        {margin-bottom:0cm;}
ul
        {margin-bottom:0cm;}
--></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]-->
      <div class="WordSection1">
        <p class="MsoNormal">Thanks for the quick replies!<o:p></o:p></p>
        <p class="MsoNormal">Now, about...<o:p></o:p></p>
        <p class="MsoNormal"
          style="margin-bottom:0cm;margin-bottom:.0001pt"><b><span
              style="font-size:12.0pt;line-height:115%">a) Data hosting:<o:p></o:p></span></b></p>
        <p class="MsoNormal">Thank you James, I really appreciate your
          offer (and that of others). So yes, I think hosting
          pre-processed data in the task manager, for approved regions,
          is an attractive offer. When we agree on a municipality for
          pre-processing, I will contact you to make the data available.<o:p></o:p></p>
        <p class="MsoNormal">BTW, I thought ODB data in OSM format was
          hosted with the OSMCanada task manager. I understand that ODB
          data are currently converted on the fly when requested?<o:p></o:p></p>
        <p class="MsoNormal"
          style="margin-bottom:0cm;margin-bottom:.0001pt"><b><span
              style="font-size:12.0pt;line-height:115%">b) Task manager
              work units for import:<o:p></o:p></span></b></p>
        <p class="MsoNormal">I agree with Nate, ~ 200 buildings or ~
          1,500 nodes would be suitable. I was thinking at the same
          importation rate, but for an hour of work. It seems best to
          target 20-minute tasks.<o:p></o:p></p>
        <p class="MsoNormal"
          style="margin-bottom:0cm;margin-bottom:.0001pt"><b><span
              style="font-size:12.0pt;line-height:115%">c) Task manager
              work units for checking already imported data<o:p></o:p></span></b></p>
        <p class="MsoNormal">According to Nate, it is definitely not
          faster than actively importing. We should then keep the above
          setup (b).<o:p></o:p></p>
        <p class="MsoNormal">However, what if I add a new tag to
          pre-processed data indicating if a building was altered or not
          by the orthogonalization (and simplification) process? For
          instance,
          <i>building:altered=no</i>, would identify buildings that were
          not changed by the process and that could be left unchanged in
          OSM (i.e. not imported);
          <i>building:altered=yes</i> for those who were changed by the
          process and that should be imported again. The same
          pre-processed datasets could then be made available for all
          cases. Thoughts?<o:p></o:p></p>
        <p class="MsoNormal"
          style="margin-bottom:0cm;margin-bottom:.0001pt"><b><span
              style="font-size:12.0pt;line-height:115%">d) Finding local
              mappers:<o:p></o:p></span></b></p>
        <p class="MsoNormal">I agree with Nate’s suggestion to try
          contacting the top 10 mappers in an area. Using the "main
          activity center" would work for most of the contributors but
          selecting other overlays (.e.g. an activity center over last 6
          months) could also work great. As long as we identify who
          might be interested in knowing there is an import coming.<o:p></o:p></p>
        <p class="MsoNormal">Comments are welcome, particularly about
          the proposal on c)<o:p></o:p></p>
        <p class="MsoNormal">Daniel<o:p></o:p></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
      </div>
    </blockquote>
  </body>
</html>