GeoParquet to GeoJSON
LocalConvert GeoParquet to GeoJSON in your browser — WKB geometry and attributes become features; failures loud, trade-offs disclosed. Free, no sign-up, no upload.
Drag files here, or click to browse
Supports PARQUET, GEOPARQUET
Choose fileGeoParquet → GeoJSON, locally in your browser. WKB geometries are read from geo metadata, GEOMETRY/GEOGRAPHY logical types, raw binary columns, or hex-encoded text; anything unmappable fails loudly instead of silently degrading.
What is it? GeoParquet to GeoJSON parses a GeoParquet file, decodes its WKB geometry and attributes, and writes GeoJSON. Geometry columns are detected via geo metadata, GEOMETRY/GEOGRAPHY logical types, raw binary WKB (read byte-exact even without GeoParquet typing), or hex-encoded WKB text; anything unmappable fails loudly in both languages instead of silently degrading, and skips/trade-offs surface as amber disclosure lines next to a map preview. Everything runs locally in your browser — nothing is uploaded.
TL;DR: GeoParquet to GeoJSON decodes WKB geometry and attributes into GeoJSON features, detecting the geometry column via geo metadata, logical types, raw binary WKB or hex WKB text. Drop a .parquet and it converts automatically — preview on the map, then copy or download. Free with no login; parsing runs locally, nothing uploaded.
How to use
- Drop a .parquet or .geoparquet file into the box — conversion starts automatically (no button, no options).
- Review the map preview and the amber disclosure lines (parsed-binary rows, skipped binary property columns, additional geometry columns dropped).
- Copy the GeoJSON or download it as a .geojson file.
FAQ
Is it local?
Yes, parsing is local.
Are attributes kept?
Yes — all columns become feature properties; INT64 values are emitted as text to preserve precision. Binary (BYTE_ARRAY) property columns are skipped and disclosed instead of landing as mojibake strings.
What if the geometry column has no GeoParquet typing?
Unmarked binary geometry columns are parsed byte-exact as WKB, and hex-encoded WKB text is decoded too; a value that is neither fails loudly naming the row — no silent geometry:null features.
Do I still need ogr2ogr or the gpq CLI?
Not for a one-off file — dropping it here converts GeoParquet to GeoJSON with no install (the CLI equivalent is "gpq convert example.parquet example.geojson"). Keep the CLI for scripted batches, server-side pipelines, or recompressing ZSTD files first — this tool reads uncompressed, Snappy and GZIP Parquet.
Should I convert to GeoJSON, or keep GeoParquet?
Keep GeoParquet for analytics — DuckDB and GeoPandas query it directly, and that is the format Overture Maps and open-data portals ship. Convert to GeoJSON for the things GeoJSON is the lingua franca of: web maps (Leaflet/MapLibre, which is exactly what the preview here renders), interchange with QGIS or older tools, and small files you want to inspect as plain JSON.
How big can my GeoParquet file be?
There is no upload limit because nothing is uploaded — the real bound is your device's memory, since decoding, WKB parsing and writing the GeoJSON all run in the browser. The result summary reports the feature count, output size and how many features came through without geometry, so you can confirm before downloading.
Are coordinates reprojected?
No — coordinates pass through unchanged and the output carries no CRS marker, so a non-WGS84 GeoParquet yields source-CRS numbers. Interpret them in the source CRS or reproject before converting if your target map expects WGS84 (RFC 7946).
Examples
- Drop in a .parquet → map preview + disclosure lines → get GeoJSON
Supported formats
Limitations
- Geometry columns are detected via GeoParquet geo metadata, GEOMETRY/GEOGRAPHY logical types, raw binary WKB bytes, or hex-encoded WKB text; detection and trade-offs are disclosed in-page.
- Values that cannot be mapped to a geometry fail loudly (no silent geometry:null); NaN/Infinity coordinates also fail loudly.
- Only the primary geometry column is read — additional geometry columns are disclosed as dropped.
- Uncompressed, Snappy and GZIP Parquet are supported; ZSTD and other codecs must be recompressed (GDAL/ogr2ogr or gpq) first.
- Rows whose geometry column is NULL come through as features without geometry (allowed by the GeoParquet spec) — the result summary counts them ("N without geometry").
- INT64 attribute values are emitted as text; no reprojection.
- Very large Parquet files may exceed browser memory.
Privacy
Privacy first: this tool runs entirely in your browser — your input and files never leave your device, and everything is cleared when you close the page.
Related tools
Standards & comparison
| Dimension | Vecaria (this tool) | Online converters (cloud) | Desktop professional CAD |
|---|---|---|---|
| Privacy | Runs locally in your browser; the file is not uploaded | You upload the file to a third-party server | Runs locally |
| Wait | No queue — as fast as your own device | Upload plus cloud queue | Local application startup |
| Standards support | GeoParquet (geo metadata) · WKB (OGC) | Varies by service, often older subsets | Full vendor protocol sets |
| Install footprint | 0 MB — runs in the browser | 0 MB | Several GB of storage |