Register GeoArrow extensions by default

[kylebarron]

I was looking at how to get GeoArrow extension metadata on Arrow types exported to Python and I learned from @paleolimbot that I needed CALL register_geoarrow_extensions() to apply the GeoArrow metadata onto exported data.

Would it be possible to register those extensions by default? I imagine not everyone knows they exist.

[Maxxen]

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

[VGSML]

The current ArrowConverter implementation with the new logical type is still not working. Using the new arrow c-api (duckdb_to_arrow_schema, duckdb_schema_from_arrow) still defines the duckdb geometry as binary data with out extension metadata in the arrow and binary arrow data with extensions metadata (geoarrow.wkb) as blob.

[Maxxen]

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

[VGSML]

I got the same results when I tried to pass a table with geometry columns through the airport extension, so it is somewhere in the arrow_converter (ArrowConverter)

[rustyconover]

I'm just going to watch this thread, once it is ready to go, I'll happily add the GEOMETRY type to the list of DuckDB types tested in the Airport CI test suite.