ASA/SFMS: Graphical Repository of All Issued Fire Behaviour and Weather Warnings, Spot Forecasts, and Venting Forecasts
- Dominant language
- Python
- Stars
- 65
- Forks
- 11
- Avg merge
- 21h 25m
- Merged PRs (30d)
- 70
Description
**As a** FBA
**I need** a Graphical Repository of All Issued Fire Behaviour and Weather Warnings, Spot Forecasts, and Venting Forecasts
**So That I ...**
1) no longer need to manage and maintain outlook distribution lists when issuing warnings/spots
2) The warnings are spatially displayed
3) users from outside the fire centres can view the adjacent fire centre's warmings and spots. This should eliminate the edge effect issues.
4) Allows us to maintain an archive of previously issued warnings and spots. This would be valuable for case studies and litigation.
**SME = Liz**
**Acceptance Criteria**
- [ ] Given (Context), When (action carried out), Then (expected outcome)
- [ ] Given (Context), When (action carried out), Then (expected outcome)
**Additional Context**
- [Similar to the Victoria/Australia Emergency Warnings on Jan 9, 2026
](https://emergency.vic.gov.au/respond/?=&bbox=139.5703125%2C-40.06966452329777%2C151.995849609375%2C-31.2503781498557&tm=1767997098338#)
**Screenshots**
Danger Trees:
**Definition of Done**
https://github.com/bcgov/wps/wiki/Definition-of-Done
Contributor guide
Research direction
No implementation files, tests, or entry points are named in this issue. Start by turning the placeholder acceptance criteria into concrete requirements with SME Liz; the work is done when the repository's display, cross-centre access, and warning and spot archive behavior are defined and verified.
Written by the indexing model from the issue text.
Assessment
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100