← Use cases

Upload and filter GeoParquet using spatial SQL

Geospatial data often arrives as Parquet files with coordinates or WKT fields and needs to be queried with other tables. You can register these files as datasets and run spatial filters directly in the same query engine, without moving data into a separate system.

How it works

Step 1 — Create a dataset from Parquet

Upload stores.parquet as Store locations with SQL table store_locations—what name do I use when I query it?

Step 2 — Confirm lon/lat (or WKT) columns

Show my uploaded datasets, then open the one I pick so I can see each field and type.

Step 3 — Radius filter from a reference point

Using my store locations upload, which stores fall roughly near downtown San Francisco? Give id and name, up to 50.

See SQL Reference — Geospatial for units and other predicates (ST_Within, ST_Intersects).

Who uses this

  • Field operations combining telemetry files with fixed reference locations.
  • Growth or marketing teams scoring leads from uploaded geographic lists.
  • Workloads that query warehouse tables and uploaded geo extracts with one dialect.