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

Add electrofishing site data to `habitat_confirmations.xls` #64

Closed NewGraphEnvironment closed 5 months ago

NewGraphEnvironment commented 6 months ago

some documentation of this process here. https://github.com/NewGraphEnvironment/fish_passage_template_reporting/issues/8

Sites were only enclosed at Thompson downstream sites which also have a second pass on the following day. We tested our efficiency by seeing how many of our captured fish had tags the next day (ie. we put the fish back into our enclosed sites after our first pass and fished them again the next day)

NOTE - for Thompson h/p should not be 2 teh second day since the fish were put back in. Also - the downstream sites were enclosed. temperature, conductivity and Turbidity were likely different second day too - card will tell us - should be recorded

NewGraphEnvironment commented 6 months ago

Actually - I think we are going to need to leave h/p as 2 for Thompson second day to avoid other complexity. We can just put a note in Step 2 that fish were returned to the site after the first pass.

lucy-schick commented 6 months ago

A couple sites that were a bit funky and have missing data:

lucy-schick commented 6 months ago

Next time, update/add data in step_4_stream_site_data spreadsheet from fiss and fish cards, then when you run the scripts in extract_inputs.R to populate step_2_fish_coll_data you will have all the correct data. I edited that data once it was already in step_2_fish_coll_data which meant I also had to edit the data in step_4_stream_site_data... still learning!

Data that was added by hand. Noting this down in case it needs to be re done... which would not be fun! Beware that some info was taken from fish cards and some from fiss cards

NewGraphEnvironment commented 6 months ago

This is great! Thank you.

Next time, update/add data in step_4_stream_site_data spreadsheet from fiss and fish cards, then when you run the scripts in extract_inputs.R to populate step_2_fish_coll_data you will have all the correct data.

Another (and potentially preferred option from my perspective) would be to add the data to data_field/2023/form_fiss_site_2023.gpkg in QQIS, track the changes in version control in the repo via fpr_sp_gpkg_backup, export to csv with scripts/fiss_site_tidy.R (template file is here https://github.com/NewGraphEnvironment/dff-2022/blob/master/scripts/fiss_site_tidy.R but likley now needs updateing) and copy paste over step_2_fish_coll_data

lucy-schick commented 6 months ago

Yes I agree I think that is the best way to do it (see slack message).

NewGraphEnvironment commented 6 months ago

logging ad hoc changes required to build reporting objects here as am doing so in main fish submission spreadsheet. Related to https://github.com/NewGraphEnvironment/fish_passage_skeena_2023_reporting/issues/102

step_3_individual_fish_data

step_2_fish_coll_data

image