{"id":1418,"date":"2025-07-23T17:04:43","date_gmt":"2025-07-23T17:04:43","guid":{"rendered":"https:\/\/sola.kau.se\/deprimap\/?p=1418"},"modified":"2025-07-23T17:04:45","modified_gmt":"2025-07-23T17:04:45","slug":"google-v3-download","status":"publish","type":"post","link":"https:\/\/sola.kau.se\/deprimap\/2025\/07\/23\/google-v3-download\/","title":{"rendered":"Efficient Access to Google Buildings V3: A Two-Step Workflow for Targeted Downloads and Processing"},"content":{"rendered":"
The Google Open Buildings v3 dataset is a valuable global resource containing building footprint information for the majority of the countries across the Global South, including Africa, South and Southeast Asia, and Latin America. While powerful in scope, the full dataset weighs in at 178GB<\/strong> in compressed form, a size that makes it impractical for many localised research or planning tasks. <\/p>\n\n\n\n Most users don’t need all of it; they need data for specific cities, countries, or project areas. Yet the official dataset is distributed in large spatial tiles, and there’s no straightforward way to download just the relevant parts.<\/p>\n\n\n\n In this blogpost, we present a simple, scalable, and memory-efficient two-step pipeline for working with the Google Buildings v3 dataset:<\/p>\n\n\n\n This approach works with any polygon-based ROI – whether it’s a single boundary or a set of disjoint polygons. It’s implemented in Python using open-source tools and is available through a public Github Repository.<\/p>\n\n\n\n Whether you’re working on deprivation mapping, urban morphology, or infrastructure planning, this pipeline offers a lightweight and reusable method to access only the data you actually need, and nothing more.<\/p>\n\n\n\n(Google Earth Engine is a good option if your study area is a single city or two. If your study area increases in size, it is not really an option.)<\/em><\/pre>\n\n\n\n
\n