Kyle Barron
Kyle Barron
Perhaps we should have a `wrap_array` method both on each extension type, so that `PointType::wrap_array` returns a `PointArray`. But then also implement that on `GeoArrowType` which returns an `Arc`.
Add readme:
The core crates that are imminently about to be released (`geoarrow-array`, `geoarrow-cast`, `geoarrow-schema`) are all fully documented now.
I don't think it would be particularly complex; the Rust side would be just a for loop. The only slightly complex part would be designing the right user-facing API. Presumably...
@lm93547 It looks like you care more about geoparquet-wasm instead? That's not distributed by this repo, that's in https://github.com/geoarrow/geoarrow-rs
> I think this also means that for several years, we will have to recommend _not_ to use this new feature for wide compatibility of your geoparquet files For what...
If you compile with `--debug` flag turned on, then you can see the actual Rust error, instead of just `RuntimeError: unreachable`. With the test in https://github.com/kylebarron/parquet-wasm/pull/607, the error is: ```...
I checked with @jorisvandenbossche and saw that the IPC spec doesn't _require_ a name to be set, so this is an issue on the Rust side. (Though there _should_ be...
Created https://github.com/apache/arrow-rs/issues/6415. Otherwise, you can work around this by manually setting a field name for any inner lists.
This was fixed in https://github.com/apache/arrow-rs/pull/8557, so the next release containing the next release of `parquet` will solve this.