Dear GDAL Community,
I am encountering a performance issue when using a VRT consisting of a
large number of source rasters and built-in C++ pixel function ("max"). I
would appreciate any guidance on whether some GDAL config option can
improve this, or I am doing something wrong, or this is a poten
Michael,
file size isn't the issue here, it is more the symptom of the driver
having to read one dataset to get on or metadata items it doesn't know,
than something it really needs (getting the file size is just a side
effect of opening a remote dataset)
Looking at the code I presume it must
Looking at some stac geoparquet datasets I created from a VRT, I see this in
the gdal debug output:
GDAL: GDALOpen(/Users/rdcrlmds/Downloads/test1.gti.parquet, this=0x1580079d0)
succeeds as Parquet.
GTI: Using assets.data.href as location field
GTI: Inspecting one feature due to missing metadata
