mapping

[NewGraphEnvironment]

@smnorris - geopackage is populated here

not sure the best approach for version control of the project maps hosted on the Hillcrest site. Using the date stamp of the map as the name of the subfolder one way to go but maybe only necessary on the last version? Until then we could have a subfolder “NewGraph” for these maps if there are multiple versions of maps on the server. Not sure.

still interested in using q atlas and the watersheds to build tighter maps for each hab con but think they need to have legends and keymaps .

[NewGraphEnvironment]

mapping files are now pulled from geopackage then burned to geojson format in fishpass_mapping with b2f3d0d8

[smnorris]

If you convert to WGS84 / EPSG:4326 they will preview nicely in GH

[NewGraphEnvironment]

🔥

[smnorris]

We now have habitat model data for Bulkley, and potentially for Morice as well.

Do we want to change the mapping to vary the stream symbol width by habitat classification rather than by gradient?
ie
narrow=non spawning/rearing habitat
medium=rearing
wide=spawning.

Retain the same accessibility colour scheme.

[smnorris]

Of course there is also the option to symbolize stream width by the modelled channel width, but modelled habitat seems more relevant.

[smnorris]

Updated spawning/rearing classification should be ready in the next day or so smnorris/bcfishpass#46

[NewGraphEnvironment]

I have had a look through but can't seem to find it. Sorry. Where are the gradient thresholds for the accessibility? I am thinking about steelhead vs. salmon vs. WCT ...

[smnorris]

Salmon = 15
Steelhead = 20
WCT = 20

This is a good point. The accessibility mapping colours for Bulkley are currently based on steelhead (20%). Symbolizing based on salmon habitat will mean that steelhead accessible streams above a 15% gradient barrier won't show any habitat.
My mistake, steelhead habitat is modelled.

[smnorris]

FYI the access classification logic is buried in here: https://github.com/smnorris/bcfishpass/blob/main/02_model/sql/model_access.sql

[NewGraphEnvironment]

We now have habitat model data for Bulkley, and potentially for Morice as well.

Do we want to change the mapping to vary the stream symbol width by habitat classification rather than by gradient?
ie
narrow=non spawning/rearing habitat
medium=rearing
wide=spawning.

Retain the same accessibility colour scheme.

We would pick a "species" based on 02_model/data/model_spawning_rearing_habitat.csv to vary the stream symbol width by habitat classification?

[smnorris]

Rather than pick just one species I was thinking of lumping all spawning into one class and all rearing into another.

[NewGraphEnvironment]

Sound like a good plan. Let's do it.

Hoping for some background on the width modelling and some references for habitat requirements from CWF soon 😶 . I shared my thin zotero modelling folder with you and Nick. We can keep a copy of our references there if that works for you guys.

[NewGraphEnvironment]

Simon. Any chance of a refresh on the maps with Jonathan's barriers now input and an update to the gpkg pushed to data/fishpass_mapping? Shooting for the end of the day to get a draft of the report to CWF and FPTWG (no real morice section yet)... I doubt anyone will look at it right away so don't think it would matter too much if the maps were updated tomorrow...

[smnorris]

Can it wait another couple of days? I am working on the spawn/rear connectivity updates, it would be nice to finish that first: smnorris/bcfishpass#46

The in-stream distance thresholds mean I'm fixing this up so it works properly
https://github.com/smnorris/fwapg/blob/main/sql/functions/FWA_LengthInstream.sql
edit - found a way around this so that function isn't getting cleaned. It should probably be removed until it is.

[NewGraphEnvironment]

Sure. I was just thinking that I should get a bit more of the methods documented and bring some area tables in to the results anyways. Needs to be done for the Morice anywho.

Maybe it’s done already but shouldn’t be too hard to add areas of streams by spawn/rear per species right? Will make a lovely table and might even read easier as a graph. Lots of info but I think the reader can handle it and we can tuck it into a leaflet link too so it is tight and available.

I’ll start looking at it tomorrow. Going to have another crack at getting the bcfishpass repo to run for me. 🤞