habitat model - include wetlands about bcfishpass HOT 6 CLOSED

This was the issue that popped when I searched edge so I’ll just throw it here. Another vote for including edge codes within the parameters table is related to intermittent versus non-intermittent streams. With those codes in our pocket in theory users can tweak model outputs more easily to cater to intermittent versus intermittent streams. That would be of benefit for speeding/sorting queries related to field site prioritization.

from bcfishpass.

I'll reopen to keep this showing up in the list

from bcfishpass.

Thank you. Along with edge codes and spawn/rear params, storing species access model gradient threshold values in the parameter files would provide wonderful transparency and flexibility too.

from bcfishpass.

Adjusting IP models (beyond discharge and slope thresholds) via parameters would be nice but I think adjusting the IP queries as required for now is fine. I've accepted that reporting is different for each project and each project needs its own database. Perhpas the code repository can hold several different models and the user can choose which ones to drop in.

from bcfishpass.

Might be worth considering adding edge codes to docs and read_me.mds of habitat models (and access perhaps - my apologies if it is there already and I missed it). Lots of species and model decision based nuances wrapped up in the edge codes and a link to fwa guide might be a good addition

https://www2.gov.bc.ca/assets/gov/data/geographic/topography/fwa/fwa_user_guide.pdf

from bcfishpass.

👍 Full documentation of spawning/rearing models (including this) is coming soon.

from bcfishpass.