You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a developer I understand why we are using --co in one case and --config in the other, but I'm not sure it's terribly obvious to a user. If we are creating an overview, should creation option--co COMPRESS=JPEG be understood to apply to that overview? In this case it makes sense, but I'm not sure blurring the lines between creation and configuration options, as a general practice, would actually reduce confusion.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Small remark: in both gdaladdo and gdal raster overview add case, in your above scenario, none of the config options should be necessary as the GeoTIFF driver will use by default the settings from the full resolution dataset
Feature description
I'm looking at an example from https://blog.cleverelephant.ca/2015/02/geotiff-compression-for-dummies.html, where we first convert a raster:
and then add overviews
As far as I can see, this is best replaced in the new CLI by
As a developer I understand why we are using
--co
in one case and--config
in the other, but I'm not sure it's terribly obvious to a user. If we are creating an overview, should creation option--co COMPRESS=JPEG
be understood to apply to that overview? In this case it makes sense, but I'm not sure blurring the lines between creation and configuration options, as a general practice, would actually reduce confusion.Additional context
No response
The text was updated successfully, but these errors were encountered: