As a followup, I was able to get this working using gdal-master build from
conda (which is quite cool):
ogrinfo -ro -oo PRELUDE_STATEMENTS="LOAD SPATIAL" -oo PRELUDE_STATEMENTS="LOAD
PARQUET" ADBC:'overture-places.parquet' -sql "select st_astext(geometry), *
from \"overture-places\" where st_d
Hi Michael,
I've also noticed that the ADBC / Arrow interface of libduckdb seems to
be less efficient than their native API. I've no idea whether this is
for a fundamental cause or if it is "just" an implementation issue that
could be improved (on their side).
In particular I had the impress
Using gdal-master conda packages, trying to use the new ADBC driver for
libduckdb integration, I’m able to connect to a parquet dataset (only if it has
the parquet extension) but the geometry is not being recognized.
Seems to take a long time to load compared with duckdb. So, I must be doing
som
