Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[1.0.0] Visibility

Open
#2,935 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

Research direction

Start with the README feature matrix and xrspatial/{viewshed,visibility}.py, then review the unresolved decisions in #2930. Run the listed /deep-sweep for viewshed.py and track the linked bug issues, notebook example, and optional script. Done means the checklist is cleared with no CRITICAL or HIGH findings.

Written by the indexing model from the issue text.

Description

1.0.0-tracking area:surface

1.0.0 readiness: Visibility

Area: Surface Functions: viewshed, cumulative_viewshed, visibility_frequency, line_of_sight
Source: xrspatial/{viewshed,visibility}.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/viewshed.py
  • Security
  • Performance
  • API consistency

Last swept: none yet

Examples
  • Notebook example
  • (optional) standalone script
Linked bug issues
  • #2786 (High) viewshed() mutates the caller's input DataArray (int16 becomes float64)
  • #2789 (Medium) viewshed: validate regular grid spacing instead of silently assuming it
  • #2792 (Medium) viewshed: ValueError 'node not found' on NaN input (CPU sweep)
  • #2793 (High) Broken bounds-check guard in viewshed _calculate_event_row_col()
  • #2794 (Medium) viewshed(): validate scalar params (max_distance >= 0, finite observer/target elev) before dispatch
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.