Japan region missing subset of 133002112 (appears to be 13300211212)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by verifying quadkey 13300211212 in the geojsonl downloads and the Planetary Computer, then compare it with the other level-11 quadkeys under 133002112. Done means determining whether the subset should contain data and either restoring its availability or documenting why it is absent.
Written by the indexing model from the issue text.
Description
Hello,
I tried downloading data for Tokyo and noticed that the following quadkey is missing from both the geojsonl downloads and the planetary computer:
13300211212
As the other 15/16 quadkeys from level 11 contain data, my assumption here is that there should be some results.
As these are found is there a best practice for creating issues and being notified of potential updates to those particular quad keys?
- Dominant language
- Python
- Stars
- 2k
- Forks
- 277
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/GlobalMLBuildingFootprints
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
Greek data missingOpen
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
microsoft/GlobalMLBuildingFootprints#137 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in microsoft/GlobalMLBuildingFootprints
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
letsencrypt/cp-cps#353 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
PedestrianDynamics/pyFDS-Evac#394 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
DOI-USGS/pywatershed#421 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
python-pillow/Pillow#10087 · 1 comment ·
Maintainers usually reply within 1 day