The Apache Parquet provides a standardized open-source columnar storage format. This specification defines how geospatial data should be stored in parquet format, including the representation of geometries and the required additional metadata.
This is version 0.1.0 of the geoparquet specification.
Geometry columns are stored using the BYTE_ARRAY
parquet type. They are encoded as WKB.
See the encoding section below for more details.
geoparquet files include additional metadata at two levels:
- File metadata indicating things like the version of this specification used
- Column metadata with additional metadata for each geometry column
These are both stored under a "geo" key in the parquet metadata (the FileMetaData::key_value_metadata
) as a JSON-encoded UTF-8 string.
All file-level metadata should be included under the "geo" key in the parquet metadata.
Field Name | Type | Description |
---|---|---|
version | string | REQUIRED The version of the geoparquet metadata standard used when writing. |
primary_column | string | REQUIRED The name of the "primary" geometry column. |
columns | Map<key, Colum Metadata> | REQUIRED Metadata about geometry columns, with each key is the name of a geometry column in the table. |
At this level, additional implementation-specific fields (e.g. library name) are allowed, and thus readers should be robust in ignoring those.
This indicates the "primary" or "active" geometry for systems that can store multiple geometries, but have a default geometry used for geospatial operations.
Version of the geoparquet spec used, currently 0.1.0
Each geometry column in the dataset must be included in the columns field above with the following content, keyed by the column name:
Field Name | Type | Description |
---|---|---|
crs | string | REQUIRED WKT2 string representing the Coordinate Reference System (CRS) of the geometry. |
encoding | string | REQUIRED Name of the geometry encoding format. Currently only 'WKB' is supported. |
edges | string | OPTIONAL Name of the coordinate system for the edges. Must be one of 'planar' or 'spherical'. The default value is 'planar'. |
bbox | [number] | OPTIONAL Bounding Box of the geometries in the file, formatted according to RFC 7946, section 5 |
The Coordinate Reference System (CRS) is a mandatory parameter for each geometry column defined in geoparquet format.
The CRS must be provided in WKT version 2, also known as WKT2. WKT2 has several revisions, this specification only supports WKT2_2019.
For the widest interoperability we recommend EPSG:4326 for all data, as it is the most widely used coordinate reference system today, so unless data is stored in an alternate projection the CRS should be:
GEOGCRS["WGS 84",
ENSEMBLE["World Geodetic System 1984 ensemble",
MEMBER["World Geodetic System 1984 (Transit)"],
MEMBER["World Geodetic System 1984 (G730)"],
MEMBER["World Geodetic System 1984 (G873)"],
MEMBER["World Geodetic System 1984 (G1150)"],
MEMBER["World Geodetic System 1984 (G1674)"],
MEMBER["World Geodetic System 1984 (G1762)"],
MEMBER["World Geodetic System 1984 (G2139)"],
ELLIPSOID["WGS 84",6378137,298.257223563],
ENSEMBLEACCURACY[2.0]],
CS[ellipsoidal,2],
AXIS["geodetic latitude (Lat)",north],
AXIS["geodetic longitude (Lon)",east],
UNIT["degree",0.0174532925199433],
USAGE[
SCOPE["Horizontal component of 3D system."],
AREA["World."],
BBOX[-90,-180,90,180]],
ID["EPSG",4326]]
Due to the large number of CRSes available and the difficulty of implementing all of them, we expect that a number of implementations will at least start with only supporting a single CRS. To maximize interoperability we strongly recommend GeoParquet tool providers to always implement support for EPSG:4326. Users are recommended to store their data in EPSG:4326 for it to work with the widest number of tools. But data that is better served in particular projections can choose to use an alternate coordinate reference system. We expect many tools will support alternate CRSes, but encourage users to check.
This is the binary format that the geometry is encoded in. The string 'WKB', signifying Well Known Binary is the only current option, but future versions of the spec may support alternative encodings. This should be the "ISO" WKB representation. For two-dimensional geometries, this is identical to "standard" WKB, but ISO WKB allows the use of 3D geometries.
Note that the current version of the spec only allows for a subset of ISO WKB: 2D or 3D geometries of the standard geometry types (the Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon, and GeometryCollection geometry types). This means that M values or non-linear geometry types are not yet supported.
The axis order of the coordinates in WKB stored in a geoparquet follows the de facto standard for axis order in WKB and is therefore always (x, y) where x is easting or longitude and y is northing or latitude. This ordering explicitly overrides the axis order as specified in the CRS. This follows the precedent of GeoPackage, see the note in their spec.
This attribute indicates how to interpret the edges of the geometries: whether the line between two points is a straight cartesian line or the shortest line on the sphere (geodesic line). Available values are:
- planar: use a flat cartesian coordinate system.
- spherical: use a spherical coordinate system and radius derived from the spheroid defined by the coordinate reference system.
If no value is set, the default value to assume is 'planar'.
Bounding boxes are used to help define the spatial extent of each geometry column. Implementations of this schema may choose to use those bounding boxes to filter partitions (files) of a partitioned dataset.
The bbox, if specified, must be encoded with an array containing the minimum
and maximum values of each dimension: [<xmin>, <ymin>, <xmax>, <ymax>]
.
This follows the GeoJSON specification (RFC 7946, section 5).
You can find an example in the examples folder.