search

NewGraphEnvironment / fish_passage_skeena_2023_reporting

https://newgraphenvironment.github.io/fish_passage_skeena_2023_reporting
Creative Commons Zero v1.0 Universal
0 stars 2 forks source link

Two way workflow #68

Closed lucy-schick closed 4 months ago

lucy-schick commented 4 months ago

Script to add data from habitat_confirmations.xlsm to form_fiss_2023.gpkg because edits were made by hand habitat_confirmations.xlsm. Workflow based on slack messages https://newgraph-2024.slack.com/archives/C06P2UXLDR8/p1714053672549609?thread_ts=1713995712.958749&cid=C06P2UXLDR8

I don't think we will ever need to use this script again (because we should be making edits in Q) so file name is not amazing, but thinking we can delete after.

NewGraphEnvironment commented 4 months ago

I don't think we will ever need to use this script again (because we should be making edits in Q)

Another note about QGIS inputs vs inputs with csvs to clarify how we can be flexible and make the workflow fit the many different and always evolving tasks.

QGIS inputs are really helpful when we want to visualize what is happening while inputing (ex. viewing stream names - trib to x creek, road tenure holder sleuthing, perhaps reviewing comments, etc.). When we have raw tabular data (like the 40 or so fish sampling sites mixed with 60 or 70 sites assessed with form_fiss_site) it can be more straight forward to input the data into a csv and join to the .gpkg (when possilbe) with R then export to another csv that will be used to copy paste into the Fish Submission Templates (shame we need to do that but seems to be our reality for now). Although no hard rules, we can consider that raw data to get info in - that is held elsewhere as well in the end (ie. the fish template) can be stored in data/inputs_raw.

Keep your eye on issues such as https://github.com/NewGraphEnvironment/dff-2022/issues/148 in dff-2022 as you help out b/c - until we write a new package or start a new repo for digital field forms (coming soon) - this is where we make the changes to this year's Mergin hosted input forms that should improve our data input and workflows for 2024/25. Remember and document that there are multiple places/standards where our forms come from and - when we can - we read those directly to try to make our input tools (ie. we make our form_fish_sample with the data submission template.

image