GeoBridge

GeoParquet 2.0 正式发布:原生几何类型成为核心

GIS 前沿5 阅读原文发布 2026/11/5编译收录 2026/11/5

近日,GeoParquet 2.0 正式发布,该版本将规范与 Parquet 2.11 中引入的原生 GEOMETRY 和 GEOGRAPHY 类型对齐,标志着地理空间数据存储向标准化迈出重要一步。 根据发布说明,GeoParquet 2.0 将规范重新聚焦于 Parquet 地理空间逻辑类型,这些类型已于 2025 年 3 月成为 Parquet 核心格式的一部分。与 GeoParquet 1.x 在普通二进制列上叠加地理空间元数据的做法不同,2.0 版本将原生 Parquet GEOMETRY 和 GEOGRAPHY 类型作为基础:几何列由格式本身进行类型化,坐标参考系统(CRS)随列存储,并且按行组的地理空间统计信息使得无需额外列即可实现高效的空间过滤。 对于兼容 GeoParquet 2.0 的读取器,现在必须能够处理完全不包含 GeoParquet 元数据的 Parquet 文件。但 GeoParquet 仍然填补了原生 Parquet 规范在地理空间用例中留下的一些空白。 GeoParquet 地理元数据得以保留,以确保工具兼容性,并提供了一些 Parquet 核心之外的小功能,包括保证内联的 CRS 定义、多边形环绕顺序、epoch 和主几何列。 更详细地说,GeoParquet 提供了以下内容: - 内联 CRS 定义:确保坐标参考系统信息始终可用,无需外部依赖。 - 多边形环绕顺序:明确多边形顶点的环绕方向,避免歧义。 - epoch:记录时间基准信息,支持时间序列数据。 - 主几何列:标识数据集中的主要几何列,便于工具处理。 来自 1.1 规范的其他 GeoParquet 元数据字段并未消失。在大多数 GeoParquet 工具跟上 2.0 之前,它们仍可用于向后兼容。 GeoParquet 2.0 的发布是地理空间数据社区与 Parquet 社区合作的成果,旨在为地理空间数据提供更高效、更标准的存储格式。随着越来越多的工具支持 2.0,用户将能够享受到更快的查询速度和更简洁的数据管理。 欲了解完整技术细节和迁移指南,请点击原文链接查看。

编译自 Lat Long Blog,原文链接

原文摘要

GeoParquet 2.0 Moves to Parquet’s Native Geometry Types

Link: github.com Just released, GeoParquet 2.0 aligns the specification with native GEOMETRY and GEOGRAPHY types introduced to Parquet 2.11 in March last year. From the release notes: GeoParquet 2.0 re-centers the specification on the Parquet Geospatial Logical Types that became part of the core Parquet format in version 2.11 (March 2025). Where GeoParquet 1.x layered geospatial metadata on top of plain binary columns, 2.0 makes the native Parquet GEOMETRY and GEOGRAPHY types the foundation: the geometry column is typed by the format itself, the CRS travels on the column, and per–row-group geospatial statistics enable efficient spatial filtering with no extra columns. Geoparquet 2.0-compliant readers must now handle Parquet files with no GeoParquet metadata at all. But GeoParquet still fills some gaps the native Parquet specification leaves for geospatial use cases. The GeoParquet geo metadata remains for tool compatibility, and it provides some small things beyond what the Parquet core does, including a guaranteed inline CRS definition, polygon winding order, epoch and the primary geometry column. In more detail, what you get from GeoParquet: A guaranteed inline CRS. Parquet’s crs property can be either inline PROJJSON or a reference to an SRID, in which case the Parquet reader has to resolve the reference. GeoParquet guarantees a full PROJJSON definition in the file itself. Polygon winding order, meaning whether the outer polygon ring runs clockwise or counter-clockwise. Some software depends on this, and native Parquet has no way to specify winding order. Epoch. For dynamic coordinate systems, where coordinates drift as tectonic plates move, this records which point in time the coordinates belong to. Primary geometry column. When a table has several geometry columns, this says which one is the default, as with a “main” geometry in GIS software. Other GeoParquet metadata fields from the 1.1 specification aren’t going away. They can still be used for backwards c