microsoft / microsoft/GlobalMLBuildingFootprints

Previous versions of dataset-links.csv

Open
#112 0 comments 0 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

Potentially dumb question. Is it possible to access previous vintages of the building footprint data?

While going through the issues log I see that this link still works:

https://minedbuildings.blob.core.windows.net/global-buildings/2023-03-13/global-buildings.geojsonl/RegionName%3DBolivia/quadkey%3D210031332/part-00117-459b9c51-35d7-4ec5-87f4-f9fc46a069a8.c000.csv.gz

If I have the processed date of interest, region and quadkey I could construct the download path, but I am not clear on how I would determine the "part" reference without a previous version of the dataset-links.csv

Any help you could provide would be greatly appreciated, even if it's just to put me out of my misery and tell me it's not possible!

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 the linked 2023-03-13 blob URL and the issue's references to dataset-links.csv, processed dates, regions, and quadkeys. Check whether the repository or published data documents access to previous vintages and how the part reference is determined; done means documenting a confirmed retrieval process or clearly stating that historical links are unavailable.

Written by the indexing model from the issue text.

Assessment

Domain
data
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.