DuckDB says it doesn't support it, but the underlying library days it supports it.
We might want to confirm that the duckdb-wasm included with Framework does have the spatial extension available. And that it can load GeoParquet.
If we confirm both of those, we should attempt a mass standardization to use GeoParquet (which our Python GeoPandas supports).
With that, we can build a high performance alternative to Mecone Mosiac where we can minimize data loads with HTTP Range requests against Parquet in a CDN, by only SELECTing a minimal column set on first load.
DuckDB says it doesn't support it, but the underlying library days it supports it.
We might want to confirm that the duckdb-wasm included with Framework does have the spatial extension available. And that it can load GeoParquet.
If we confirm both of those, we should attempt a mass standardization to use GeoParquet (which our Python GeoPandas supports).
With that, we can build a high performance alternative to Mecone Mosiac where we can minimize data loads with HTTP Range requests against Parquet in a CDN, by only SELECTing a minimal column set on first load.