Max Gabrielsson

Ok, like always caching is the culprit. We've made adjustments on our end so if you already have spatial installed a simple `UPDATE EXTENSIONS` or `FORCE INSTALL spatial` should give...

Yes! Like mentioned above this is related to strtod. We could try to use duckdbs own code for decimal parsing, although that would introduce a pretty ugly dependency between spatials...

This will be fixed in DuckDB v1.5 as ST_GeomFromText will be part of core and use DuckDBs own locale-independent decimal parsing functions.

DuckDB should only try to get the last modified time if the column is selected. Does it work if you eg only SELECT the content?

Hello! Thanks for opening this issue. Yes, this is currently expected, spheroid/sphere based joins require a more advanced indexing structure to handle wraparound the earth. But it is definitely something...

Hello! Thanks for reporting! My first thought was that the build side (pre) was not large enough to benefit from indexing, but changing the capacity of the r-tree nodes does...

Ok, I think I figured it out. In the blockwise-nl-join, we basically execute a cross-product and then evaluate the predicate on each pair. Because DuckDB is vectorized engine, we're being...

We're getting a native geometry type in DuckDB v1.5 so this won't be necessary anymore then!

I think thats a problem with the C-API, I will have a look at it before 1.5 eventually.

Hello! This is possible using [GDAL's virtual filesystem](https://gdal.org/en/stable/user/virtual_file_systems.html#chaining). E.g. ```sql FROM st_read('/vsigzip//vsicurl/https://object.data.gouv.fr/contours-administratifs/2024/geojson/departements-100m.geojson.gz') ; ┌─────────┬──────────────────────┬─────────┬────────────────────────────────────────────────────────────────────────────────────────────────┐ │ code │ nom │ region │ geom │ │ varchar │ varchar │ varchar │...