r.in.gdal scale/offset not applied

[landam]

Reported by alf on 14 Apr 2012 21:45 UTC Hi,

r.in.gdal does not apply scale and offset specified as metadata (and correctly shown by gdalinfo) in the file to be imported.

Maybe it shoud/should not by default, but a specific flag might be advisable.

Best,

Alessandro

Operating system

Linux

GRASS GIS version and provenance

6.4.2

Migrated-From: https://trac.osgeo.org/grass/ticket/1640

[landam]

Modified by @landam on 14 Apr 2012 22:39 UTC

[landam]

Comment by hamish on 15 Apr 2012 06:39 UTC Hi,

afaik they are non-standard extensions and just treated as plain-text metadata by GDAL. heuristics might be possible (albeit fragile), but perhaps not advisable to apply them by default. (e.g. makes filtering out transformed non-NULL no-data values a bit more difficult)

for examples of semi-automatic transforms see: http://grass.osgeo.org/wiki/MODIS#Processing

and exponential flavour: (where Slope and Intercept are present but not y=mx+b) http://grass.osgeo.org/wiki/MODIS#Processing_2

Hamish

[landam]

Modified by @landam on 12 May 2016 06:42 UTC

[landam]

Modified by @landam on 25 Aug 2016 15:51 UTC

[landam]

Comment by @landam on 27 Aug 2016 13:42 UTC Milestone renamed

[landam]

Comment by stjo on 8 Dec 2016 08:21 UTC Hello,

specifying scale and offset directly in r.in.gdal would be helpful for Proba-V NDVI Data too. So you wouldn't have to use the r.mapcalc tool after the import.

Maybe it's a good reason to start this topic again :)

kind regards,

Jonas

[landam]

Comment by neteler on 26 Jan 2018 11:40 UTC Ticket retargeted after milestone closed

[landam]

Modified by neteler on 12 Jun 2018 20:48 UTC

[landam]

Comment by @landam on 25 Sep 2018 16:51 UTC All enhancement tickets should be assigned to 7.6 milestone.

[landam]

Comment by @landam on 25 Jan 2019 21:07 UTC Ticket retargeted after milestone closed