Excellent! Thanks for the answers.
When I've explored a bit more I might implement the overview sizes just so
we can match downstream tools (the current motivation is like-for-like
performance comparison, I haven't looked there but I think odc goes very
low level to eke out speed).
Cheers, Mike
Michael,
Hi, can we specify overview sizes exactly?
No, the BuildOverviews() interface onlys take an array of overview
factors. It is up to the driver implementation to decide how it computes
the overview size from the main raster size and overview factor.
The COG driver is a bit of a
Hi, can we specify overview sizes exactly? I have this odd grid that is
36000x17999, and I get consequently yucky overview sizes:
gdal_create -outsize 36000 17999 -ot Int8 -co SPARSE_OK=YES -a_srs
EPSG:4326 -a_ullr 0 17999 0 36000 weird.tif
gdal_translate weird.tif cog.tif -of COG
gdalinfo
