NewGraphEnvironment / fish_passage_skeena_2023_reporting

https://newgraphenvironment.github.io/fish_passage_skeena_2023_reporting
Creative Commons Zero v1.0 Universal
0 stars 2 forks source link

198217_ds_ef3 - Tributary to Skeena River #84

Closed lucy-schick closed 5 months ago

lucy-schick commented 5 months ago
NewGraphEnvironment commented 5 months ago

ya - good call - lets make the numbers work to get to 6m and keep all the detail we can in the comments

lucy-schick commented 5 months ago
lucy-schick commented 5 months ago

After thinking about this a bit more, for the 2024/25 season maybe we should add a column to the fiss form for the actual electrofishing site length, and could have an option saying "same as site length" which is most common, but would also allow for cases when the ef site length is different than the actually assessed site length . We could then use the ef site length for this calculation https://github.com/NewGraphEnvironment/fish_passage_skeena_2023_reporting/blob/main/scripts/01_prep_inputs/0100-extract-inputs.R#L871

I think it would be helpful for resolving cases like this where the length of stream assessed for the habitat assessment is truly 6m but only one small pool was shocked, therefore the ef site length is much less than 6m. Even more so for https://github.com/NewGraphEnvironment/fish_passage_skeena_2023_reporting/issues/78 where the site length was 25m but reduced to 2 to get the correct area.

Was just reading through https://www2.gov.bc.ca/assets/gov/environment/natural-resource-stewardship/nr-laws-policy/risc/recce2c.pdf and having separate ef and assesment site length would allow for the assessment site length to be closer to "be at least the greater of 100 m or 10 times the bankfull width (Wb). " as seen on page 86.

We could add an ef site length column and also write it on the fish cards. Can link to https://github.com/NewGraphEnvironment/dff-2022/issues/148 if we want to move forward with this.