Tree 40942 and 182471 not in biannual survey but listed in intraannual survey

[jess-shue]

@rudeboybert @teixeirak

1. Need to confirm the status of tree 40942 - it was removed from the biannual survey this year, but is still in the intraannual survey.

• OK to remove from intrannual, or does it need to remain in the survey and return to the biannual data collection as well?

3. Tree 182471 - ceca (redbud) was newly added this year, but only appears in the intraannual survey

• OK to add this to dendro_trees and the biannual survey?

I realized there were a few discrepancies in the new version of dendro_trees.csv I merged this morning and these are two corrections I could use your input on before hopefully finalizing the updates.

[teixeirak]

Thanks, @jess-shue. Without fully understanding these specific cases,
(1) any tree in the intraanual survey should be in biannual as well. It looks like we only have 3 acru in the biannual survey (compared to target of 4), so definitely keep.
(2) That should be okay. From the google doc it appears that we were supposed to have some new biannual -only CECA.

[jess-shue]

OK, these updates have been made to dendro_trees.csv
We will need to make sure these trees are included in the fall biannual survey data when the time comes.

[jess-shue]

@rudeboybert @teixeirak
Sorry I dropped the ball on this! It looks like I updated dendro_trees, but these changes actually weren't included; not sure what happened!
I'm going to update dendro_trees:

1. Remove the end date for 40942. From what I can tell, we missed measuring this band during the spring biannual survey, but it has been measured during the intraannual measurements this year.
2. Add 182471 to dendro_trees as a biannual and intraannual tree.

There are 7 trees missing from the data_entry_biannual_spr2022.csv file - they are in the 'fix' files.

1. Should I add them to the data_entry_biannual_spr2022 file and push it to GitHub with these updates? I guess the data_entry_fix files need to be manually incorporated as things get a bit complicated in those files.

Hoping to prepare the fall biannual field form and update the maps - again, thought I had updated the maps but that doesn't appear to be the case.

[rudeboybert]

Hey @jess-shue I think it's fine to add those 7 missing stems to data_entry_biannual_spr2022.csv with NA missing measurements.

I see Wed Nov 9 is the tentative biannual survey date. I'll be sure to keep time slots open in the week preceding that date to help out if need be.

[rudeboybert]

However please don't close this issue until after the fall biannual survey is done, in case there is something in the repo that needs to be changed to that this is streamlined for next fall