>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.
It is not imagery and it is imported. Therefore it really does need all
the red tape for a formal import.
There have been some really poor building outlines created by AI
software which means you really should distinguish your sources.
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.
Thanks John
Rory McCann wrote on 2019-02-18 10:11 AM:
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.
--
Sent from Postbox
<https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>
_______________________________________________
Imports mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/imports
