← Use cases

Upload and filter GeoParquet using spatial SQL

GeoParquet usually shows up next to everything else you're querying. Load the file into a managed database and run spatial filters in the same engine without a sidecar GIS stack.

How it works

Step 1: Load Parquet into a managed database

Create a managed database with catalog geo, declare a store_locations table, and load stores.parquet into it. What name do I use when I query it?

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

Show my managed databases and list the tables inside q2.

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 ops blending telemetry files with fixed reference points.
  • Growth or marketing scoring leads from uploaded geographic lists.
  • Anyone joining warehouse tables to geo extracts without switching dialects.