microsoft / microsoft/GlobalMLBuildingFootprints
Spike polygon in Pakistan, quadkey: 12310213122
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2k
- Forks
- 277
- PR merge metrics
- No merged PRs in 30d
Description
The polygon shown below has a spike:
The WKT is: POLYGON ((72.4680086 34.9335963, 72.4679303 34.9336224, 72.4679948 34.9336009, 72.4680111 34.9336338, 72.4680354 34.9336257, 72.4680827 34.9337212, 72.4679986 34.9337492, 72.4679643 34.9336802, 72.4678032 34.9337339, 72.4677635 34.9336538, 72.4676553 34.9336899, 72.4676039 34.9335861, 72.4677778 34.9335281, 72.4677937 34.9335602, 72.4678891 34.9335284, 72.4678689 34.9334877, 72.4679425 34.9334631, 72.4680086 34.9335963))
While most systems regard this as invalid -- the notable exception being BigQuery -- it does look like an artefact of post processing, which could be removed with something like an internal angle > 359 degree check.
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 locating the polygon post-processing or geometry-validation entry point in the repository; the issue provides the affected WKT and quadkey 12310213122 as a reproduction. Check how invalid building polygons are handled and compare the generated geometry for this example. Done means the spike is removed without damaging the rest of the polygon, with a regression check for this WKT if the project has a suitable test location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100