Convert FGB to PARQUET
Turn FGB files into PARQUET. A GeoParquet file with one row for each feature: its shape as WKB in a geom column that GeoParquet metadata describes with its geometry types, bounding box and coordinate system, then every attribute as a column, with lists and nested values kept as Parquet lists and structs.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop FGB files on the dialor turn it to pick what to do
A GeoParquet file from your FlatGeobuf map data.One row for each feature, with its shape and every attribute kept.
What you get
A single GeoParquet file with one row for each feature in the FGB file. The shape of each feature is stored as WKB in a column named geom.
GeoParquet metadata describes that column with its geometry types, its bounding box and its coordinate system.
What happens to attributes
Every attribute becomes its own column. Lists and nested values are kept as Parquet lists and structs, so they do not get flattened into text.
The coordinate system of the source is kept.
When there is no coordinate system
If the data names no coordinate system, it is taken as WGS 84 when its coordinates fit. When they do not fit, the conversion stops with
unsupported_elements.
FGB and PARQUET.What each format is.
The formats
FlatGeobuf
FlatGeobuf, a compact binary format for map features that streams over the web.
- Extensions
- .fgb
- MIME type
- application
/flatgeobuf - Kind
- Text and data
Parquet
The columnar data format of analytics. Compressed, typed and fast to scan.
- Extensions
- .parquet .pq
- MIME type
- application
/vnd .apache .parquet - Kind
- Text and data
In your code.The same FGB to PARQUET conversion through the API, for your app or your agent.
$ cv convert report.fgb report.parquet$ cv convert report.fgb report.parquetQuestions.What people ask about FGB to PARQUET.
Yes. Every attribute becomes a column, and lists and nested values stay as Parquet lists and structs.
In a column named geom, as WKB. GeoParquet metadata describes it with the geometry types, bounding box and coordinate system.
The one from the source. If the source names none, WGS 84 is assumed when the coordinates fit.
The file names no coordinate system, and its coordinates do not fit WGS 84. The conversion stops instead of guessing.