Convert GeoParquet to GeoJSON
Free, in-browser conversion from GeoParquet (.parquet, .geoparquet) to GeoJSON. Drop a file below — the converted output downloads automatically. No account, no software install, no upload retention for direct conversions.
About GeoParquet
GeoParquet is the OGC-blessed extension to Apache Parquet that adds geometry columns (WKB-encoded by default) and a `geo` schema-metadata block. It is the format of choice for analytical pipelines — Athena, BigQuery, DuckDB, Polars, and Spark all read it directly.
About GeoJSON
GeoJSON is an open standard (RFC 7946) for representing points, lines, polygons, and feature collections as JSON. It is the lingua franca of web mapping — small, human-readable, and consumed by every major mapping library.
How to convert GeoParquet to GeoJSON
- Drop your GeoParquet file (.parquet, .geoparquet) on the area above, or click to browse.
- The file is parsed server-side — geometries are normalised to a GeoJSON FeatureCollection internally, then written out as GeoJSON.
- The converted file downloads automatically. No retention; nothing is kept on the server.
Want to inspect the geometry before converting? Use the full 3D viewer instead — it renders the file on a MapLibre globe with toggleable layers, then lets you convert from the same toolbar.
Related conversions
FAQ
Is the GeoParquet to GeoJSON converter free?
Yes. rooot viewer is free and requires no account. There are no per-conversion charges.
Do I need to install software?
No. The conversion runs server-side, the result is delivered as a download. Works in any modern browser.
Are my files kept after conversion?
Direct conversions through this page (the form above) do not persist files at all — the bytes are parsed in memory and the result returned. Persistence only happens when you use the main viewer's Open in roooute button, and persisted files are deleted within 24 hours.
What is the maximum GeoParquet file size?
50 MB per file.
Does the converter preserve attribute properties?
Yes — feature properties round-trip through the canonical GeoJSON intermediate. Schema differences between source and target formats may force lossy coercions (e.g. shapefile DBF column-name length limits), but rooot viewer applies sensible defaults.