Max Gabrielsson

Partially implemented in #74

Time flies! Ive recently completed a pretty major overhaul of the internal geometry representation used during execution so im planning on going back and adding the remaining missing measurement functions,...

Hi! There's a couple of things at play here. `ST_Transform` defaults to respecting the axis order defined by the CRS authority. `EPSG:4326` is defined as lat/lon, while `'EPSG:3857'` is defined...

> means always_xy must always be used for 4326 -> 3857 conversion of GeoJSON data when imported into DuckDB. Not necessarily, you could transform `OGC:CRS84` -> `EPSG:3857` instead in which...

> I don't expect DuckDB to be having any expectations regarding CRS, when DuckDB is not keeping track of CRS (or "CRS-blind"). And it generally doesn't. You have to supply...

What you are looking for is passing the `layer_name` argument like this ```sql COPY (SELECT ST_Point(1,2) as geom, 10 as i) TO './testing.gdb' WITH (FORMAT 'GDAL', DRIVER 'OpenFileGDB', GEOMETRY_TYPE 'POINT',...

No, I don't think this is supported yet, but it might be possible to implement in the future.

Hi @colinjamesstewart! Unfortunately not, we might maybe be able to start prototyping non-peristent in-memory only indexes before the end of the year. But would you mind telling me a little...

@colinjamesstewart For sure, I understand that once you reach billions of records, being able to prune out intersection candidates at the storage level becomes more or less mandatory, but at...

Yes, since our flatgeobuf support is based on gdal we do support pruning when reading flatgeobuf files, there is an optional "filter_bbox" argument you can pass to st_read to use...