[1.0.0] polygonize

Open
#3,030 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
data

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.

Description

1.0.0-tracking area:vector

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.

Dominant language
Python
Stars
972
Forks
92
Avg merge
2d 12h
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from xarray-contrib/xarray-spatial

All issues in xarray-contrib/xarray-spatial

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.