DuckDB-Wasm Reads Geoparquet 1.1 in cloud shell but not in test example

[jtbaker]

What happens?

Hi, thanks for the awesome tool - I'm really excited about potential use cases for WASM. While tinkering around with using it to read from a new GeoParquet 1.1 file published from Overture maps on an S3 bucket, in a test project it seems like it is reading the geometry column as a blob instead of a geometry, according to the spec.

I searched through the GH Issues and didn't see anything mentioning this specific issue (I know the GeoParquet functionality is fairly new).

Notably, this only happens in my own project, and not using the same code/data on shell.duckdb.org. I don't know white enough about WASM to fully debug it - in the commit history, I see that the duckdb git submodule was updated to use v1.1.1 recently, which I believe should be able to read geoparquets natively now. Perhaps I am dynamically loading an older version of the spatial extension?

I've attached a stackblitz link here that reproduces the issue: https://stackblitz.com/edit/vitejs-vite-7nv57v?file=src%2Fdb.ts

To Reproduce

use this stackblitz example: https://stackblitz.com/edit/vitejs-vite-7nv57v?file=src%2Fdb.ts

Browser/Environment:

Version 1.70.119 Chromium: 129.0.6668.70 (Official Build) (arm64)

Device:

Macbook Pro M2

DuckDB-Wasm Version:

^1.28.1-dev106.0

DuckDB-Wasm Deployment:

shell.duckdb.org

Full Name:

Jason Baker

Affiliation:

n/a

[carlopi]

I think you might need the latest (dev) version of duckdb-wasm. New version to be tagged

[jtbaker]

I think you might need the latest (dev) version of duckdb-wasm. New version to be tagged

Thanks for your response @carlopi. The confusing thing is is that I have my package.json pinned to the same version @duckdb/[email protected] shown as the duckdb-wasm version in this link, where everything works as expected.

If the shell version is somehow different than my version, does that mean I would need to compile the .wasm files on my own and serve those instead of a prebuilt version from npm?

Edit:

Ok, this was resolved with npm i @duckdb/duckdb-wasm@next instead of npm i @duckdb/duckdb-wasm or npm i @duckdb/duckdb-wasm@latest

I can leave this issue open in case other people run across the same issue until duckdb 1.1.1 compatibility is released, or close it.