-
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
st_write support GeoParquet #2506
Comments
Please report your operating system and how you installed |
It seems the driver name is sf::st_drivers() |>
dplyr::filter(name == "Parquet")
#> name long_name write copy is_raster is_vector vsi
#> Parquet Parquet (Geo)Parquet TRUE FALSE FALSE TRUE TRUE |
Just in case this is useful, I found no Parquet driver on my Windows. It seems Rtools' GDAL (v3.10.1 at the latest) doesn't have support for GeoParquet. |
@yutannihilation the OS and how sf and GDAL were installed also matter apart from spelling. |
Sorry, I added these information on my first comment! It was the result on my Manjaro Linux laptop. |
@yutannihilation Thanks for your help! As far as I know, the CRAN Windows and macOS static binary builds omit the GDAL vector "Parquet" and "Arrow" drivers. Different Linux package management systems may choose to include or exclude the upstream software needed to include these drivers. |
Oh, good to know the situation about Windows and macOS. Thanks for sharing the details! |
Present on both Windows 10 and Windows server 2016. Installed via install.packages. |
@arthurgailes The current |
Here was similar thread in |
@kadyb thanks, very useful! |
With my ubuntu 24.04 and ubuntugis-unstable ppa I couldn't read geoparquet files, but in a docker image with this Dockerfile I could. |
This seems to work quickly following the example at https://github.com/geoarrow/geoarrow-r if googlers are looking for a workaround |
As of 1.0-19, writing (geo)parquet files doesn't seem to work. It's supported in GDAL, but not included in st_drivers(). This issue is mentioned in an old thread #1756, but I'm not sure what the status is.
Thanks for your time.
The text was updated successfully, but these errors were encountered: