xarray-contrib / xarray-contrib/xarray-spatial
[1.0.0] polygonize
Open
Nobody has claimed this yet.
1.0.0-tracking
area:vector
- Dominant language
- Python
- Stars
- 972
- Forks
- 92
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 7
Description
1.0.0 readiness: polygonize
Area: Vector Function: polygonize
Source: xrspatial/polygonize.py
Scope
- Public surface frozen against the README feature matrix
- Dark-corner decisions resolved (see #2930)
Sweep clearance, no CRITICAL or HIGH (accuracy and security first)
- Accuracy
/deep-sweep xrspatial/polygonize.py - Security
- Performance
- API consistency
Last swept: none yet
Examples
- Notebook example
- (optional) standalone script
Linked bug issues
- #2538 (Medium) polygonize: dask backend processes chunks serially, no parallelism
- #2677 (High) Dask 8-connectivity float polygonize diverges from numpy at large rtol
Part of #2951.
Contributor guide
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 with xrspatial/polygonize.py and the README feature matrix, then review the dark-corner decisions in #2930 and the linked issues #2538 and #2677. Run /deep-sweep xrspatial/polygonize.py and address the readiness checklist; done means no CRITICAL or HIGH findings, resolved API and example checks, and cleared linked concerns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100