xarray-contrib / xarray-contrib/xarray-spatial
[1.0.0] Terrain metrics
Open
Nobody has claimed this yet.
1.0.0-tracking
area:surface
- Dominant language
- Python
- Stars
- 972
- Forks
- 92
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 7
Description
1.0.0 readiness: Terrain metrics
Area: Surface Functions: roughness, tpi, tri, landforms
Source: xrspatial/terrain_metrics.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/terrain_metrics.py - Security
- Performance
- API consistency
Last swept: none yet
Examples
- Notebook example
- (optional) standalone script
Linked bug issues
none yet
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/terrain_metrics.py and compare its public surface with the README feature matrix. Review the dark-corner decisions in #2930, then work through the accuracy, security, performance, API-consistency, and example checklist; done means the surface is frozen, sweeps have no CRITICAL or HIGH findings, and the notebook example is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100