Skip to content

Commit f30b801

Browse files
Optional column metadata field to store bounding box information (#21)
Co-authored-by: Brendan Ward <[email protected]>
1 parent d8241a4 commit f30b801

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

format-specs/geoparquet.md

+11
Original file line numberDiff line numberDiff line change
@@ -52,6 +52,7 @@ Each geometry column in the dataset must be included in the columns field above
5252
| ---------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
5353
| crs | string | **REQUIRED** [WKT2](http://docs.opengeospatial.org/is/12-063r5/12-063r5.html) string representing the Coordinate Reference System (CRS) of the geometry. |
5454
| encoding | string | **REQUIRED** Name of the geometry encoding format. Currently only 'WKB' is supported. |
55+
| bbox | \[number] | **OPTIONAL** Bounding Box of the geometries in the file, formatted according to [RFC 7946, section 5](https://tools.ietf.org/html/rfc7946#section-5) |
5556

5657
#### crs
5758

@@ -78,6 +79,16 @@ This is the binary format that the geometry is encoded in. The string 'WKB' to r
7879
[Well Known Binary](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry#Well-known_binary) is the only current option, but future versions
7980
of the spec may support alternative encodings. This should be the ["standard"](https://libgeos.org/specifications/wkb/#standard-wkb) WKB representation.
8081

82+
#### bbox
83+
84+
Bounding boxes are used to help define the spatial extent of each geometry column.
85+
Implementations of this schema may choose to use those bounding boxes to filter
86+
partitions (files) of a partitioned dataset.
87+
88+
The bbox, if specified, must be encoded with an array containing the minimum
89+
and maximum values of each dimension: `[<xmin>, <ymin>, <xmax>, <ymax>]`.
90+
This follows the GeoJSON specification ([RFC 7946, section 5](https://tools.ietf.org/html/rfc7946#section-5)).
91+
8192
### Additional information
8293

8394
## TODO

0 commit comments

Comments
 (0)