On Wed, 2008-08-06 at 01:14 +0100, Glynn Clements wrote:
Nikos Alexandris wrote:
The -g and -e switches make grey.log and grey.eq redundant
By the way, something I don't understand (copy-paste from the manual):
The -e flag equalizes the original raster's color table. It can
Dear list,
I try to adapt the color table of a raster file using an ascii file ( rules
option) with the following statement:
r.colors [EMAIL PROTECTED] color=rules
'rules=/sonne3/.../GIS/colorscript_farben_temp'
Hence the following message comes up:
color, rules, and raster options are
Hi,
2008/8/5 christian Brandt [EMAIL PROTECTED]:
I try to adapt the color table of a raster file using an ascii file ( rules
option) with the following statement:
r.colors [EMAIL PROTECTED] color=rules
'rules=/sonne3/.../GIS/colorscript_farben_temp'
Hence the following message comes up:
christian Brandt wrote:
I try to adapt the color table of a raster file using an ascii file
( rules option) with the following statement:
r.colors [EMAIL PROTECTED] color=rules
'rules=/sonne3/.../GIS/colorscript_farben_temp'
Hence the following message comes up:
color, rules, and
Hi,
2008/8/5 Glynn Clements [EMAIL PROTECTED]:
What it says; you can't use both color and rules. If you use
color=rules, the rules are read from stdin (equivalent to -i). If
you use rules=..., the rules are read from the specified file.
So, just omit the color=rules option, i.e.:
r.colors
On Tue, 2008-08-05 at 21:30 +0200, Martin Landa wrote:
Hi,
2008/8/5 Glynn Clements [EMAIL PROTECTED]:
What it says; you can't use both color and rules. If you use
color=rules, the rules are read from stdin (equivalent to -i). If
you use rules=..., the rules are read from the specified
On Tue, 2008-08-05 at 22:47 +0200, Martin Landa wrote:
Hi,
2008/8/5 Nikos Alexandris [EMAIL PROTECTED]:
[...]
I remember facing this error message some time ago which sounded very
logical. Since then I never force a color when I want to use rules.
Maybe an additional reference in
Martin Landa wrote:
I try to adapt the color table of a raster file using an ascii file (
rules option) with the following statement:
r.colors [EMAIL PROTECTED] color=rules
'rules=/sonne3/.../GIS/colorscript_farben_temp'
Hence the following message comes up:
color, rules, and
On Tue, 2008-08-05 at 22:00 +0100, Glynn Clements wrote:
[...]
The -g and -e switches make grey.log and grey.eq redundant
By the way, something I don't understand (copy-paste from the manual):
The -e flag equalizes the original raster's color table. It can preclude
the need for grey.eq rule,
Martin Landa wrote:
I remember facing this error message some time ago which sounded very
logical. Since then I never force a color when I want to use rules.
Maybe an additional reference in the manual wouldn't leave any space for
doubts.
that 'color=rules rules=path_to_file' ends
Nikos Alexandris wrote:
The -g and -e switches make grey.log and grey.eq redundant
By the way, something I don't understand (copy-paste from the manual):
The -e flag equalizes the original raster's color table. It can preclude
the need for grey.eq rule, when used as -e color=grey. Note
Hamish wrote:
If reading from stdin remains, it will be via -i, although
I'm inclined to simply remove the feature altogether
(it doesn't work well the GUI).
I agree that -i is confusing from the auto-gen GUI.
Well; not just confusing. If you run a module from the GUI, and it
expects
12 matches
Mail list logo
