SFMS: Consumption method for fuel grid
- Dominant language
- Python
- Stars
- 65
- Forks
- 11
- Avg merge
- 21h 25m
- Merged PRs (30d)
- 70
Description
**Describe the task**
Develop a method for Geospatial to upload annual fuel grid updates that would automatically update our tools like SFMS and ASA.
With green up and standing grass settings updating every day, there's a need to store those outputs and display them in SFMS Insights.
**Acceptance Criteria**
- [ ] Permission based functionality to Upload fuel grid: only users with `geospatial` role can upload
- [ ] #5766
- [ ] Upload percent conifer in M-1/M-2 fuel types
- [ ] Upload percent deadfir in M-3/M-4 fuel types
- [ ] Uploads include grid and lookup table
- [ ] Testing & Validating the newly uploaded version:
- confirm valid raster values match fuel table and have assigned FBP Fuel Types and color values
- if fuel grid has m1/m2 fuel types, upload must include percent conifer grid
- all values greater than 0, less than (equal to?) 100
- if fuel grid has m3/m4 fuel types, upload must include percent deadfir grid
- all values greater than 0, less than (equal to?) 100
- [ ] Versioning scheme: `sfms/static/fuel///
- [ ] Versioning scheme percent conifer: `sfms/static/fuel///
- [ ] Versioning scheme percent deadfir: `sfms/static/fuel///
**Additional context**
- Cadillac = Preview link
- Or here
Contributor guide
Research direction
The issue names no files, tests, or entry points; begin by locating the existing SFMS fuel-grid upload, role-permission, and Insights flows. Done means geospatial-only uploads accept the required grids and lookup table, validate values and fuel types, create the specified versioned files, and have tests covering the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fastapi, python
- Domain
- api, authorization, backend, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100