Hello everyone, I am working big geospatial and trying to solve very large tables in object storage. Iceberg appear to be the ideal solution but does unfortunately not appear to support geometry columns.
The way that iceberg is structured, it appears to be a good fit with the GeoParquet-standard (https://github.com/opengeospatial/geoparquet/blob/main/format-specs/geoparquet.md), so I created a pull request where I attempt to add this support: https://github.com/apache/iceberg/pull/6062 The PR deviates from GeoParquet in the CRS-field of the column metadata. GeoParquet requires the CRS to be defined as a PROJJSON JSON object, while the PR simply asks the user to specify and EPSG ID, where EPSG:4326 (WGS84 - latitude/longitude) is considered default. I would love feedback on the PR and welcome the discussion on whether geospatial/geometry belongs in the iceberg standard. Thomas Li Fredriksen Lead Solution Architect p +47 452 21 055 [cid:864ecf94-2d7d-419d-ab01-ae6ed9e6a485] ––––– www.hubocean.earth<http://www.hubocean.earth>
