<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=utf-8">
<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:0cm;
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;}
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";}
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: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"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I am about to complete the Squamish test area and so far the new ODB import procedure seems adequate. So, if you require the data to be pre-processed over the
selected area just let me know. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">However, I would suggest using squares instead of various polygons to define tiles because it is simpler to manage OSM data when downloading it in JOSM.<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">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Daniel<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>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Nate Wessel [mailto:bike756@gmail.com]
<br>
<b>Sent:</b> Saturday, April 04, 2020 00:57<br>
<b>To:</b> talk-ca@openstreetmap.org<br>
<b>Subject:</b> [Talk-ca] Toronto building import<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p>Hi all, <o:p></o:p></p>
<p>I've been spending some time today working on restarting the Toronto building import effort which seems to have stalled a while back (I got distracted, sorry!).
<o:p></o:p></p>
<p>What I'm proposing to do is essentially just to finish off the building import that was started over a year ago in Ontario, though just within the bounds of the City of Toronto. That larger import, at the time, never reached the central parts of the city
and there are about 55,000 buildings that can still easily be imported from the ODB.
<o:p></o:p></p>
<p>There is an outline of the proposal here ( <a href="https://wiki.openstreetmap.org/wiki/Toronto_building_import">
https://wiki.openstreetmap.org/wiki/Toronto_building_import</a> ) <o:p></o:p></p>
<p>And I've uploaded some task-level OSM data to GitHub ( <a href="https://github.com/Nate-Wessel/TO-building-import/tree/master/tasks">
https://github.com/Nate-Wessel/TO-building-import/tree/master/tasks</a> ) if anyone cares to inspect it.<o:p></o:p></p>
<p>Hopefully this import process will address most of the concerns raised about the initial import, including those I raised myself ;-)<o:p></o:p></p>
<p>Anyway, this email is just to notify y'all that I've been working on this again and to start the necessary discussions and get any feedback. I'd love to begin to move forward in the next couple of weeks if there is support for this effort here, and on the
imports mailing list. Please let me know what you think!<o:p></o:p></p>
<p>Best,<o:p></o:p></p>
<div>
<p class="MsoNormal">-- <o:p></o:p></p>
<p>Nate Wessel<span style="font-size:10.0pt">, PhD<br>
Planner, Cartographer, Transport Nerd<br>
<a href="https://www.natewessel.com"><span style="text-decoration:none">NateWessel.com</span></a></span>
<o:p></o:p></p>
</div>
</div>
</body>
</html>