importing raster after October 2023

[francisvolh]

Hi there! awesome package! thanks for the work!

I am not sure this should be an issue, but I tried checking a bit previous issue reports and found nothing.

I am migrating a huge set of scripts into terra and sf, and some of this code uses exact_extract().

I noticed (or at least I think so) it imports the raster package, and wondered if this will be an issue once they do the full migration and remove some other packages from CRAN in October. I know you only use raster for the examples (or again, I think so).

just throwing it out there! thanks for any input you may have!

@francisvolh

[dbaston]

I removed rgdal from Suggests: in the 0.10.0 release: 02dae55

I'm not aware of any issues with importing the raster package, and loading the current CRAN version of exactexractr produces no warnings. Is there a problem you're experiencing?

[francisvolh]

Hi @dbaston ! you are right! I think the issue is with sp, not raster.

I just run this test with Rstudio by writing only in the script the package and a function (it may be just Rstudio the one causing the specific warning, and not really an issue in itself, I suppose). Just by opening this script with those two lines, triggers the warning. But not really when loading the library.

I guess if the sp package is remaining now (from what I read in the r-spatial evolution site) this is not a problem for you to worry about. Thanks and sorry for the trouble!

@francisvolh