Format Atlas

Data

FlatGeobuf: feature collections and optional spatial indexing

FlatGeobuf is a binary geographic feature format based on FlatBuffers. It contains a header, an optional spatial index and feature data. A .fgb file holds a single layer.

.fgbBinary feature collections

When to choose this format

  • Read features within a bounding area in compatible tools

When to avoid this format

  • A database for frequent SQL updates to individual records

Common uses

  • Distribute a static feature layer

Features

  • The header can describe attribute columns, geometry type and CRS

Advantages and disadvantages

Advantages

  • A spatial index can support bounding-box searches when present

Disadvantages

  • The format is not designed for random writes

Open and convert

How to open

Use compatible GIS to check layer, CRS, attribute types and index presence. Partial HTTP reads need Range support and suitable hosting. Keep buffer verification enabled for unknown data.

How to convert

After conversion to GeoPackage, check counts, CRS, coordinates, Z/M and attribute types. Split multiple layers into separate .fgb files. GeoPackage tiles and extensions do not all map into a feature file.

Cautions

  • GDAL restricts NULL geometries in indexed output. Check settings and implementation version, and review location sharing scope. Binary encoding does not imply encryption or compression.

FAQ

Does every FlatGeobuf file have a spatial index?

No. The index is optional. Search efficiency depends on indexing, implementation, data and delivery conditions; test actual datasets.

Related formats

Compare

Related uses and checks

Checks before handing off GIS data

References and specifications