xarray-contrib / xarray-contrib/xarray-spatial
[1.0.0] Emerging hotspots
Open
Nobody has claimed this yet.
1.0.0-tracking
area:stats
- Dominant language
- Python
- Stars
- 972
- Forks
- 92
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 7
Description
1.0.0 readiness: Emerging hotspots
Area: Stats Functions: emerging_hotspots
Source: xrspatial/emerging_hotspots.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/emerging_hotspots.py - Security
- Performance
- API consistency
Last swept: none yet
Examples
- Notebook example
- (optional) standalone script
Linked bug issues
- #2804 (Critical) emerging_hotspots() repeats the local-mean z-score bug instead of computing Gi*
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/emerging_hotspots.py and compare its public surface with the README feature matrix. Review the unresolved decisions in #2930 and the critical issue in #2804, then run the listed accuracy, security, performance, and API-consistency sweeps. Done means no CRITICAL or HIGH findings remain and the notebook example is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- analytics, data
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100