[1.0.0] Raster / Vector conversion

Open
#2,951 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the README feature matrix and the decisions in #2930, then inspect xrspatial/polygonize.py, contour.py, rasterize.py, and polygon_clip.py. Run the listed deep sweep against polygonize.py and review each linked bug issue. Done requires resolved scope and dark-corner decisions, no CRITICAL or HIGH findings, and completed notebook coverage.

Written by the indexing model from the issue text.

Description

1.0.0-tracking area:vector

1.0.0 readiness: Raster / Vector conversion

Area: Vector Functions: polygonize, contours, rasterize, clip_polygon
Source: xrspatial/{polygonize,contour,rasterize,polygon_clip}.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
  • #2788 (Low) contours() validates return_type too late, wasting compute on invalid values
  • #2790 (Medium) contours() emits degenerate and duplicate lines for exact-level plateaus
  • #2791 (Low) contours(): n_levels is not validated as a positive integer
  • #2795 (Low) contours() emits RuntimeWarning on all-NaN input with auto level selection
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.