FlatGeobuf is a new geospatial data format that allows users to work more efficiently with vector data. It can be used as a replacement for GeoJSON, providing smaller file sizes and faster loads. It is a binary (FlatBuffers-encoded) format that defines geospatial geometries. It is row-oriented rather than columnar like GeoParquet and GeoArrow and offers a different set of trade-offs.
FlatGeobuf was inspired by geobuf and flatbush.
- Row oriented
- Supports appends, but not random writes
- Optionally supports a spatial index
Goals are to be suitable for large volumes of static data, significantly faster than legacy formats without size limitations for contents or meta information and to be suitable for streaming/random access.
FlatGeobuf supports any vector geometry type defined in the OGC Simple Features specification (the same feature types supported by the WKB 2D geometry type enumeration).
GeoBuf geometries include the standard building blocks of
GeometryCollection, but also includes more infrequently types such as
Surface, and `TIN`` (Triangulated irregular network). These additional types are not supported by Studio.
Note: Storing only geometries with the same type allows readers to know which geometry type is stored without scanning the entire file.
Apart from geometry, FlatGeobuf supports columns with a range of types:
|Signed 8-bit integer
|Unsigned 8-bit integer
|Signed 16-bit integer
|Unsigned 16-bit integer
|Signed 32-bit integer
|Unsigned 32-bit integer
|Signed 64-bit integer
|Unsigned 64-bit integer
|Single precision floating point number
|Double precision floating point number
|General JSON type intended to be application specific
|ISO 8601 date time
|General binary type intended to be application specific
Studio does not yet use the spatial index in flatgeobuf files.
Updated about 1 month ago