<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head><body style="font-family: Verdana; font-size: 12pt;"
bgcolor="#FFFFFF" text="#000000"><div style="font-size:
12pt;font-family: Verdana;">>The Microsoft building outline dataset
is very simple, containing only
the outline of the building. No address, no height, no building type. no
name. It can be (and was) derived 100% from aerial imagery. IMO if
someone loads that up, and manually approves each building, then that
(IMO) is much less of an import.
<br><br>It is not imagery and it is imported. Therefore it really does
need all the red tape for a formal import.<br><br>There have been some
really poor building outlines created by AI software which means you
really should distinguish your sources.<br><br>The other bigger here is
who are the local community who approves such things. Microsoft
building outlines cover a lot of space. If one person in the US feels
that the quality isn't good enough does that stop the use of any import
using the Microsoft building outlines or can local groups decide they
are happy with the quality? If so how do you define a local group.<br><br>Thanks
John<br><br><span>Rory McCann wrote on 2019-02-18 10:11 AM:</span><br><blockquote
type="cite"
cite="mid:820b0c8b-fd2c-b489-f9a1-f3e2f5ccae7c@technomancy.org">The
Microsoft building outline dataset is very simple, containing only
the outline of the building. No address, no height, no building type. no
name. It can be (and was) derived 100% from aerial imagery. IMO if
someone loads that up, and manually approves each building, then that
(IMO) is much less of an import.
</blockquote><br><div class="moz-signature">-- <br>
<div>Sent from <a
href="https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach"><span
style="color: rgb(0, 157, 247);">Postbox</span></a></div></div></div></body></html>