-
This is a late entry from the half-bakery, a rough idea about squashing multiple texts together. It is I think similar to but not the same as an idea @rebeccacremona has mentioned. I have in mind some…
-
This site seems odd to me:
- This crossing was already assessed in 2022 and has a natural falls which ranks as a barrier
- There is a crossing just downstream that is still unassessed
- when lookin…
-
too many tables when split by watershed group. being able to filter will be really helpful for more than just the watershed
-
- [x] `residual_pool_depth_m` present on fiss site card but missing in form, added to form.
- [x] comments say "fished outlet pool, approx 6m squared" but `Site length` = 6 and `wetted width` = 5.3 w…
-
-
- [x] culvert and pscis assessment ~55m away from modelled crossing. Need to fix in https://github.com/NewGraphEnvironment/bcfishpass/blob/main/data/pscis_modelledcrossings_streams_xref.csv
- [x] Ups…
-
could be any bcdata table with any filter/select combo. will come in handy for more than just fish passage
-
should tell user to assign those params to the columns that already contain partial match of `easting` (ex. utm_easting) and `northing` (`utm_northing`)
so that we don't add easting and northing co…
-
If we want a stable database and reports, new PSCIS crossings should not be included in the bcfishpass db without first being reviewed by a human - crossings on unmapped tribs are incorrectly snapped …
-
Documenting how we QA the form fiss 2023 so others can understand the process. Hoping we can use this to update onboarding or https://github.com/NewGraphEnvironment/fish_passage_template_reporting at …