Great notebook and thanks for sharing! You’ll want to combine the declaration of the DuckDB instance and the tables in the same cell, for example: ``` const geoDb = await DuckDBClient.of({world}); await geoDb.query(`INSTALL spatial; LOAD spatial;`); await geoDb.query(`CREATE OR REPLACE TABLE world AS SELECT …`); ``` If you instead define the table in a different cell (as above), there’s a good chance that cells that query the database (geoDb) could see it before the `world` table has been created. In other words, those queries mutate the database, and on Observable you don’t want to mutate a value defined in another cell because it causes unpredictable behavior. Whereas if you do the mutation within the cell that defines the value, it’s safe because downstream cells will wait for the mutation to be applied before running. Hope this helps.

Thank you very much for the feedback! I understand the issue and have updated the notebook accordingly. I hope it will be useful to the community.