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
In Ubuntu / Linux Mint, but not on Windows and macOS systems, there's an odd effect of having called raster::raster() in an R session before writing a GeoPackage with terra::writeVector(). GDAL raises an ENCODING warning in that specific scenario. See reprexes below.
I don't know whether the solution is here or in the raster package; posting it in terra is a wild guess...
>terra::gdal()
[1] "3.6.4"
# Normally no warning appears when writing a GeoPackagetmp1<- tempfile(fileext=".gpkg")
obj<-terra::vect(
x= c("POINT (7e5 7e5)", "POINT (6e5 6.5e5)"),
crs="EPSG:3812"
)
terra::writeVector(obj, tmp1)
unlink(tmp1)
Adding some context. This was discovered in a GitHub Actions R-CMD-check workflow of {qgisprocess} after having added unit tests with terra::SpatVector() to the test file that tests the handling of {terra} objects. Only the Ubuntu jobs were affected. It was observed locally that the many warnings disappear after the test file for handling {raster} objects is removed. That file is run before the {terra} test file because of alphabetical order.
In Ubuntu / Linux Mint, but not on Windows and macOS systems, there's an odd effect of having called
raster::raster()
in an R session before writing a GeoPackage withterra::writeVector()
. GDAL raises an ENCODING warning in that specific scenario. See reprexes below.I don't know whether the solution is here or in the raster package; posting it in terra is a wild guess...
Created on 2023-12-19 with reprex v2.0.2
Session info
Created on 2023-12-19 with reprex v2.0.2
Created on 2023-12-19 with reprex v2.0.2
Session info
The text was updated successfully, but these errors were encountered: