Equivalent Clearcut Area (ECA) results for Watershed Management Level (WML) 3-2 (3000) sub-watersheds within the Kispiox River Watershed. WML3-2 sub-watersheds are WML3 sub-watersheds with multiple WML2 mainstem sub-watersheds. Prepared by Eclipse Geomatics Ltd. in April 2023 for SkeenaWild Conservation Trust.
This work builds on the Peak-Flow-Sensitivity (PFS) assessment work completed by Lake Babine Nation, BC Ministry of Forests, Lands and Natural Resource Operations and Rural Development, Northern Habitat Solutions, and SKR Consultants Ltd. in 2020, which computed PFS scores and ECA risk categories for Watershed Management Areas (WMAs) at six Watershed Management Levels (WMLs) in the Kispiox River Watershed Atlas Group.
Unique feature identification number (row number sorted by FSW_WMA_NAME)
FSW_WMA
Watershed Management Area Name
Fisheries Sensitive Watershed WMA name from SKR (2020)
LAYER
Layer Name
Name of original kml spatial layer from from SKR (2020)
WML
Watershed Management Level
Corresponding WML from SKR (2020) as text with WML3-2 (WML3 with multiple WML2 mainstems) differentiated
FSW_MGT
Watershed Management Level
Corresponding WML from SKR (2020) as numeric
GNIS_NA
Gazetted Watershed Name
Gazetted watershed name from BC Freshwater Atlas associated with WMA from SKR (2020)
WS_KM2
Watershed Area
Total area of WMA in square kilometers (calculated by EGIS)
ECA_KM2
ECA Area
Total area of ECA in square kilometers (calculated by EGIS)
ECA
ECA Percentage
ECA as a percentage of the MWA (i.e. 100*(ECA_AREA_KM2/ WATERSHED_AREA_KM2) (calculated by EGIS)
LOW_RSK
Low Risk Threshold
FSW_WMA_Percent_ECA_Trigger_to_Low_Risk derived by SKR (2020)
MOD_RSK
Moderate Risk Threshold
FSW_WMA_Percent_ECA_Trigger_to_Mod_Risk derived by SKR (2020)
HIGH_RS
High Risk Threshold
FSW_WMA_Percent_ECA_Trigger_to_High_Risk derived by SKR (2020)
RISK
Risk Rating
Risk rating based on ECA result in comparison with risk triggers. Very low: < LOW_RISK_TRIGGER Low: ≥ LOW_RISK_TRIGGER & < MOD_RISK_TRIGGER Moderate: ≥ MOD_RISK_TRIGGER & < HIGH_RISK_TRIGGER
Comments (0 total)
Log in to add a comment