Hi,
why was the r.info "-m" flag (in grass 6x) removed in grass 7? Difficult to
implement, not useful?
Thanks, Nikos
Hi,
why was the r.info "-m" flag (in grass 6x) removed in grass 7? Difficult to
implement, not useful?
Thanks, Nikos
Nikos:
why was the r.info "-m" flag (in grass 6x) removed in grass 7?
Difficult to implement, not useful?
it was moved into 'r.info -e'.
I think the idea was to have a less complicated view for the
module GUI, but to me it makes it less useful from the command
line. (2c)
probably the "none" values for 'r.info -e' should just be empty,
to make them easier to parse & work with `eval` directly.
Hamish
Nikos:
> why was the r.info "-m" flag (in grass 6x) removed in grass 7?
> Difficult to implement, not useful?
Hamish:
it was moved into 'r.info -e'.
I think the idea was to have a less complicated view for the
module GUI, but to me it makes it less useful from the command
line. (2c)
...here, still, mechanically typing `r.info -rm` very often
probably the "none" values for 'r.info -e' should just be empty,
to make them easier to parse & work with `eval` directly.
I guess so, Nikos
On Sat, Aug 3, 2013 at 2:50 AM, Hamish <hamish_b@yahoo.com> wrote:
probably the "none" values for 'r.info -e' should just be empty,
to make them easier to parse & work with `eval` directly.
Yes, this would be good.
I imported "black marble" with r.in.gdal, then r.composite and get
GRASS 7.0.svn (europe_laea):~ > r.info -e blackmarble2012_italy.rgb
title= (blackmarble2012_italy.rgb)
units="none"
vertical_datum="none"
timestamp="none"
which isn't quite `eval` parseable...
Markus