Occurrence processing for Belgium (CUBE BE) about occ-cube-alien

[peterdesmet]

I would say: querying from GBIF.

[damianooldoni]

@peterdesmet: For step 1, filtering on alien species
should we filter by downloading the unified checklist from GBIF or by using the GitHub version from https://github.com/trias-project/unified-checklist? Using GBIF checklist would make workflow more repeatable worldwide.

[damianooldoni]

Here below how I get three data cubes, one for each of the three filters mentioned above.

1. For alien taxa where rank = SPECIES and taxonomicStatus one of ACCEPTED or DOUBTFUL:

year	eea_cell_code	speciesKey	n
1792	1kmE3865N3144	2769766	1

Occurrences referring to species synonyms, subspecies/varieties and their synonyms are automatically included.

2. For alien taxa where rank below SPECIES and taxonomicStatus one of ACCEPTED or DOUBTFUL:

year	eea_cell_code	acceptedTaxonKey	n
2018	1kmE4012N3120	6411098	3

Occurrences referring to synonyms have been included in the query, that means searching occurrences where acceptedTaxonKey is one of nubKey from unified checklist. Contrarely to name data, in occurrence data the field acceptedTaxonKey is always present and it is equal to taxonKey in case of not synonyms (see issue in gbif checklistbank repo).

3. For alien taxa where taxonomicStatus is NOT one of ACCEPTED or DOUBTFUL, i.e. synonyms:

year	eea_cell_code	taxonKey	n
1940	1kmE3927N3130	3022668	1

Occurrences where taxonKey is one of nubKey from unified checklist.

Question

How to call the column name containing speciesKey/acceptedTaxonKey/taxonKey?

Possible solution

My suggestion is to use column name taxonKey:

year	eea_cell_code	taxonKey	n
1792	1kmE3865N3144	2769766	1
2018	1kmE4012N3120	6411098	3
1940	1kmE3927N3130	3022668	1

@peterdesmet: what do you think?

[damianooldoni]

Discussed with @peterdesmet : we use taxonKey.

[damianooldoni]

Done. Documentation about structure and workflow added in README.md of the repo. Issue can be closed or left for informative reasons.