microsoft / microsoft/GlobalMLBuildingFootprints

How to access latest data and understand versions

Open
#88 4 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
2k
Forks
277
PR merge metrics
No merged PRs in 30d

Description

First, thanks and much appreciation for making this both open and accessible, both via the dataset-links.csv linked from this repository and on the planetary computer data catalog!

I can happily access either source, but I'm not clear which data releases are available in each location, or how best to pull updates.

  • https://minedbuildings.blob.core.windows.net/global-buildings/dataset-links.csv lists all URLs with 2023-12-26 in the path. Is 2023-12-26 the release date for all these files?

  • the README.md here lists an update for 2024-01-03, particularly for buildings in Brazil and Italy. Is this update included in files linked from dataset-links.csv?

  • the planetary computer example notebook shows how to access the data as a Delta Table, which lists URIs under 2023-04-25/ml-buildings.parquet, and table.history() gives a single WRITE operation at timestamp 1682774982678, around 2023-04-29. Are any of the more recent updates listed in this repository present in that parquet dataset, or are there plans to push updates there?

Should I be aware of tools to help with bulk access or reading metadata for either location?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with README.md, dataset-links.csv, and the Planetary Computer example notebook named in the issue. Verify how release dates, Delta Table history, bulk listing, and metadata access relate, then document the supported versions and update workflow.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, python
Domain
cloud, data-engineering, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.