Kyle Barron

> > It looks like pyarrow doesn't implement **arrow_c_stream** for a ChunkedArray? > > It definitely should! Opening an issue would be helpful (I can take a stab at implementing)....

> longer term it might be interesting to think about whether shapely could directly support the C Data Interface That would be really cool, especially if it could vendor nanoarrow...

> It seems like the some things I should prioritize here are implementing the stream protocol for ChunkedArrays and implement the protocol in objects returned by geoarrow.c? I'd agree with...

With https://github.com/geoarrow/geoarrow-rs/pull/293 I now have a working prototype (of an `area` method) based on the pycapsule interface. I haven't tested it yet on a pyarrow extension array, but it worked...

Oh, I should've known this bug was from that. We should really push that spec PR over the line

> so there are also pyarrow extension type and array definitions in the `geoarrow-pyarrow` package yeah I didn't know those existed when I wrote these 🙈 > I assume we...

Thinking about it again, I think the biggest problem with the approach in this PR is that the returned object from the submodule is not necessarily the same class as...

Yeah, I agree it's early and there are a lot of unknowns. The reason I reach for an object oriented approach is that not all operations are implemented on every...

FWIW I believe a GEOS prepared geometry indexes _every coordinate pair_ (`Line` in geo terminology). This is vastly different than indexing each polygon, especially for large polygons like country/land boundaries....