You don't mention if your geoparquet files have a covering bounding
box column. For the default WKB encoding, this is essential to avoid
full scan of the file.
I don't know about that - will check - but the basic
SetSpatialFilterRect on a GDAL Python layer works fine.
$ ogr2ogr poly_with_bbox.parquet autotest/ogr/data/poly.shp
$ ogrinfo poly_with_bbox.parquet --debug on
[...]
PARQUET: geo = { ... "covering":{"bbox":{...} }
[...]
PARQUET: Bounding box column 'geometry_bbox' detected for geometry
column 'geometry'
[...]
vs
$ ogr2ogr poly_without_bbox.parquet autotest/ogr/data/poly.shp -lco
write_covering_bbox=no
$ ogrinfo poly_without_bbox.parquet --debug on
no mention of bbox in debug traces
Hm, Parquet files are given at this point - I'm doing
consultancy/development for a client and Parquet is their choice so I
guess I have developer role now. :)
To be clear I meant using libduckdb+OGR ADBC as an alternate driver to
read Parquet files: see https://gdal.org/en/stable/drivers/vector/adbc.html
--
http://www.spatialys.com
My software is free, but my time generally not.
_______________________________________________
gdal-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
