You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@NewGraphEnvironment as per this comment on a bulkley issue regarding this. Is the same still true for this report? Am I replacing co_rearing_km with st_rearing_km?
The text was updated successfully, but these errors were encountered:
I ran script section for habitat gain with new bcfishpass object and st_rearing_km and there are 3 sites that have 0m of upstream habitat length modelled. These are 198215, 8530, and 198236. Am I going to estimate these three using GIS?
Depends if they can be tied to the modelling with this or not (8530 definitely can). If they can, then we will ammend the csv, PR and I will run again later once bcfishpass is building from scratch again (should be soon). Otherwise we can use GIS but we should try to align the estimate with what the model will output
They are all tied to modelled crossings yes. So I'm adding all 3 of those sites to Simon's csv? Maybe I'm not fully understanding this. Do these 3 sites have 0m of upstream habitat modelled because steelhead have never been observed in the streams? Or have these streams just not been modelled with bcfishpass yet?
@NewGraphEnvironment as per this comment on a bulkley issue regarding this. Is the same still true for this report? Am I replacing
co_rearing_km
withst_rearing_km
?The text was updated successfully, but these errors were encountered: