bcgov / bcgov/wps

ASA: Topographic Position Index statistics

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

Description

**As a** person issuing or receiving fire behaviour advisories

**I need** general information on what elevations advisory conditions are expected

**So That** I have better topographic context, i.e.) valley bottom, mid-slope, ridge top.

**Acceptance Criteria**
- [ ] Given advisory conditions are present in a fire zone unit, When I select a fire zone unit on the map, Then the elevation statics shown in the left side panel provide the proportion of advisory cells in valley bottom, mid-slope, and ridge top.
- [ ] All HFI values >= 4,000 kW/m can be used to create a single bar chart for the three topographic classes similar to the Combustible Land Under Advisory or Warning chart.
- [ ] Remove min/max elevation statistics table.

**Additional Context**
- Classified Topographic Position Index (TPI) grid to be created ahead of time before this story can be actioned.
- Could consider using surface roughness grid to define the size of the moving window used for the TPI calculation.
- Resolution of the TPI grid needs to match the SFMS outputs (2000 m).

TPI - https://blogs.ubc.ca/tdeenik/2021/02/16/topographic-position-index-tpi/

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

Contributor guide

Open the contributing guide

Research direction

Start by locating the existing Combustible Land Under Advisory or Warning chart and the left-side fire zone unit statistics panel. Confirm that the classified TPI grid prerequisite exists at the 2000 m SFMS resolution, then trace how advisory cells and HFI values are supplied. Done means showing the three topographic proportions, charting HFI values >= 4,000 kW/m, and removing the min/max elevation table.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.