Hi! I needed the docs are correct but as this is the second time it confuses people maybe the wording should be revised?
https://github.com/OSGeo/gdal/pull/5969 Any ideas? On Mon, 17 Oct 2022, 11:49 Nicolas Godet, <[email protected]> wrote: > Indeed, this is right. > My bad.. > ------------------------------ > *De :* Andrew C Aitchison <[email protected]> > *Envoyé :* lundi 17 octobre 2022 10:25 > *À :* Nicolas Godet <[email protected]> > *Cc :* [email protected] <[email protected]> > *Objet :* Re: [gdal-dev] [Doc] gdal_calc.py extent option > > On Mon, 17 Oct 2022, Nicolas Godet wrote: > > > Dear Devs, > > > > In documentation< > https://gdal.org/programs/gdal_calc.html#cmdoption-extent>, extent param > description seems a bit odd to me. > > > > > > union - the extent (bounds) of the output will be the minimal > > rectangle that contains all the input extents. > > > > intersect - the extent (bounds) of the output will be the maximal > > rectangle that is contained in all the input extents. > > > > Shouldn't it be the other way around? > > I think this *is* the right way round; > "all" can be misunderstood but I can not think of a clearer phrasing, > although "every one of" might help. > > > As I intend to add this option to QGIS gdal_calc window (very useful > > option), I must be sure. > > -- > Andrew C. Aitchison Kendal, UK > [email protected] > _______________________________________________ > gdal-dev mailing list > [email protected] > https://lists.osgeo.org/mailman/listinfo/gdal-dev >
_______________________________________________ gdal-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/gdal-dev
