Max Gabrielsson

Perhaps it would be better do something similar to the `Columns` method on statements instead of just returning the type id and name: https://github.com/duckdb/duckdb-node/blob/2722553743f45dcc5394011288f98ef92cc1f7bf/src/statement.cpp#L588 if you were to use the...

Hi! I _think_ I have a partial fix for this in https://github.com/duckdb/duckdb_spatial/pull/145, at least ShapeFiles, GeoJSONSeq and formats not using GDAL's internal thread pool should work.

Hi! Just letting you guys know we just got distribution of development builds for spatial working, so you should be able to install the latest spatial version for duckdb v0.9.1...

Sure, we should add support for all the unsigned type as well. But I think H3 should work with signed ints too, you might be able to work around this...

Actually, looks like GDAL doesn't support unsigned ints as OGR fields at all? But we should be able to do a try-cast internally (or error out) at least so that...

Yeah it is not supported yet. We already have our own Parquet reader extension in DuckDB and we are looking into how to integrate that with this extension in a...

I should explain: It is not supported because we don't bundle the Arrow library (which provides the parquet driver)

Ill just share that native Geoparquet support is planned to be the next big feature i work on for spatial, im just going to wrap up some refactoring and documrntation...

I currently have basic writing and reading working, with the "bbox" and "geometry_types" fields in the metadata being properly populated, but CRS handling is blocked since we can't store projection...

I think thats overselling it a bit, but in essence you get bounding box statistics per row group that potentially allow you to skip scanning entire groups if the parquet...