SFMS: Design Data Model for Storing Data Inputs and Outputs
- Dominant language
- Python
- Stars
- 65
- Forks
- 11
- Avg merge
- 21h 25m
- Merged PRs (30d)
- 70
Description
**Describe the task**
SFMS requires a number of gridded and tabular inputs along with season inputs. The system generates an even larger number of outputs. **This task is to design the data model for storing and retrieving inputs and archiving outputs.**
**Acceptance Criteria**
- [x] #4946
- [x] #5002
- [x] #4959
- [ ] #4947
- [x] #4961
- [ ] #4962
- [ ] #4963
- [x] #4970
- [ ] Accessible APIs: Fuel Layers etc.
- [ ] FFMC elevation adjustment for Temp and dewpoint temp (Liz)
- [ ] Shaded Digital elevation model when viewing the FFMC or BUI layer so that FBAs can pick out the south facing slopes. (Liz)
- [ ] Lat/Long coordinates are provided when hovering over a pixel (Liz)
- [ ] Add a scale legend (Liz)
- [ ] How do iterative calculations work, i.e.) when are we using station data, and when do we switch to numerical weather model data?
- [ ] UI that allows viewing of time series data - time slider? - something to view the forecast ffmc/dmc/dc/etc for the next few days
- [ ] What numerical weather model should we consume for both hourly and daily calculations. The answer could include a different weather model for each parameter.
- [ ] File naming scheme for data storage including actuals and forecast. Can we use the current file naming scheme to ease transition.
- [ ] Data retention rules - what do we keep and for how long?
- [ ] How do temporal configuration parameters like grass curing, greenup, snow masking work?
- [ ] How do time zones work in the calculations?
- [ ] What are all the outputs we are calculating? Current outputs include: https://wfapps.nrs.gov.bc.ca/pub/wfwx-info-war/sfms
- [ ] What must consume our data outputs for fire season 2026 (ASA, BCWS GeoDatabases and fire growth modelling vendors)
- [ ] What is the schedule for computing forecast and observed values? Does the system re-run to account for late and/or missing data inputs?
- [ ] **Migrating SFMS Insights to Gold Disaster Recovery**
**Additional context**
- Consider defining outputs as Cloud Optimized GeoTiffs (COGs).
- The desired cell resolution for calculations is 250 m. The current resolution of SFMS calculations is 2000 m.
- https://cwfis.cfs.nrcan.gc.ca/en/interactive-map?selectedDate=2026-06-04&layerIds=public%3Am3polygons%2Cpublic%3Afwi
Contributor guide
Research direction
Start by reviewing the unchecked acceptance criteria and the current SFMS outputs linked in the issue. Define the required input and output data, retention and naming decisions, consumers, schedules, and accessible APIs before selecting the storage model. Done means the model and retrieval approach are agreed, including the listed spatial, temporal, and forecast requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- backend-api-design, data-engineering, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100