Skip to content
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

Sapling Data Missing Species #133

Open
blcampbell opened this issue May 22, 2019 · 1 comment
Open

Sapling Data Missing Species #133

blcampbell opened this issue May 22, 2019 · 1 comment
Assignees
Labels
data issue Issue lies in the underlying data instead of the application or database structure/functionality

Comments

@blcampbell
Copy link
Contributor

Several records (8) have a no species listed for a tag.

Event_Date | Plot_Name | Tag

8/11/2009 | PRWI-0648 | 9963
8/28/2009 | HAFE-0161 | 14222
7/8/2013 | PRWI-0648 | 9963
7/29/2016 | PRWI-0783 | 8825
5/17/2018 | NACE-0490 | 23050
5/17/2018 | NACE-0490 | 23047
5/17/2018 | NACE-0490 | 23019
5/17/2018 | NACE-0490 | 23048

Fix
Recommend these be set as 'unknown' unless there is a viable reason for species to be missing.
Sapling data Habit values would be updated to the default for 'Unknown' species (Tree) unless otherwise known.

This item also relates to #103, #129, #130, #132 for sapling data Habit cleanup.

@lizmatthews03 , @johnpauls , @abrolis please review fix for validity.

@blcampbell blcampbell added the data issue Issue lies in the underlying data instead of the application or database structure/functionality label May 22, 2019
@blcampbell blcampbell added this to the 2019 Pre-Season Updates milestone May 22, 2019
@blcampbell blcampbell self-assigned this May 22, 2019
@blcampbell
Copy link
Contributor Author

Per our discussion these records primarily are from saplings which have been removed from study, however two ( 9963 & 14222) include data where the sapling status is not set (14222) yet the tag status is (RIO).

14222:
Sapling status should be set to RFS (removed from study) for this record.

9963:
Sapling status currently is out of sync with the RFS flag noted at the tag level (which is set as RFS).
Sapling status is currently Alive Standing.
In addition, there is a note in tag history showing this sapling is alive standing on the following dates: 8/11/2009, 7/8/2013, 8/2/2017 even though the tag shows the tag was a sapling on 8/11/2009 and a dead sapling on 7/8/2013.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data issue Issue lies in the underlying data instead of the application or database structure/functionality
Projects
None yet
Development

No branches or pull requests

1 participant