microsoft / microsoft/GlobalMLBuildingFootprints
Particularly poor geometry around the Chicago Loop
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2k
- Forks
- 277
- PR merge metrics
- No merged PRs in 30d
Description
Although we have seen media showcasing otherwise decent geometry offered by Microsoft Building Footprints, the geometries near Chicago from the 2022 dataset seem to be particularly inaccurate:
This is still not near as egregious as the chaotic geometry of this area from the 2019-2020 US Building Footprints:
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by comparing the linked 2022 Global Building Footprints Chicago data with the linked 2019–2020 Illinois dataset and the screenshots to reproduce the geometry problem. The issue does not identify an entry point, test, intended correction, or acceptance criteria, so what constitutes a completed fix must be clarified before implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100