Set up data and scripts for 2022 season #114
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update branch
…last row in data_entry_fix_2022.csv. So I'm switching this one to 1139
… from 2018 census so I added them
This was referenced Apr 3, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A ton of changes:
#89 Identify which bands need replacing
#90 Combine field form and raw data: Now only single form to take in field, whether iPad or print out
#97 Sampling strategy for new bands: Carefully reallocated (species) x (intraannual vs biannual) distributions of bands. Summarized in this Google Sheet (note final counts in the end differed a small bit)
#100 Update CSV's (still need to update
dendro_trees.csvhowever)#106 Fix dendrometer bands with double springs