Max Gabrielsson

Sure! Ideally we dont need the vsi stuff soon now that we have pur own http cache, will investigate further!

Hello! You need to setup VCPKG to pull in the required dependencies to build spatial. `unofficial-sqlite3` is the name for the sqlite package in VCPKG.

Hello! This is already implemented, ```sql DuckDB v1.4.1 (Andium) b390a7c376 Enter ".help" for usage hints. Connected to a transient in-memory database. Use ".open FILENAME" to reopen on a persistent database....

Hey @JoelJaeschke! I would strongly prefer a from scratch implementation, or a implementation using our existing dependencies (e.g. GEOS). Spatial already has a ton of third party code and it...

Hi! Thanks for opening this issue! Im unable to reproduce the error using the code you provided, both when building duckdb from source and when using the one provided by...

My hunch is that this was fixed by https://github.com/duckdb/duckdb-spatial/pull/452, but ill investigate

One thing that's on my todo list is investigating using sqlites memvfs in combination with its [zipvfs](https://sqlite.org/zipvfs/doc/trunk/www/howitworks.wiki) file system, potentially reducing the size of the embedded PROJ database even further.

This has been fixed on main/nightly. ```sql v1.0.1-dev4162 2077b0afed Enter ".help" for usage hints. Connected to a transient in-memory database. Use ".open FILENAME" to reopen on a persistent database. D...

Hello! The reason this isn't implemented is that DuckDB doesn't store SRID's for individual geometry values anyway (and probably never will). Although I guess you could make a `ST_AsEWKB(geometry, int)`...

That makes sense! Both the WKT and WKB writing code in spatial is a bit of a mess right now as it hasn't been rewritten to use the new way...