Closed tim-salabim closed 2 years ago
In the light of the propsed retirement of rgdal at the end of 2022(3?), it seems a bit odd to be forced to state it as a Suggests now.
It's probably the easiest, and won't be harmful. Most of the real work lies with raster
, which will have to make itself independent from rgdal
when calling (many of the) functions that use GDAL.
raster now Imports terra, so (as yet untried) using that package might work (but I don't see terra in mapview now).
Just cloned 9009 passes on released and devel r82118 (that is with rgdal in Suggests), with the env. variable given.
raster now Imports terra, so (as yet untried) using that package might work (but I don't see terra in mapview now).
Yeah, providing methods for terra is still on my to-do list. But that wouldn't solve the raster issue as we'd still want to keep the raster methods (as we do for e.g. sp - for now).
Just cloned 9009 passes on released and devel r82118 (that is with rgdal in Suggests), with the env. variable given.
Thanks, it also checks cleanly on win-builder (r-devel) now.
My suspicion is that raster may move towards replacing calls out to rgdal by calls to *'terra** at some point.
Ok, I'll stick with rgdal in suggests for now and wait how raster things pan out. Thanks for all the input!
This is just to confirm that the plan for raster
is to eventually replace functions from rgdal
and rgeos
with equivalent functions from terra
. By making raster
dependent on terra
I have made one big step in that direction. But I am otherwise not in a hurry, because I prefer to work on terra
; and because I am assuming that the "retirement" of rgdal
and rgeos
(or of their maintainer, really) will not immediately break things.
It is likely that retirement will mean archiving the three packages at the latest ultimo 2023. Creating masking sequel packages creates more maintenance, so unless sp methods are involved, especially sp::spTransform()
, the best solution is hard retirement. We'll know more by August this year.
I got the following emails from CRAN team:
and
The resulting error is:
.requireRgdal()
is an unexported function of the raster package.I can reproduce the error with
If I understand the CRAN suggestion correctly, I would either need to declare rgdal as a Suggests in my package (which seems to work - checks cleanly on my local machine) or Depend on raster (not tried). I am assuming that this will affect all packages that are using raster and at least have examples or tests run during
R CMD check
.In the light of the propsed retirement of rgdal at the end of 2022(3?), it seems a bit odd to be forced to state it as a Suggests now.
How do we envision this to be addressed in the long run? @rhijmans @rsbivand @edzer
I have no problem with this rgdal Suggests as a hotfix, but it clearly only is a hotfix...