Open SanderDevisscher opened 3 years ago
@SanderDevisscher yes, would be so nice, we could use that workflow for future matching exercises and PRA's. Perhaps one functionality to add is the production of one or a few maps (for current/future climate):
Deadline for the pra is 20 May, but never mind if you have little time to stick to it, this is an 'extra' to the pra. If it works, we could run it for more species subject to PRA and see if the outcome corroborates the conclusions of the species distributions models.
This workflow, as well as the one for the RIPARIAS climate matching, would be good to consolidate as a package/function, the same way it is done for TrIAS. I think there is great scope for it to be used worldwide by the invasion community, for example for horizon scanning, drafting alert lists, risk assessment etc.
Therefore: could you include Damiano in the discussion/revision of code and turning it into a package/function?
@damianooldoni I'll write a function for climate matching. You can later integrate the code into the RIPARIAS - package.
ok for you ?.
If needed (see #21), yes.
this function is best integrated in the TrIAS package, so moved here
@timadriaens I close this issue since the function has been written for the Trias package see #77
After integration into the Trias package (allmost) @timadriaens still needs the cm for Pycnonotus jocosus (2486151) & Pycnonotus cafer (2486131)
20_cm_bul_bul
- branch
for these records: [Uploading Pycnonotus_jocosus_records.zip…]()
@timadriaens I think this is best suited to be made into a function with these functionalities:
and with this as output:
what do you think ?
also whats the deadline ?