FireBAT: Confirm FBA exclusions, e.g. Slash in Coastal
- Dominant language
- Python
- Stars
- 65
- Forks
- 11
- Avg merge
- 21h 25m
- Merged PRs (30d)
- 70
Description
**Describe the task**
Decision: how will we balance OSWS 5 with some known exceptions?
- Some fuels in some fire centres would always generate an advisory, e.g. slash fuels in Coastal, creating a less-useful FBA (over-alerting, distracting from new advisory/warning areas). In this case, we don't want to display slash fuels in the table / on a map.
- On their current FBA template, Coastal say "All slash fuels are in Extreme Fire Behaviour Warning 0900-2300 daily. Expect average rates of spread 10-15m/min - vigorous surface fire" (July 27, 2021)
**Acceptance Criteria**
- [ ] PO decision: how to handle this
- collect and add variable exclusions to the FBA templates for each FC, as applicable?
**Additional context**
- Add any other context about the task here.
- Or here
Contributor guide
Research direction
Begin with the OSWS 5 and FBA-template context in this issue, especially the Coastal slash-fuel example. The product owner must decide whether each fire centre's template should contain variable exclusions; done means the decision is recorded and applicable exclusions are identified.
Written by the indexing model from the issue text.
Assessment
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100