[GRASS-dev] [GRASS GIS] #1640: r.in.gdal scale/offset not applied

GRASS GIS GRASS GIS developer
,
1

#1640: r.in.gdal scale/offset not applied
-------------------------+--------------------------------------------------
Reporter: alf | Owner: grass-dev@…
     Type: defect | Status: new
Priority: normal | Milestone: 6.4.3
Component: Default | Version: 6.4.2
Keywords: | Platform: Linux
      Cpu: Unspecified |
-------------------------+--------------------------------------------------
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

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/1640&gt;
GRASS GIS <http://grass.osgeo.org>

2

#1640: r.in.gdal scale/offset not applied
--------------------------------------+-------------------------------------
Reporter: alf | Owner: grass-dev@…
     Type: defect | Status: new
Priority: normal | Milestone: 6.4.3
Component: Raster | Version: 6.4.2
Keywords: r.in.gdal, scale, offset | Platform: Linux
      Cpu: Unspecified |
--------------------------------------+-------------------------------------
Changes (by martinl):

  * keywords: => r.in.gdal, scale, offset
  * component: Default => Raster

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/1640#comment:1&gt;
GRASS GIS <http://grass.osgeo.org>

3

#1640: r.in.gdal scale/offset not applied
--------------------------------------+-------------------------------------
Reporter: alf | Owner: grass-dev@…
     Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.0
Component: Raster | Version: 6.4.2
Keywords: r.in.gdal, scale, offset | Platform: Linux
      Cpu: Unspecified |
--------------------------------------+-------------------------------------
Changes (by hamish):

  * type: defect => enhancement
  * milestone: 6.4.3 => 7.0.0

Comment:

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

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/1640#comment:2&gt;
GRASS GIS <http://grass.osgeo.org>