Kyle Barron

GEOS only has a point, right? I don't think it has a coordinate concept, and they get by fine

> One way to make the change a little more piece-meal could be to unify the coords/point accessors - to wit, getting rid of the public field accessors on Coord,...

To clarify I assume you're referring to the native encodings, not the serialized WKB encoding, which is just a binary column?

In case it's useful, I implemented the pycapsule interface for polars in https://github.com/pola-rs/polars/pull/17676 and https://github.com/pola-rs/polars/pull/17693. I figure polars-arrow hasn't diverged too much from arrow2, so it should be pretty similar...

I hope you don't mind I'm incorporating this PR into my alternative binding: https://github.com/developmentseed/object-store-rs/pull/11

Right... I'm kinda lost at what's happening. It looks like the core error is ``` = note: wasm-ld: error: /Users/kyle/github/geoarrow/geoarrow-rs/python/core/emsdk/upstream/emscripten/cache/sysroot/lib/wasm32-emscripten/libstandalonewasm.a(__main_void.o): undefined symbol: main ``` but I can't see what's causing...

I don't know... FWIW this isn't high priority to me right now, but I'd never seen this error before, so I figured I might as well log it 🤷‍♂️

Another GeoParquet member checking in: My main question/concern about this is the degree to which it forces generic Parquet implementations to be aware of and care about geospatial data types....

If this feature is for in-memory processing, not a file format, and if databend is otherwise using Arrow, then I would strongly recommend you incorporate [GeoArrow](https://geoarrow.org/), and not create your...

> but @kylebarron I'm pretty sure doesn't agree with me! I'd generally prefer having only one coordinate representation. But it's hard because some pieces of the ecosystem might only support...