modelled crossing stability / change report

[smnorris]

Office reviewed modelled crossings will have associated records in fix tables and external reports.

If roads associated with modelled crossings are removed from the source inventories (DRA/FTEN etc), the modelled crossing is silently dropped from bcfishpass on the next weekly refresh, orphaning any fixes/reporting data.

It isn't obvious to me how we want to handle these, that requires some consideration - should all mapped crossings ever generated be retained in the database?

An auto generated report of additions/deletions is a simple step that would help with tracking for now.

[smnorris]

eg 1006800220, a trib to Harpers Lake in Horsefly. Unassessed crossing on private road is not currently present in DRA - so the crossing is no longer present in bcfishpass.

Currently workaround is to add missing record to user_crossings_misc.csv. Thankfully the ids for this table are not auto-generated, so the crossing id can be retained.

[smnorris]

A report is probably fine.

Only modelled crossings with additional data are at issue. For crossings with fix records, we could automatically retain crossings where it makes sense (eg, flagged as a known barrier)

But for reporting, bcfishpass scripts do not presume the db has access to wcrp reporting/tracking tables, automatic retention would not currently work.

Instead of fixing on bcfishpass side, I'd lean to de-coupling WCRP reporting from the provincial model - only adding/deleting crossings as needed and not automatically refreshing from the latest. This could be a part of a larger fix where plans are run individually for much faster turnaround.