bcgov / bcgov/wps

FireBAT Table: Only display stations crossing an HFI threshold (4,000+)

Open
#1,538 1 comment 0 reactions 0 assignees View on GitHub
Ready User Story
Dominant language
Python
Stars
65
Forks
11
Avg merge
21h 25m
Merged PRs (30d)
70

Description

**As a** *FBAN/FBS* **I want** *to see a table displaying any representative stations in my Fire Centre that are crossing an HFI threshold (4,000 or 10,000)* **So That** *the FBA generation is automated, compliant with OSWS No.5, and I can quickly scan critical context*

**Additional Context**
- [Figma](https://www.figma.com/file/AUhBnTB50dnY7ysoxBSqPN/FireBAT-2021?node-id=207%3A2)
- the map may show polygons for the province and that's ok (zooming = filtering)
- con: let's see how visually busy it is, and how it performs (speed)
- pro: FBANs often consider stations on the border/into the next FC, fires do not respect the fire centre boundaries, they run right through em!
- [list of stations and fuels to consider for each FC](https://bcgov.sharepoint.com/:x:/t/01324/EcqhMuUfI85Jk4QeUCr6cOwB2z-GLJYLqd4PMAi5TKvItg?e=zPYmI3)

**Acceptance Criteria**
- [ ] Given I am using FireBAT, When I select a Fire Centre, Then I only see station and fuel combos that are 4,000+ in the table
- [ ] Given I am using FireBAT, When I select a Fire Centre, Then I see an error message for any stations failing in my Fire Centre. It links me to the Calculator for more info - TG to mock in Figma

**Definition of Done**
- [ ] Ready to Demo in Sprint Review
- [ ] Does what I have made have appropriate test coverage?
- [ ] Documentation and/or scientific documentation exists and can be found
- [ ] Peer Reviewed by 2 people on the team
- [ ] Manual testing of all PRs in Dev and Prod
- [ ] Merged

Contributor guide

Open the contributing guide

Research direction

Start with the FireBAT interface and the linked Figma design, then trace how selecting a Fire Centre populates the station and fuel table. Implement the 4,000+ filtering and the failing-station error link to the Calculator, and verify the acceptance criteria, test coverage, documentation, and manual behavior in Dev and Prod.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, react
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.