Kyle Barron

> If I understand correctly, some of the async code from `parquet2` did get upstreamed into `parquet`? I'm not sure if it ever got upstreamed or if `parquet` separately implemented...

I've made significant progress at https://github.com/developmentseed/async-tiff, and plan to make an initial release within a week or so. So far, reading all tag data (including geospatial tags) seems to be...

To update you on my/our (@developmentseed's) plan: 1. Stabilize the core functionality from `async-tiff`. 2. Expose Python bindings for `async-tiff`. 3. Write a high level `async-geotiff` wrapper (**in Python**) that...

> how to make some of this generic I would suggest looking at https://github.com/apache/arrow-rs/pull/7015. It enables the new functionality in https://github.com/geoarrow/geoarrow-rs/pull/1040. Right now that PR hides the new encoders out...

> * Allow user to pass in `target_geoarrow_type` Note to self: I'm in favor of having the CSV reader not do any casting and letting the user use `geoarrow_cast` themselves...

This issue is for something else. Arrow supports multiple types to store binary and string data. In particular, it has both the ["traditional" binary/string array](https://arrow.apache.org/docs/format/Columnar.html#variable-size-binary-layout) and the new ["view types"...

> results in a panic `src/vendor/geoarrow/src/array/dynamic.rs:199:9: not yet implemented` I accidentally pushed it directly but I fixed that `todo!()` in https://github.com/geoarrow/geoarrow-rs/commit/b4ecffa3f5f4c56da9554e41444cb1de891379ff. But still, that only fixes the `into_array_ref` panic. `GeometryArray::try_from`...

https://github.com/apache/arrow-rs/pull/6924 and the existing `StringArrayType` may help in making this generic. (And then we could also implement `StringArrayType` for our `WKTArray` and `BinaryArrayType` for our `WKBArray`).

While it's not explicitly called a "WrapArray" trait, there's equivalent functionality in `geoarrow-array` to achieve this. Every geometry array type has several `TryFrom` implementations that convert data from `arrow` arrays...

One downside of the current `from_arrow_array` top-level function is that it always uses `GeoArrowType::from_arrow_field` (interpreting any geometry-like column, loosely) instead of using `GeoArrowType::from_extension_field` (actively requiring GeoArrow extension metadata to be...