SPIKE: ASA: Investigate alternative ways to handle and process HFI data TIMEBOX = ?
- Dominant language
- Python
- Stars
- 65
- Forks
- 11
- Avg merge
- 21h 25m
- Merged PRs (30d)
- 70
Description
**Describe the task**
Calculating the combustible land area per HFI range (0-4k, 4k-10k, >10k) per zone unit is an extensive process as it involves spatial intersect queries of potentially thousands of HFI polygons with combustible land per zone unit. We currently reclassify the HFI raster from SFMS to the three ranges and store advisory and warn level polygons in the database as many tiny polygons leading to thousands of rows per SFMS run.
We need to explore a better way of doing this.
**Acceptance Criteria**
- [ ] first
- [ ] second
- [ ] third
**Additional context**
- Add any other context about the task here.
- Or here
Contributor guide
Research direction
Start by reviewing the current SFMS HFI raster reclassification, the three HFI ranges, and how advisory and warning polygons are stored in the database. Investigate alternatives to the spatial intersection process and define concrete acceptance criteria for the preferred approach; the existing first, second, and third criteria are placeholders.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- data, databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100