-
Notifications
You must be signed in to change notification settings - Fork 299
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
Can't write GDBs using OpenFileGDB driver #2134
Comments
Please look at |
Yep, you're right. The installation of OSGeo and GDAL were done automatically when I just ran |
Which platform/operating system, and how did you install |
I'm currently working on a PC with Windows 10. I installed |
Which version of |
The version of |
I can check R 4.3 for Windows 10 tomorrow, Rtools42 have the GDAL version you already have. |
I'm running the R-4.3.0 alpha build (available at https://cran.r-project.org/bin/windows/base/rtest.html), and can confirm that as long as you're running the 4.3.0 build of sf, your reproducible example runs without any problem. Don't forget, after installing R-4.3.0, that you'll need to do this or something equivalent to get the newer build: remove.packages("sf")
install.packages("sf") ETA, here are the versions of the external geospatial software being used: library(sf)
sf::sf_extSoftVersion()
## GEOS GDAL proj.4 GDAL_with_GEOS USE_PROJ_H
## "3.11.1" "3.6.2" "9.1.1" "true" "true"
## PROJ
## "9.1.1" |
On Windows, the user library is usually versioned, so that 4.2 and 4.3 can co-exist. So in 4.3, |
For me, Windows 10, R 4.3-devel (mid-March):
reporting write TRUE.
|
Thanks! |
Awesome, thanks for all the info! =) |
Hi all, I want to set a minimum version of {sf} to be based on when the |
I think it is only controlled by the GDAL version. From https://gdal.org/en/latest/drivers/vector/openfilegdb.html, GDAL 3.6 is needed for writing fgdb. For CRAN binaries, Windows is now at 3.9.3 I think, but macOS is on 3.5. A small example file to test, say in a github actions run, might make sense. |
For writing both vectors and rasters, using the driver argument controls. For reading, the detection of the needed driver should be done by GDAL. The extension map is very likely superfluous, never needed in |
Around mid 2022, the
GDAL
library was updated and theOpenFileGDB
was enhanced to include the capacity to write GDBs (see here).I think some other changes need to be made to
sf
to allow its users to access those capabilities. Right now, when I try to wright a GDB usingsf
, i get an error:The
st_write
command above yields the following error message:Is there any way I can bypass this? Thanks!
The text was updated successfully, but these errors were encountered: