Max Gabrielsson

So I've spent some time looking into this and done some tweaks to ST_Read spread out over the last couple of PR's, after #296 I can now get the first...

Hi! Thanks for opening this issue! This is something I've been thinking about for a while and would be great to support some day. However, scanning the GDF in the...

@kylebarron Thats sounds great! Id like to revisit #153 soon, even if support for "additional custom type metadata" is quite a bit away.

Hi! It sounds like there's a bunch of different issues at play here. The pure virtual abort in particular seems like it would be hard to reproduce and could originate...

Not unexpected, there's a couple of reasons why we're much slower than osm2pgsql - For every layer the osm driver has to scan through and consume all the preceding layers...

Hi! Thanks for reporting this issue! Ill try to have a look soon, but for now I think you can work around this using the csv output in combination with...

Ok I've partly figured out the issue - the issue is that GDAL doesn't understand that this is chardev file when going through DuckDBs filesystem and asks to create a...

Hi! duckdb spatial does not store the SRID inside the geometry type, its recommended to keep it in a separate column for now and in the future ST_Read might be...

You can't use `st_read_meta` for parquet files, parquet files are handled by duckdbs parquet extension and so in this case to read geoparquet metadata you should use the `parquet_kv_metadata` function....

To clarify, all the algorithms implemented as of now assume a planar coordinate system. This makes a lot of algorithms much easier and faster to implement and works well when...