EwoutH commented on issue #1884: URL: https://github.com/apache/iceberg-rust/issues/1884#issuecomment-4132318101
Some context on the upstream dependencies for this, since the picture has improved significantly since this issue was opened: **arrow-rs** (the Parquet layer iceberg-rust depends on) [completed GEOMETRY/GEOGRAPHY support](https://github.com/apache/arrow-rs/issues/8373) in January 2026. This means the foundational read/write path for geospatial Parquet types is already available — iceberg-rust doesn’t need to implement Parquet-level geo type handling from scratch. For the Iceberg-level work, the main pieces would be: 1. **Type system** — Add `Geometry` and `Geography` to iceberg-rust’s `PrimitiveType` enum, with CRS metadata. The [Iceberg spec](https://iceberg.apache.org/spec/) defines these as v3 types that default to null with no initial/write default. 1. **Schema serialization** — Handle JSON serialization/deserialization of the new types in table metadata. 1. **Arrow type mapping** — Map Iceberg geometry/geography to Arrow’s `geoarrow.wkb` extension type (which arrow-rs now supports via `parquet-geospatial`). 1. **Manifest statistics** — Support bounding box upper/lower bounds for geometry columns, as [defined in the spec](https://iceberg.apache.org/spec/#appendix-e-field-id-to-field-name-mapping). The reference Java implementation has been landing in stages — [#12667](https://github.com/apache/iceberg/pull/12667) (geospatial bounding box types + intersects checking) merged in November 2025, with follow-up PRs for spatial predicates ([#14101](https://github.com/apache/iceberg/pull/14101)) and metrics evaluator integration ([#14102](https://github.com/apache/iceberg/pull/14102)). iceberg-go also has a [WIP PR](https://github.com/apache/iceberg-go/pull/663). Both could serve as references. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
