GeoParquet
GeoParquet stores geospatial vector data — points, lines, and polygons — in Apache Parquet, with a specification for identifying geometry columns and related geospatial metadata.
viewparquet opens GeoParquet through its Parquet reader. You can browse the attribute table, inspect column names and DuckDB types, see geometry values in their stored form, filter non-spatial attributes with SQL, and export results. It does not currently render geometries on a map, decode them into GIS features, or validate GeoParquet CRS and metadata fields; use a geo-aware tool when you need those checks.
Drag a .parquet or .geoparquet file into viewparquet, or open a compatible object from S3 or an HTTPS URL.
Use the grid and schema information to identify attribute columns, DuckDB types, and the raw geometry column. The current metadata panel describes the loaded table; it is not a GeoParquet specification validator.
Filter rows by attributes, count categories, or sample records with DuckDB SQL, then export the tabular result to Parquet, CSV, or JSON Lines.
GeoParquet is Apache Parquet with a standardized way to identify geospatial vector data. It defines geometry columns and geo metadata such as encoding, geometry types, CRS, and optional bounds; a general Parquet reader can read the table, while a geo-aware tool interprets those fields.
Open it in viewparquet for a browser-based table and schema inspection. DuckDB-WASM reads a local file without a GIS install, but map rendering, decoded geometry inspection, spatial validation, and CRS checks still require a geo-aware tool.
GeoParquet geometry is commonly WKB (Well-Known Binary), although the specification also allows other encodings. viewparquet displays the stored column value and DuckDB type in the table; it does not currently draw the geometry or decode it into an interactive GIS feature.
GeoParquet is a compressed columnar file with richer schemas and a single-file layout, while shapefiles split a dataset across sidecar files and impose legacy field constraints. GeoParquet also fits analytical engines and object-storage workflows, but GIS compatibility should still be checked for your tools.
A local GeoParquet file is read in your browser with DuckDB-WASM and is not uploaded to viewparquet. A remote object is requested directly by your browser from its host; aggregate analytics never includes the filename, remote URL, geometry values, or file contents.
Drop a Parquet, GeoParquet, CSV, or JSON file into viewparquet: browse rows, run DuckDB SQL, and export results in-browser without uploading the dataset to viewparquet. Optional AI sends messages and applicable context directly to the provider you choose; review Settings → AI before use.