[GRASS-dev] [GRASS GIS] #2052: r.in.gdal should not by default call first three bands red, green, blue
GRASS GIS
trac at osgeo.org
Thu Aug 1 04:13:40 PDT 2013
#2052: r.in.gdal should not by default call first three bands red, green, blue
----------------------------+-----------------------------------------------
Reporter: mlennert | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.0
Component: Raster | Version: svn-trunk
Keywords: r.in.gdal, rgb | Platform: Unspecified
Cpu: Unspecified |
----------------------------+-----------------------------------------------
Comment(by mlennert):
Replying to [comment:5 mmetz]:
> Replying to [comment:4 mlennert]:
> > Replying to [comment:2 hamish]:
> > > I'm not 100% sure, but ISTR that it was libgdal doing that,
r.in.gdal was just passing the band name along untouched. --> gdal band
name detection bug?
> >
> > Yes and no: GDAL does return a !ColorInterp info which is "wrong", but
this is apparently due to the original data:
[https://trac.osgeo.org/gdal/ticket/5177]
>
> >
> > The problem in r.in.gdal is here:
[https://trac.osgeo.org/grass/browser/grass/trunk/raster/r.in.gdal/main.c#L525].
>
> That means the -k flag should be removed and the band number always used
as suffix, or optionally the meaning of the -k flag should be reverted
such that color names are appended only on request?
Duh. I have to admit that I completely overlooked this flag. So the
question is: what is less confusion for newcomers: have rgb extensions
sometimes not be correct, or always only have numbers ?
Moritz
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2052#comment:6>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list