[GRASS5] Ps.map wish/question

Hamish hamish_nospam at yahoo.com
Mon May 16 21:34:37 EDT 2005


> Maybe I missed it in my cursory look at the ps.map docs, but it seems
> like some d.* command options are a subset of the ps.map commands. I
> assume that people using ps.map would continue to use the richer
> ps.map commands (i.e., not replace ps.map commands, but have ps.map
> also recognize some d.* commands). 

d.* is better for web & presentation graphics.
ps.map is better for hardcopy (ie paper) output for reports etc.
GMT is more powerful than ps.map, but less integrated with GRASS.


> I was thinking that if ps.map also would read relevant d.* commands it
> would be more easily scriptable.

Have a peek at the code for the file->print option in the d.m menu.

See also  http://intevation.de/rt/webrt?serial_num=1717


the ultimate way would be to have a command line flag --psmap or
something to have the display modules output their commands in ps.map
form. These could be cat-ed together for a prototype ps.map command
script. Perhaps that is a lot more trouble than it is worth, and a
shell/perl/python script to translate a couple of the more common d.*
commands from d.save into a ps.map command file is all that is needed.



Hamish




More information about the grass-dev mailing list