Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ASA: Add topographic position information to advisory bulletin #4196

Open
1 task
nealmcloughlin opened this issue Jan 10, 2025 · 0 comments
Open
1 task

ASA: Add topographic position information to advisory bulletin #4196

nealmcloughlin opened this issue Jan 10, 2025 · 0 comments
Labels
4Refinement this ticket is ready for refinement with the team Task Technical task that cannot be written as a user story

Comments

@nealmcloughlin
Copy link
Collaborator

Describe the task
Update the automated text bulletin for fire zone advisories and warnings to be more descriptive about what topographic positions are of concern based on percentage of each topographic position under advisory.

Acceptance Criteria

  • Auto-generated text includes topographic positions to watch out for whenever the percentage of a topographic position (valley bottom, mid slope, upper slope) under advisory is >50%. If the percentage of a topographic position is <= 50% then it is not mentioned in the text bulletin.

Additional context

  • Refer to updated percentages in ASA: TPI percentages in dashboard infographic #4194
  • Here is example wording: "There is a fire behaviour Advisory in effect for G3-Robson Valley Fire Zone between 08:00 and 23:00. C-3 and C-7 fuel types account for 75% or more of today's total advisory area. Also watch out for C-2 and S-3 fuel types which occupy a small portion of the zone but are expected to be under advisory conditions wherever they occur. Advisory conditions are expected across 65% of valley bottoms."

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

@nealmcloughlin nealmcloughlin added 4Refinement this ticket is ready for refinement with the team Task Technical task that cannot be written as a user story labels Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4Refinement this ticket is ready for refinement with the team Task Technical task that cannot be written as a user story
Projects
None yet
Development

No branches or pull requests

1 participant