-
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
rewrite code avoiding using sp and rworldmap #110
Comments
I'll look into it |
@soriadelva will look into this under my supervision. |
Thanks for the update. I have added her just now to trias as member. |
@damianooldoni, the RDA data files currently provide the climate data as SpatialPolygonsDataFrame and Sander and me were wondering if it could be useful to recode them as sf objects? |
👋 @soriadelva! > class(observed)
[1] "list"
> names(observed)
[1] "1901-1925" "1926-1950" "1951-1975" "1976-2000" "1980-2016"
> class(future)
[1] "list"
> names(future)
[1] "2001-2025-A1FI" "2026-2050-A1FI" "2051-2075-A1FI" "2076-2100-A1FI" "2071-2100_Beck"
> class(legends)
[1] "list"
> names(legends)
[1] "KG_A1FI" "KG_Beck" So, saving them as geojson would mean we will have 10 geojson file (5 from It will make everything quite complex for everybody, I think. I would just convert
and then overwriting the .rda files. |
@damianooldoni thanks for the reply! I'll convert them to two lists of sf. |
#110 Function converted to work on sf package instead of sp package. World maps imported via package rnaturalworld instead of rworldwap. Possible issue: this package may consider continents a little differently (e.g., Greenland is not a part of Europe while in rworldmap it was considered a part of Europe)
@SanderDevisscher: the climate function is using sp package. rworldmap is also used, which relies on sp.
It's time to move to sf. In this way we don't need to use packages rgeos and rgdal which are archived since October 2023 and not more available. See failures of GitHub actions. This is not only important for the authomatic checks of this package, but as you are authomatising the indicators workflow, using the trias package in your GitHub Actions will fail.
The text was updated successfully, but these errors were encountered: