geoarrow-c
geoarrow-c copied to clipboard
geoarrow
Experimental C and C++ implementation of the GeoArrow specification
Add minimal geoarrow_vctr class for geoarrow vectors. Enables integration with other packages `wk`, `sf`, `geos` etc. See https://github.com/geoarrow/geoarrow-c/issues/69#issuecomment-1778320000
Like the previous geoarrow, we should provide `read_geoparquet()` (which reads to data.frame with geometry as `geoarrow_vctr`) and `read_geoparquet_sf()` (which reads directly to sf). I believe the current geoarrow is set...
Like the previous geoarrow incarnation, we should provide arrow package integration. This allows direct use of things like `arrow::read_parquet()` and the arrow package dplyr integration. I think the implementation will...
There's a good deal of code in Python that would have to be duplicated in R to support inferring the extension name from a storage array. The inference is basically:...
Currently, an attempt to `GeoArrowBuilderInitXXX()` from a WKB or WKT array fails. This leads to awkward code for clients that want to support generic conversion using the visitor pattern (I...
nanoarrow goes to considerable effort to make it very, very easy to copy/paste files into another project and use them as-is. There is nothing inherent about geoarrow-c that would prevent...
Currently all kernels are in the same file in one totally massive mess of function pointers. This is a bad example of how to implement a kernel, which should mostly...
Currently, calling `geobuffers()` on a sliced array will result in buffers that don't necessarily line up with the logical content of the array (i.e., non-zero offsets are not supported). This...
Currently, all offset types are `int32_t` and iterating over `LARGE_WKT` and `LARGE_WKB` is currently not possible. We need to: - Ensure that the `offsets` member of the `GeoArrowArrayView` can handle...