ASA - Additional Grids: Elevation - Front End

[conbrad]

As a recipient of a FBA, or I want to show the local fire environment context that's driving the advisory So That it is clear what elevations the advisory pertains to

Acceptance Criteria

• [ ] For each elevation, we display the advisory status based on the % of combustible land area under advisory/warning, based on the Threshold Slider;
• [x] Elevation attributed by advisory and warning HFI levels
• [x] Sidebar chart would illustrate the advisories and warnings based on either elevation classes, gradients, topographic position index grid (see 3159)
• [x] Given a Fire Zone: Valley Bottoms vs Mid-slope vs Upper Elevations (or any combination thereof - use checkboxes?)
• [ ] When you click on a zone, the percentage breakdown is displayed in the information panel
• [ ] Remove existing elevation stats in the frontend, table we store the current stats in, and associated models.

Additional Context Backend = #3696 Aim to avoid false predictions that may be affected by snow melt.

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

https://design.penpot.app/#/view/5fc21da5-c28b-817c-8004-348443092545?page-id=93732509-be23-80b0-8004-352e0034b2de&section=interactions&index=0&share-id=df60c394-e535-80b3-8004-3cf6d339eca8

[conbrad]

This ticket will need more refinement when we get into the visualization implementations, and most likely will be split up into further tickets. The file below is captured to provide some lo-fi initial mockups of what elevation and aspect visualizations could look like for advisories:

https://app.zenhub.com/files/235861506/7ed7a060-e7ce-423f-94dc-2f699ed8d315/download

[conbrad]

Resolutions: Fuel Layer: Should be the same resolution in SFMS, affects calculations Elevations, Slope, Aspect: Align on SFMS resolution now, potentially add higher resolution layers later

[rajpersram]

I'm curious about possibiliities and practicalities of perhaps using a map layer on the main page (instead of the sidebar chart suggested in the above link) that can represent elevation-related burn rates. The inspriration for this comes from https://bookdown.org/mcwimberly/gdswr-book/application---wildfire-severity-analysis.html. In particular,

• FIGURE 11.6: Vector data characterizing WUI classes for the High Park fire.
• FIGURE 11.8: Raster data distance from the nearest WUI for the High Park fire.
• FIGURE 11.11: Slope angle within the boundary of the High Park fire.

Perhaps the illustration types along with an elevation threshold selection could narrow down areas of highest risk.

[rajpersram]

The Figma mockups are posted here, ready for discussion with team. There are three design candidates listed with notes describing each.

[rajpersram]

For discussion with team: Last AC. Question: Does the Figma mockup with the elevations listed cover all these elevations? Not sure what the checkboxes could be for.

[rajpersram]

Second draft of Elevation risk available in Figma here. Ready for discussion.

[rajpersram]

Updated version in PenPot found here (use arrows at bottom of screen to go to 2 of 2 pic). Ready for discussion.

[rajpersram]

Each fire zone picks the highest elevation and that measurement is used on the elevation labels.

[rajpersram]

Figma mockup for Topography info (ASA - FBA Draft 3 - MVP 1) found here.

[rajpersram]

Assets

As jpg

As svg