Max Gabrielsson

Here's the PR for part 1: Minimal GeoParquet 1.0 support. When the spatial extension is installed and loaded, reading from a geoparquet file through DuckDB's normal parquet functionality will now...

@CGenie you're right, that's an issue indeed. The internal function signature is wrong even though I think the function is implemented correctly. I'll push a fix tomorrow.

Of course! Now that GeoArrow is more mature we should definitely make sure that we can export our geometry types properly to it. I'm not entirely sure how much we...

So I think the main difficulty here is enabling DuckDB's types to carry arbitrary metadata. As of now a "custom" duckdb type is really just a wrapper of another type...

@paleolimbot Sure! Here's my thoughts One way to solve this is to introduce some sort of new `ArrowConversionExtension` object in the `DBConfig` that extensions can subclass and provide a callback(s)...

Hey @paleolimbot did you end up working on this? Im thinking of revisiting this soon and have some fresh ideas on how to make this happen without blowing up the...

Great! Ill try to give it a shot soon then and ping you once I got something!

Yes! I have a sketch for these functions in an old PR so will definitely be added in the future!

@talllevy Hmm, looks like I didnt push it after all and I can't find it in my git stash... Anyway, the difficulty lies in writing the protobuf out incrementally in...

I've revisited this again the last couple of days, now that we have fast spatial filtering through the R-Tree index I think using duckdb as a tile server backend could...