ydyvip / globalmlbuildingfootprints Goto Github PK

Bing Maps is releasing open building footprints around the world. We have detected 1.04B buildings from Bing Maps imagery between 2014 and 2022 including Maxar, Airbus, and IGN France imagery. The data is freely available for download and use under ODbL. This dataset complements our other releases.

• 2023-03-13 - Added 41MM new buildings in Japan derived from Maxar Imagery (FP rate 0.8%). Added 79M building height estimates for North America structures.
• 2022-11-16 - Added 40M new and updated buildings across 46 geographies derived from Bing imagery including Maxar, IGN-France, and AirBus between 2015 and 2022. The largest updates are for Pakistan (16M), Turkey (13M), Afghanistan (3M), and Saudi Arabia (2.5M). Added make-gis-friendly.py demonstrating how to convert files into a GIS tool (e.g., QGIS, ArcGIS) friendly format.
• 2022-10-12 - Added 147M new buildings for North America based on Vexcel and Maxar imagery between 2017 and 2022. This data is a refresh of US. Updated data format from country-partitioned zip files to country-l9 quad key gzipped partitioned files. Each file extension is .csv.gz but the contents are geojsonl. False positive rate for this dataset is ~1% based on a 4k structure sample. Link table was moved to a dataset-links.csv
• 2022-07-08 - Added 78M buildings in Western EU Countries from Maxar imagery between 2014 and 2021 bringing the total structure count to 856M. Added link to download buildings coverage.
• 2022-07-05 - The complete building footprints dataset is available on Microsoft's Planetary Computer

You can download the layer above as GeoJSON here.

This data is licensed by Microsoft under the Open Data Commons Open Database License (ODbL).

999M building footprint polygon geometries located around the world in line delimited GeoJSON format. Due to the way we process the data, file extensions are .csv.gz see make-gis-friendly.py for an example of how to decompress and change file extension.

As of October 2022, we moved the location table to dataset-links.csv since it's over 19k records with country-quadkey partitioning.

GeoJSON is a format for encoding a variety of geographic data structures. For intensive documentation and tutorials, refer to this blog.

Microsoft has a continued interest in supporting a thriving OpenStreetMap ecosystem.

Maybe. Never overwrite the hard work of other contributors or blindly import data into OSM without first checking the local quality. While our metrics show that this data meets or exceeds the quality of hand-drawn building footprints, the data does vary in quality from place to place, between rural and urban, mountains and plains, and so on. Inspect quality locally and discuss an import plan with the community. Always follow the OSM import community guidelines.

Yes. The HOT Tasking Manager has integrated Facebook RapiD where the data has been made available.

The building extraction is done in two stages:

1. Semantic Segmentation – Recognizing building pixels on an aerial image using deep neural networks (DNNs)
2. Polygonization – Converting building pixel detections into polygons

We trained a neural network to estimate height above ground using imagery paired with height measurements, and then we take the average height within a building polygon. Structures without height estimates are populated with a -1.

We did not apply any modeling improvements for this release. Instead, we focused on scaling our approach to increase coverage, and trained models regionally.

The evaluation metrics are computed on a set of building polygon labels for each region. Note, we only have verification results for Mexico buildings since we did not train a model for the country.

Building match metrics on the evaluation set:

We track the following metrics to measure the quality of matched building polygons in the evaluation set:

1. Intersection over Union – This is a standard metric measuring the overlap quality against the labels
2. Dominant angle rotation error – This measures the polygon rotation deviation

False positives are estimated per country from randomly sampled building polygon predictions.

Vintage of extracted building footprints depends on the vintage of the underlying imagery. The underlying imagery is from Bing Maps including Maxar and Airbus between 2014 and 2021.

Our metrics show that in the vast majority of cases the quality is at least as good as hand digitized buildings in OpenStreetMap. It is not perfect, particularly in dense urban areas but it provides good recall in rural areas.

EPSG: 4326

Maybe. This is a work in progress. Also, check out our other building releases!

• US
• Australia
• Canada
• Uganda and Tanzania
• South America
• Kenya and Nigeria
• Indonesia, Malaysia, and the Philippines

We excluded imagery from processing if tiles were dated before 2014 or there was a low-probability of detection. Detection probability is loosely defined here as proximity to roads and population centers. This filtering and tile exclusion results in squares of missing data.

Some files are very large but they are stored in line-delimited format so one could use parallel processing tools (e.g., Spark, Dask) or create a memory efficient script to segment into smaller pieces. See scripts/read-large-files.py for a Python example.

Check out our ML Road Detections project page!

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries. The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks. Microsoft's general trademark guidelines can be found here.

Privacy information can be found here.

Microsoft and any contributors reserve all others rights, whether under their respective copyrights, patents, or trademarks, whether by implication, estoppel or otherwise.