You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have pre-selected 5 species for PRA based on initial data availability and trends in occurrences (when we’ll face additional bottlenecks regarding data availability or expert identification we might reduce this number during the coming weeks, tbc):
Crepidula fornicata (gastropod)
Mnemiopsis leidyi (Ctenophora)
Ensis leei (bivalve)
Hemigrapsus takanoi (Crustacea)
Magalana (Crassostrea) gigas (bivalve)
@damianooldoni: would it be possible to create a GAM for C. fornicata & M. Leidyi? Thanks in advance!
The text was updated successfully, but these errors were encountered:
emerging status via decision rules (no enough data for GAM). Ranking via hierarchical strategy: 68th place. Ranking via point strategy: 187th place. All indicators classify it as emerging in 2018 and as unclear in 2017. In 2016 from unclear to emerging depending on the indicator.
Via GAM: occupancy in BE and observations in BE both NOT emerging. Not enough data for applying GAM on observation and occupancy in Natura2000 area. Decision rules applied. Both observations and occupancy: potentially emerging in 2018 and 2016, unclear in 2017. So, very low ranking with both ranking strategies.
To do: improve GAM plots (as we correct at class level, the GAM curve doesn' necesarily follows the real points, so we have to make different subplots. See #72) and rerun with updated occurrence cube, although dramatic changes should not occur.
From e-mail of Thomas Verleye:
We have pre-selected 5 species for PRA based on initial data availability and trends in occurrences (when we’ll face additional bottlenecks regarding data availability or expert identification we might reduce this number during the coming weeks, tbc):
@damianooldoni: would it be possible to create a GAM for C. fornicata & M. Leidyi? Thanks in advance!
The text was updated successfully, but these errors were encountered: