secondary stems that are now the only stem >10cm

[ValentineHerr]

@rmh24 and I just noticed that some stems (16 of them) only show up in the stem file and not in the tree file.
This is either due to the fact that the main stem was dead or that it remained under 10cm.

The problem is that now those 16 stems can't be accessed via the app (they don't have coordinates associated to them).

We don't want to rebuild the app, so we are going to collect those stems manually, and create a csv file that will be read and attached to data within the script.

This is the list of tags of those secondary stems:
c(10494, 10550, 12211, 12233, 32031, 40969, 50019, 50169, 50474,
50515, 60040, 140674, 182671, 22198)

I am opening this issue so next year we are aware of it and think of a solution to remediate it because it may become more and more common.

We can think of two solutions:

1. instead of filtering by stem, filtering by trees --> include all stems of a tree that has any stem meeting our inclusion criteria
2. map all stems (and not trees) in the Field Maps app. We just checked with @rmh24 that all trees show up when the general area of a clump of trees is clicked on in the app, and so we think that it might work the same if all stems were mapped.