Trib to Missinka models as potentially accessible but no crossing present

[NewGraphEnvironment]

@lucy-schick spotted this one

linear_feature_id = 165107895

[smnorris]

That segment is coded in the FWA as being downstream of PSCIS 125191 - because blue_line_key 359016386 is a side channel / distributary of blue_line_key 359502337.

To avoid this issue, future models could build the network directly from the stream geometries (rather than using watershed codes), but that would be a big change - we have to live with this for now.

There is something slightly weird going on though - that took me longer than it should to diagnose because clicking on that feature in QGIS shows an empty value for the column barriers_pscis_dnstr. The correct data is present in the view (see below) - but is not showing up in QGIS. It shows up fine if querying streams_vw.

bcfishpass=# select barriers_pscis_dnstr from bcfishpass.streams_vw where linear_feature_id = 165107895;
 barriers_pscis_dnstr
----------------------
 125191
(1 row)

bcfishpass=# select barriers_pscis_dnstr from bcfishpass.streams_bt_vw where linear_feature_id = 165107895;
 barriers_pscis_dnstr
----------------------
 125191

edit - it is just something peculiar going on in the layer file from the bcfishpass repo. If I add streams_bt_vw directly from the db & click on the stream - the value is shown without issue.

[NewGraphEnvironment]

cool. ya - we have seen other anomalies in how the layer file shows other info that can be remedied with a reload of the layer and re-symoblizing. It was happening to us before with the observed species upstream and downstream so I think it may be an issue related to how QGIS "sees" arrays