Could anyone provide hints for creating a nice color ramp for the map used as the hue parameter of d.his suitable for representing an alpine valley in which the lowest elevations would be green going to brown, grey, and white for the highest elevations?
Could anyone provide hints for creating a nice color ramp for the map
used as the hue parameter of d.his suitable for representing an alpine
valley in which the lowest elevations would be green going to brown,
grey, and white for the highest elevations?
Could anyone provide hints for creating a nice color ramp for the map used as the hue parameter of d.his suitable for representing an alpine
valley in which the lowest elevations would be green going to brown, grey, and white for the highest elevations?
Thank you for the prompt reply. After reading the documentation it proves to be much easier than I was making it. I am embarrassed to have posted such a trivial question.
Thanks for your help.
--
Richard Greenwood
www.greenwoodmap.com
On Mon, Apr 19, 2004 at 08:56:12PM +0000, Richard Greenwood wrote:
Hamish wrote:
>>Could anyone provide hints for creating a nice color ramp for the map
>>used as the hue parameter of d.his suitable for representing an alpine
>>valley in which the lowest elevations would be green going to brown,
>>grey, and white for the highest elevations?
>
>
>
>see:
>http://intevation.de/rt/webrt?serial_num=2072
>
>thus,
>
>r.colors map=xxxx col=rules << EOF
>-11000 0 0 0
>-500 0 0 30
>-100 0 0 200
>-1 150 150 255
>0 0 150 0
>270 90 165 90
>300 90 175 90
>500 50 180 50
>500 70 170 70
>1000 70 145 75
>1000 70 155 75
>2000 150 156 100
>2800 220 220 220
>3000 255 255 255
>8850 255 255 255
>nv 255 255 255
>EOF
>
>
>i.e. [elevation Red Green Blue]
>
>or for your suggested colors, use these rules:
>
>0% green
>33.3% brown
>66.7% grey
>100% white
>
>
>Hamish
Thank you for the prompt reply. After reading the documentation it
proves to be much easier than I was making it. I am embarrassed to have
posted such a trivial question.
To make it less trivial, someone could implement above color table
into r.colors as 'terrain'...
> Thank you for the prompt reply. After reading the documentation it
> proves to be much easier than I was making it. I am embarrassed to have
> posted such a trivial question.
To make it less trivial, someone could implement above color table
into r.colors as 'terrain'...
Or maybe:
r.colors ... rules=<name>
which would just be shorthand for e.g.:
r.colors ... color=rules < $GISBASE/colors/<name>
That way, adding new tables (e.g. "terrain") would just be a matter of
adding a rules file; no coding involved.
The only cases which should really need to be coded are those which
can't be described by a fixed set of rules. BTW, most of the existing
colour tables could be implemented using rules; AFAICT, the only ones
which can't are "grey.eq", "grey.log" and "random".
Actually, maybe we should just change the semantics of the "color=..."
option so that anything other than "rules", "grey.eq", "grey.log" and
"random" is treated as the name of a rules file.
(I find the unsaturated a little too dark and too saturated, I'll fix it
someday I have time to give it some thought
Both try to present diffs in lowlands and shallow seas, the habitats of the
organisms we usually work with, and for ecology altitude and depth
differences mean far more the closer you are to sealevel, so the color ramps
focus on that by being very steep close to sealevel. So diffs in depths and
mountains are mostly toned down.
--
Gustavo Alcides Concheiro Pérez <gacp@d-konstruktors.org>
Unión de la Cruz del Sur
«Non serviam»
---
Clave pública GPG para gacp / GPG public key for gacp:
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.0.7 (GNU/Linux)