bcgov / bcgov/wps

Innovation: Fuel Treatment Success Rates

Open
#4,720 0 comments 0 reactions 0 assignees View on GitHub
4Refinement User Story
Dominant language
Python
Stars
65
Forks
11
Avg merge
21h 25m
Merged PRs (30d)
70

Description

**Based on the previous Innovation Sprint #3906 and the Generate Values Threatened Details**

**As a** Wildfire Prevention Officer,

**I need:**
a) to upload an annual Fuel Treatment KML file with all the Fuel Treatments in BC
b) get alerted when wildfires burn into a Treated Area
c) get alerted when a wildfire is lees than 5 km from a treatment. (may not be MVP)

**So That**
I can send out an assessor to inform me if the Fuel Treatment worked or not and if the Fuel Treatment helped the firefighters.

Re: c) I will get notified before a treatment has an interaction to allow staff to be dispatched prior to interaction to observe how fire interacts with a stand.

Also: treatments are usually conducted near values. This early warning method will also be a heads up to operational staff that a community or value may also be threatened.

**Acceptance Criteria**
- [ ] Given (Context), When (action carried out), Then (expected outcome)
- [ ] Given (Context), When (action carried out), Then (expected outcome)

**Additional Context**
- Another benefit of this system is that it will allow for more thorough documentation of interactions, resulting in a more efficient process and improved guidance on treatments, which in turn will support better funding allocations. By increasing the number of documented interactions, it will also expand opportunities for people to study and observe these interactions, enhancing overall knowledge of the program across the province. This approach will also improve field observation techniques and foster the development of interested staff, ultimately leading to a larger pool of experienced field observers and fire effects monitors within the province.

**Definition of Done**
https://github.com/bcgov/wps/wiki/Definition-of-Done

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are identified in the issue. Start by clarifying the annual KML upload, wildfire interaction and distance-alert requirements, then define concrete acceptance criteria and identify where treatment data and notifications belong; done is a reviewed, testable scope rather than the current placeholder criteria.

Written by the indexing model from the issue text.

Assessment

Domain
backend, data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.