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
Apparently, the R spatial world is shifting away from rgdal, rgeos, and maptools toward sf and terra. rgdal, rgeos, and maptools all scheduled for retirement at the end of 2023. Thanks for the heads up @infotroph
raster doesnt yet have a retirement date, but its suggested to move toward terra
Proposed Solution
So to me this means right now is a great time to overhaul our spatial dependencies. First start with simpler functions toward sf/terra (e.g. in data.remote) but we need to develop a list of all functions that use these tools and then schedule the order for updating.
Alternatives Considered
none
Additional Context
[](https://twitter.com/@RogerBivand)[Roger Bivand](https://twitter.com/@RogerBivand)Roger Bivand [@RogerBivand](https://twitter.com/@RogerBivand)
[@edzerpebesma](https://twitter.com/edzerpebesma) I'm not sure that taking over maintenance is a sensible use of effort (add maptools to that list). The main condition for this will be transition from raster to terra, as raster uses rgdal heavily. If sf/stars and terra become the main workflow bases, things get simplified.
TwitterTwitter | [Jun 23rd, 2021](https://mobile.twitter.com/RogerBivand/status/1407705212538822656)
Some other issues - if we need to buffer points to average pixels when extracting does terra support that like raster?
The text was updated successfully, but these errors were encountered:
Description
Apparently, the R spatial world is shifting away from rgdal, rgeos, and maptools toward sf and terra. rgdal, rgeos, and maptools all scheduled for retirement at the end of 2023. Thanks for the heads up @infotroph
https://mobile.twitter.com/RogerBivand/status/1407705212538822656
https://cran.r-project.org/web/packages/rgdal/index.html
raster doesnt yet have a retirement date, but its suggested to move toward terra
Proposed Solution
So to me this means right now is a great time to overhaul our spatial dependencies. First start with simpler functions toward sf/terra (e.g. in data.remote) but we need to develop a list of all functions that use these tools and then schedule the order for updating.
Alternatives Considered
none
Additional Context
Some other issues - if we need to buffer points to average pixels when extracting does terra support that like raster?
The text was updated successfully, but these errors were encountered: