duckdb-spatial

DuckDB reads remote geospatial data by using ST_Read or read_parquet with correctly formatted S3 or HTTPS URLs. You must configure S3 endpoint secrets to ensure the spatial extension can properly access and interpret remote files.

ST_Read and read_parquet differ in how they ingest geospatial data and which URL schemes they accept. ST_Read is designed for spatial formats, while read_parquet handles Parquet files and requires the spatial extension to interpret geometry columns.

read_parquet fails to recognize geometry columns when the DuckDB spatial extension is not installed and loaded. Enabling the spatial extension allows DuckDB to properly interpret and parse the geospatial geometry data stored in Parquet files.

Yes, you need to install and load the DuckDB spatial extension to parse GIS data. The extension provides the necessary functions like ST_Read and enables geometry column interpretation for geospatial workflows.

Configuring S3 endpoint secrets involves setting up the correct authentication credentials within DuckDB. This ensures that ST_Read and read_parquet can securely access and read geospatial data stored on remote S3 endpoints.

Limitations of the DuckDB spatial extension include URL handling misconfigurations and secret setup errors when accessing remote files. Understanding the specific URL schemes accepted by ST_Read and read_parquet is crucial to avoid ingestion errors.