NEW FireBAT: Dynamic Thiessen polygons
- Dominant language
- Python
- Stars
- 65
- Forks
- 11
- Avg merge
- 21h 25m
- Merged PRs (30d)
- 70
Description
**As a** *Fire Behavior Analyst* **I want** *my advisory to be based on currently reporting weather stations* **So That** *my advisory is based on accurate data*
**Additional Context**
- Stations do actually change from time to time, or go offline, and our polygons have to update accordingly.
- Stations on map need to be based on their reporting status.
- Thiessen polygons need to match currently reporting stations.
- There are python libraries that we can leverage, see: https://github.com/WZBSocialScienceCenter/geovoronoi
**Acceptance Criteria**
- [ ] Given a wildfire station is active, When I generate a FBA, Then it should be on the map.
- [ ] Given a wildfire station is active, When I generate a FBA, Then it should have a corresponding Thiessen polygon.
- [ ] Given a wildfire station is not active, When I generate a FBA, Then it should not be on the map.
- [ ] Given a wildfire station is not active, When I generate a FBA, Then it should not have a corresponding Thiessen polygon.
- [ ] Given a station isn't a wildfire station, When I generate a FBA, Then it should not be represented in any form.
- [ ] Given I need to generate an FBA, the list of stations and the Thiessen polygons load quickly.
- [ ] Given a wildfire station switches from active to inactive, this change is reflected in the FBA immediately. (*I think we can do this in real-time, if immediate is difficult, then we'll need an actually acceptable range (hours or days?) and need to create an appropriate cronjob or something. *)
Contributor guide
Research direction
No files, tests, or entry points are named. Start by tracing FBA generation and how reporting wildfire stations are selected; then verify map station and Thiessen polygon output against the acceptance criteria, including the unresolved refresh interval.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, data-visualization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100