-
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
Determine a logical gbif records threshold #7
Comments
OK, I played around a bit with those. My proposal for criterium:
This should leave the following number of species:
|
I find it striking though that none of the species occur twice in both climate classifications for Belgium. |
If we are a bit more severe on the criteria:
current: 14
current: 10 @adrienlatli can you take a look at the above list and tell us if that is workable? Do we want to land at around 30 spp to risk assess or do we go for less? |
Great Job Sander thx. I think 30 spp to risk assess is realizable by Romain. This number could be improve if they find new species in shop but I'm think it's still feasible. @timadriaens : If you can add Romain to Github it's must be usefull :-) (WILLEPUT Romain Romain.Willeput@ulb.be) |
ok! we need his github name for that |
@adrienlatli OK, calculating back from those 30 species I propose the following cut-offs (it appears the total number of records on gbif is more limiting than the degree of KG overlap):
This leaves exactly 30 species. speciesAstacopsis franklinii @SanderDevisscher can you rerun using those selection criteria? |
@adrienlatli can you provide his github username ? |
#7 Current thresholds: total number of gbif records at least 90 with at least 20% climate match
In the current climate matching outputs (see future & present - data overlays) contain all species with at least 1 record in the belgian climate zones (Cfa, Cfb & Dfb). A single/low number of record(s) can be an error, fluke, etc.... and can best be excluded from the list.
But a what number do we place the threshold ?
The text was updated successfully, but these errors were encountered: