[1.0.0] Terrain metrics

Open
#2,934 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
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
data

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.

Description

1.0.0-tracking area:surface

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

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.