-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix species (and other?) issues in main census data #35
Comments
@jess-shue , these are issues that it would be wonderful to get your help with, if possible. |
@teixeirak I'd be happy to help with these during band replacements and possibly during the biannual survey. @ValentineHerr Would it be possible to make a single list of all of the various lists of species checks? Happy to do something myself, but could use some clarification/guidance on the third list. |
@jess-shue , I'm just flagging this again in case you get time to look at some of these this spring. The third list appears to be the fixes applied, but the one to address questions would be @ValentineHerr . |
@jess-shue , do we need to resolve this before making the maps, etc? |
@teixeirak I could take a look at these trees on the 18th. @ValentineHerr Could I have some clarification on the third list? Just the trees in rows 6-9 that need species checks, correct? |
Sorry for the delay @jess-shue. The third list is actually the place where we are writing down what we want to fix (it is read in R and implemented during the transition from raw data to cleaned data). (I'll edit the comment so it makes more sense). If you scroll the file all the way to the right, you'll be able to see a description of the issues we are trying to address. There may be overlap with the 1st and 2nd lists. Let me know if you have more questions |
@jess-shue, if we wanted to be super thorough we would check the trees mentioned in that 3rd list, to make sure we are fixing the issues correctly, but if you can get through list 1 and 2 that will already be great. |
@ValentineHerr Thank you for those details, sorry for misunderstanding the initial post! I will plan to check the species on the first two lists, and time permitting, double check things on the 3rd. |
I found a couple more errors: |
Deals with following issues Krista's comment in #35 >I found a couple more errors: >1- tag 121374 is marked as dead in the last main census but is alive, with a dendro band. >2- tag 60161 is marked as DS in the 2021 mort census but is AU, with a dendro band. Luke's comment in mortality issue here: SCBI-ForestGEO/SCBImortality#47 > I had the following notes. Although, I'm not totally certain on picking apart C. glabra from C. ovalis. > Tag 093481: species should be Carya cordiformis > Tag 093487: species should be Carya glabra And Jess's comment in mortality issue SCBI-ForestGEO/SCBImortality#96 >133461 - is the smaller tree and is a caco >131352 - was a large fram this is down and dead From Bert's PR #29 > 80180 should be a cagl > 131272 should be a fram
Deals with following issues Krista's comment in #35 >I found a couple more errors: >1- tag 121374 is marked as dead in the last main census but is alive, with a dendro band. >2- tag 60161 is marked as DS in the 2021 mort census but is AU, with a dendro band. Luke's comment in mortality issue here: SCBI-ForestGEO/SCBImortality#47 > I had the following notes. Although, I'm not totally certain on picking apart C. glabra from C. ovalis. > Tag 093481: species should be Carya cordiformis > Tag 093487: species should be Carya glabra And Jess's comment in mortality issue SCBI-ForestGEO/SCBImortality#96 >133461 - is the smaller tree and is a caco >131352 - was a large fram this is down and dead From Bert's PR #29 > 80180 should be a cagl > 131272 should be a fram
including fixing some more species things like for tag 60161 mentioned in this issue: SCBI-ForestGEO/SCBI-ForestGEO-Data#35
There are various issues that could be addressed/checked in the main census data.
See these 2 lists of issues:
And where we will store the solutions:
The text was updated successfully, but these errors were encountered: