ASA: Additional Grids: Slope
- Dominant language
- Python
- Stars
- 65
- Forks
- 11
- Avg merge
- 21h 25m
- Merged PRs (30d)
- 70
Description
**As a** *recipient of a FBA, or* **I want** *to show the local fire environment context thats driving the advisory* **So That** *the information is practical and useable*
ASA: Additional Grids: Fuels, Elevation, Slope, Aspect
**Additional Context**
- Categorical: frequency by fuel type, frequency by aspect
- Elevation vector vs High HFI
**Acceptance Criteria**
- [ ] Grids accessible for the analysis, start with fuel layer, elevation, slope TBD, aspect later (new stories?)
- [ ] Use HFI threshold areas as a mask (polygon/raster/etc), extract out underlying values
TO DO: Pull out to other stories
- [ ] Zonal statistics off of underlying rasters
- [ ] Visualize/Textualize zonal statistics to make it useful
- [ ] Given (Context), When (action carried out), Then (expected outcome)
- [ ] Given (Context), When (action carried out), Then (expected outcome)
- [ ] Infographic?
**Definition of Done**
- Ready to Demo in Sprint Review
- Does what I have made have appropriate test coverage?
- Documentation and/or scientific documentation exists and can be found
- Peer Reviewed by 2 people on the team
- Manual testing of all PRs in Dev and Prod
- Merged
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by identifying the existing analysis-grid and HFI-threshold-mask workflows, then clarify which fuel, elevation, slope, and aspect work belongs in this story. Done should include accessible grids, masked underlying values, useful zonal statistics, tests, documentation, review, and a demo-ready merged change.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100