Kyle Barron

How should nullability be handled here? For `geoarrow.geometrycollection`, should we disallow any null items in the children of the union array?

It would also be great to get feedback from cuSpatial developers, especially as this PR closes #23. cc @thomcom @trxcllnt. How similar is this to your existing data structures? I...

One comment came up in https://github.com/geoarrow/geoarrow-rs/pull/646#issuecomment-2139145702. In _practice_, should the Geometry array include _all_ possible child arrays or just the child arrays that have data? E.g. if you have points...

Is it true that if the _types_ all have the same child ids, then the physical array layouts need to exist for all union children as well? I.e. I assume...

> I think that having this type description as you have it here is good (i.e., it's "just" a union), with the convention that you either return `union` OR `list>`...

Latest changes: - Require all children arrays to have same dimensionality. - Disallow nested geometry collections. That is, not permit a `Geometry` array to contain `GeometryCollections`. I think it's easier...

> you must always include all six children of a GEOMETRY type You're only suggesting the six children with the same dimension, not children across multiple dimensions? With the Rust...

> But we could also define GeometryCollection as `List`, and then this is also never a nested collection, without the restriction on `Geometry` to not contain collections. This still has...

> Like I said, given how much work this is, it feels mostly academic at this point. What do you think is the right path forward here? For my own...

Thanks! This is really insightful background. > So, if you have a better suggestion, go ahead and change it. I'd encourage anything other than `BINARY` which gives zero information on...