<HTML>
<HEAD>
<TITLE>Ps.map wish/question</TITLE>
</HEAD>
<BODY>
<FONT FACE="Skia, Verdana, Helvetica, Arial"><SPAN DEFANGED_STYLE='font-size:12.0px'>I haven’t used ps.map. It seems like a very useful module, but one that is fairly complex to use. While looking though the docs, however, it became apparent that it performs the same kind of display functions (to paper/postscript file) as many of the d.* modules do (to the display monitor)--and does a number of other special functions like setting paper size and margins of course. However, it uses a slightly different syntax to perform equivalent functions. E.g., rast [mapname] for ps.map vs. d.rast [mapname] for screen display. <BR>
<BR>
This led me wonder if it would be difficult to have ps.map accept as an alternative syntax, the d.* commands for which it has equivalent functions. D.vect (vareas, vlines, vpoints), d.rast (rast), d.barscale (scalebar), d.grid (grid or geogrid) seem easily apparent. There might be reasonably straightforward translation for additional d.* commands like d.frame and d.graph also.<BR>
<BR>
If this could be done, then either a set of normal GRASS commands—or even nicer, the file produced by d.save—could be piped to ps.map to make nice postscript output.<BR>
<BR>
How feasible would this be?<BR>
<BR>
Michael<BR>
____________________<BR>
C. Michael Barton, Professor of Anthropology<BR>
School of Human Evolution and Social Change<BR>
PO Box 872402<BR>
Arizona State University<BR>
Tempe, AZ 85287-2402<BR>
USA<BR>
<BR>
Phone: 480-965-6262<BR>
Fax: 480-965-7671<BR>
www: <www.public.asu.edu/~cmbarton><BR>
</SPAN></FONT>
</BODY>
</HTML>