...
Because of this and rows in the mapping have a 1:1 relationship with an FoI (i.e. a parameter cannot belong to more than one FoI), the data will be separated into three tables for processing: survey-plant population, survey-plant individual and opportunistic-plant occurrence.
Survey columns individuals
Select data for survey only
| Code Block |
|---|
bdbsa.supatch."SITETYPE" = 'SU' |
2. Separate Select data for individuals using DBH as key
| Code Block |
|---|
"DBH" is not null |
3 . For individuals the following variables from the suspecies table will be ingested:
PLANTEDRELEASED_individual, CROWN_EXTENT_PERC, CROWN_EXTENT_SCORE, CROWN_DENSITY_PERC, CROWN_DENSITY_SCORE, DBH, NEW_TIP_GROWTH, EPICORMIC_GROWTH, EXTENT_REPRODUCTION, MISTLETOE_LOAD, LEAF_DIE_OFF, LEAF_DAMAGE, EXTENT_BARK_CRACKING
Notice that the following columns need to be created for both individuals and populations “PLANTEDRELEASED” and species_name columns into “PLANTEDRELEASED_tree” and “species_name_tree”
| Code Block |
|---|
"DBH" is not null |
and tree”and “PLANTEDRELEASED_population” and “species_name_population”
...
4. The scientific name of the species comes from matchin the NSXCODE column from suspecies to flvnonsynnotren table.
Opportunistic columns
Select data for opportunistic only
...