Yes, it must be internal
Le mar. 8 juin 2021 à 21:21, a écrit :
> Thanks Thomas.
>
>
>
> Does cogger need a mask band to be internal as well, and not a sidecar
> file?
>
>
>
> -Mat
>
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osg
Thanks Thomas.
Does cogger need a mask band to be internal as well, and not a sidecar file?
-Mat
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Matt,
In the general case, cogger supports a tiff with internal overviews, i.e.
without a .tif.ovr sidecar file. The advanced usecase which takes multiple
files is a remnant of the time when gdaladdo was much slower than
successive runs of "gdal_translate -outsize 50% 50%", or for when you need
spe
I forgot to add: I tried adding the .ovr file in a manner similar to the Cogger
readme example but got an error:
~~~
$ cogger -output test.tif SPOT6_321_BeaverRiver_08Sep2018_NAD83_YAlbers.tif
SPOT6_321_BeaverRiver_08Sep2018_NAD83_YAlbers.tif.ovr
mucog write: load: cannot load multiple tifs if
Hi,
I took cogger for a first test drive and I'm confused. I'm relatively new to
the world of Cloud Optimized Geotiffs, so I don't know if my confusion is about
the COG format itself or cogger:
I fed a jpeg-in-geotiff file with external overviews (tif.ovr) and mask
(tif.msk) to cogger. The out
