OSGeo
Doc: Description of gdal_translate "-strict" argument is unclear
What is the bug?
Don't be forgiving of mismatches and lost data when translating to the output format.
Mismatches of what? Lost data from what? (data type conversion, presumably?)
It looks like the flag is passed to CreateCopy but also affects the handling of zero-band datasets in GDALTranslate.
Steps to reproduce the issue
none
Versions and provenance
master
Additional context
No response
data type conversion, presumably?
yes, mostly. That's a driver specific decision to decide what in strict mode must be absolutely preserved, but my recollection is that it can perfectly account for the input data type is what 90% of drivers that check the bStrict flag will do (but only a minority of drivers actually care about that flag)
Regarding the gdal_translate_lib specific logic, this was introduced related to the TileDB driver per https://github.com/OSGeo/gdal/commit/7601a637dfd204948d00f4691c08f02eb7584de5#diff-105a02c4f1d97ed21a207d81b6d18b3d8b26c46951c91f00eb217b12cf172b6eR660 . It is related to its subdataset handling, but reviewing the code I cannot figure it out... Given how obscure that is, I don't think that's (this TileDB specific thing I mean) worth trying to document..
