Max Gabrielsson

Hello! Thanks for raising this issue (and providing the data!). I suspect this is a problem with our filesystem layer but I'm going to look into it.

Hi! Thanks for reporting this issue. This seems to be a DBeaver issue? Although I don't expect them to be able to read our internal geometry format (nor do I...

Seems like this is implemented on a case-by-case basis, at [least there's special handler code for PostGIS](https://github.com/dbeaver/dbeaver/blob/fb989655a38111fb1a6a8275cf4a0e69f4fdc50f/plugins/org.jkiss.dbeaver.ext.postgresql/src/org/jkiss/dbeaver/ext/postgresql/model/data/PostgreGeometryValueHandler.java#L161) I'd definitely like to investigate how hard it would be to add something...

Sorry about that, we're working on updating the docs and the readme here on GitHub properly. The ST_Envelope_Agg basically returns a bounding box (as a polygon) containing the bounding box...

Hmm, come to think of it it should probably be changed/aliased to `ST_Extent`, like in [PostGIS](http://www.postgis.net/docs/ST_Extent.html)

Hi! DuckDB's internal representation of the geometry type is not actually WKB, in fact it is very similar to PostGIS geometry representation, although with a different "header". However **I can't...

Hey! Since this is an issue with an upstream third-party dependency we probably won't invest too much energy into fixing this, but a workaround would be to pass the newly...

Hello! As of DuckDB 1.2.0 the duckdb [excel extension](https://duckdb.org/docs/extensions/excel.html#reading-xlsx-files) provides support for reading and writing xlsx files with greater efficiency and many more options. Therefore we're going to deprecate this...

Hi! The `GEOMETRY` is internally ambivalent to which axis order is used, as far as we know there's only an "x" and a "y", coordinate, whatever corresponds to lat or...

I hear you. I'll work on aligning with what PostGIS does (always lon/lat, ignore CRS axis-order definition) next chance I get.