microsoft / microsoft/GlobalMLBuildingFootprints
Geometries are not valid as per SQL
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2k
- Forks
- 277
- PR merge metrics
- No merged PRs in 30d
Description
I imported the Ukraine building data into SQL as Geography objects and found that they were not valid. I simply had to run an update on all geometry and call MakeValid to correct this (took about 4 hours). It would be great if the geometries could be made valid in this repo so that those who are consuming the data don't need to do this extra step and do this heavy compute (think of it as a sustainability thing).
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
No file, test, or entry point is named. Start by locating the pipeline that produces the SQL Geography objects and determine where geometry validity can be checked or corrected. Done means the generated geometries are valid for SQL consumers without requiring a separate MakeValid update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sql
- Domain
- data, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100