Kyle Barron

> GeoPackage stores CRS information as WKT2 I'm not an authority on GeoPackage but it doesn't appear to be that simple. In the [WKT reference in the spec](https://www.geopackage.org/spec131/index.html#extension_crs_wkt), it says...

Moved from https://github.com/geopandas/geo-arrow-spec/pull/2#issuecomment-612558417 I wanted to bring up the non-WKB "ragged" array for discussion again. @jorisvandenbossche wrote [here](https://github.com/pygeos/pygeos/pull/93#issuecomment-593350887): > One big advantage of using that layout (and that's the main...

And just to make sure, that memory model won't change with the future closer integration with `pygeos`, right?

I think my suggestion above is essentially identical to the flatbuffer description with the exception that I store _all_ coordinates together, and leave the interpretation to the user. So instead...

I think you're referring to two different features? There isn't a current WKT option to have both `Linestring` and `Linestring Z` in a single feature, unless you use a `GeometryCollection`,...

Just a quick note that in versions of geoparquet so far WKB is the standard, but in future versions we hope to also enable an Arrow-native geometry encoding, see https://github.com/geopandas/geo-arrow-spec/blob/main/format.md....

A few notes... I've already started planning how to implement `geoparquet` and `geoarrow` and I'd love to discuss each of these so that we can align our work. It might...

It's still worthwhile to have a geoparquet/geoarrow implementation in `geozero`, so I don't want to dissuade you from that. My point is that today the `georust/geo` algorithms all use geo-specific...

> Things like moves into a new-type struct are optimized away That's super interesting. I've never looked into low-level compiled output before. @apps4uco Re-reading my comment I think my tone...

This is interesting; thanks for writing this up. My comments here are generally in comparison with the geometry representation thoughts I wrote [here](https://github.com/geopandas/geo-arrow-spec/issues/3#issuecomment-613101661). ### Nested vs flat lists The biggest...