You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 13, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 13, 2026. It is now read-only.
I was eager to try it out on the latest Overture release data from yesterday.
I tried out this query in the Overture Maps Downloader tool: select * from read_parquet('s3://overturemaps-us-west-2/release/2024-03-12-alpha.0/theme=buildings/type=building/*') where bbox.minx > -73.510779 and bbox.miny > 41.171381 and bbox.maxx < -69.471306 and bbox.maxy < 42.98083 limit 100;. This will work fine in native duckdb, but returns Error: Error: Invalid Error: [object WebAssembly.Exception] here. I see a similar error in shell.duckdb.org so I'm guessing this is lack of wasm support for the underlying aws libraries.
@jwass, thank you so much! Yes, the Content Security Policy in the browser, I believe, doesn't allow the wildcard/glob (https://*) functions to be used because the entire app is running on the client side in the browser, with no servers involved (ref: duckdb/duckdb-wasm#1040 ). You can try:
Or, I believe you can create a list with all the parquet files you want to query from, like:
SELECT
id,
geometry
FROM
read_parquet(['s3://overturemaps-us-west-2/release/2024-03-12-alpha.0/theme=buildings/type=building/part-00150-4dfc75cd-2680-4d52-b5e0-f4cc9f36b267-c000.zstd.parquet','s3://overturemaps-us-west-2/release/2024-03-12-alpha.0/theme=buildings/type=building/part-00151-4dfc75cd-2680-4d52-b5e0-f4cc9f36b267-c000.zstd.parquet'])
WHEREbbox.minx>78.53608051444496ANDbbox.maxx<78.56248512255797ANDbbox.miny>25.483406547011967ANDbbox.maxy<25.521748210549873LIMIT2000;
We can implement a workaround in this app by utilizing STAC for the GeoParquet files stored in S3. This way, when a user zooms into a specific bounding box (bbox), we can intersect this bbox with the ones defined in the STAC catalog. This process will enable us to list the GeoParquet files containing data for the specified region.
Activity
yharby commentedon Mar 14, 2024
@jwass, thank you so much! Yes, the Content Security Policy in the browser, I believe, doesn't allow the wildcard/glob (https://*) functions to be used because the entire app is running on the client side in the browser, with no servers involved (ref: duckdb/duckdb-wasm#1040 ). You can try:
Or, I believe you can create a list with all the parquet files you want to query from, like:
We can implement a workaround in this app by utilizing STAC for the GeoParquet files stored in S3. This way, when a user zooms into a specific bounding box (bbox), we can intersect this bbox with the ones defined in the STAC catalog. This process will enable us to list the GeoParquet files containing data for the specified region.
jwass commentedon Mar 14, 2024
Thanks! I literally just discovered this about 10 minutes ago and came to say that it works for individual files. This is pretty cool!