spatial

Spatial queries on Overture Maps data are performed by loading DuckDB's spatial extension and reading the dataset via read_parquet. This enables distance calculations, containment checks, and spatial joins directly on the parquet files.

DuckDB reads and converts formats like Shapefile, GeoJSON, GeoPackage, and GPX using the ST_Read function. After loading the spatial extension, you can perform spatial analysis and export the results back into these geospatial formats.

Spheroid distance calculations require configuring geometry_always_xy and using ST_Point with POINT_2D inputs. This setup ensures that functions like ST_Distance_Spheroid accurately process coordinates for curved surface measurements.

Finding the nearest features to a point requires loading the spatial extension and querying the dataset via read_parquet. You apply spatial functions to calculate distances and sort the results to retrieve the top nearest records.

DuckDB supports spatial joins and density analyses through its spatial extension. You can use H3-based density patterns, containment checks with ST_Contains, and intersection operations to analyze spatial relationships across datasets.

DuckDB geospatial analysis requires explicit configuration, including loading the spatial extension and setting geometry_always_xy for spheroid calculations. Proper POINT_2D inputs are mandatory for accurate distance and area computations.