[R]: Export wk reader & writer S3 methods?

[anthonynorth]

Could we export wk_handle.geoarrow_array and wk_writer.geoarrow_array S3 methods? This will allow for integration with {wk} readers, writers and filters.

Geoarrow arrays don't currently have their own class. I'm assuming this is planned?

I think this is all we need (once the geoarrow_array class exists)

wk_handle.geoarrow_array <- function(handleable, handler, size = NA_integer_, ...) {
  handler <- wk::as_wk_handler(handler)
  geoarrow::geoarrow_handle(handleable, handler, size)
}

wk_writer.geoarrow_array <- function(handleable, schema = NULL) {
  # what is an apppropriate default?
  if (is.null(schema)) {
    schema <- geoarrow::infer_geoarrow_schema(handleable)
  }
  geoarrow::geoarrow_writer(schema)
}

wk::wk_count(my_geoarrow_array)

[paleolimbot]

Good spot! I haven't had time to circle back to this recently...the main blocker was the geoarrow_array class, as you noted. I'd been planning to call it geoarrow_vctr and have it be basically the same as the geoarrow_vctr here: https://github.com/paleolimbot/geoarrow/blob/master/R/vctr.R .

[anthonynorth]

Is the intent to bring across the geoarrow_vctr as-is + necessary fixes?

Does this package completely replace paleolimbot/geoarrow?

[paleolimbot]

Does this package completely replace paleolimbot/geoarrow?

Yes! I also need to port over read_geoparquet() and read_geoparquet_sf() as well as the Arrow C++ extension type stuff. The code in paleolimbot/geoarrow was based on an early attempt at what is now nanoarrow and geoarrow-c, which have much better support.

Is the intent to bring across the geoarrow_vctr as-is + necessary fixes?

Yes, although I was planning to have it be as minimal as possible and perhaps more aggressively materialize (maybe via arrow for now) when doing anything other than slicing. The minimal useful implementation doesn't really need subsetting at all...just something to exist that somebody can call sf::st_as_sfc() (or geos::as_geos_geometry(), etc.).

[anthonynorth]

Ok. I'll follow up on the geoarrow_vctr discussion with a separate issue.