-
Notifications
You must be signed in to change notification settings - Fork 1
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
Analysis of the infraspecific taxa #59
Comments
My gut feeling is that each line in the file should be independent. Therefore, if there are alien and native subspecies present in Belgium, then only the alien subspecies should be in the list. Whereas, when all the subspecies are present you a row for the species could be added without creating exceptions. |
My thoughts:
I'm not sure how we can easily assess that: how do we know we have all?
Not really sure what the benefit of that is. We wouldn't even be able to express that something is non-native. So, I would say it's up to the analysis (e.g. occurrence indicators) if infraspecific taxa should be lumped. One thing we could try to tackle is being smarter about lumping infraspecific taxa and species when both are present in source lists. So if one source checklist has |
Thanks @qgroom and @peterdesmet for your insights. @peterdesmet: I have just checked: there are no infraspecific taxa and their related species in unified. But it's good you put the question for the future. Listing only the species could be dangerous as we risk to lose a lot of information. In case of @timadriaens : can you check in the file I made which infraspecific taxa belong to group 2? I don't think they are many... In this case then we can lump at indicators level as proposed by @peterdesmet. |
I would merge those just like we merge same taxa across checklists. So if date info is available for just one, it will be included. And in case of 2008-2012 + 2006-2014, it will become 2008-2014. |
@damianooldoni I have checked the list to see if the taxon is alien/native at specieskey level but only the ones I knew. There are indeed quite a few subspecies of native species that are alien, will have different information on dates etc. and I feel the unified should definitely keep those. Trachemys scripta, Ludwigia peploides and Ludwigia grandiflora are Union List species so the information on them in the indicators (e.g. for the pathways) will not be ok presumably (as for the pathways, we do not have the subspecies taxonkey in the list of union list species). That is presumably why they were lacking from the protected areas analysis. For the "number of introductions" indicator, I would also keep it at taxon level as this indicator is trying to visualize the number of introduction events more than the number of species. In brief: I would NOT start to lump intraspecific taxa. But for the Union List species, I pragmatically propose to
What do you think @qgroom @peterdesmet ?
|
Reference file added in indicators repo: https://github.com/trias-project/indicators/blob/master/reference/assessment_alien_status_species_with_alien_infraspecific_taxa.tsv. @qgroom: as most of the species/infraspecific taxa are plants, feel free to fill the field |
@timadriaens found strange that there was no analysis of
Trachemys scripta
, although this species is in the Union list of concern species. The answer was simple: in the unified there are three subspecies of it, but not the species itself (see www.gbif.org/species/163636890), although it is an alien species.Why are there infraspecific taxa in unified and source checklists? There are two possible reasons, so we can divide such taxa in two groups:
Subspecies of
Trachemys scripta
belong to second group as the 3 subspecies have different date of first observed in ad-hoc checklist (see raw dump). But the species itself is alien...So, how to distinguish infraspecific taxa of group 1 from those of group 2? An idea could be to add the species to taxon core without extensions, so no informations about pathways, native range, distribution etc. are present as they are specified at infraspecific level.
This solution will not affect checklist indicators at all as they are based on the information in the extensions. For occurrence indicators we should add a step in the pipeline for making the cube to avoid doubling the number of occurrences, but it is feasible.
In this file, infraspecific_alien_taxa_source_info.txt, you can find a list with all infraspecific taxa in the unified with their source checklist where
key
is the key of the taxon in the unified (e.g. 152543132) andnubKey
is the key of the corresponding taxon in the GBIF backbone (e.g. 6157050).@timadriaens and I think it is worth to find them. They should not be so many.
@peterdesmet, @qgroom & co.: what do you think about it? Is it something to add at unified level? Or at source checklist level?
The text was updated successfully, but these errors were encountered: