[GRASS5] ps.map, p.map and p.map.new

Markus Neteler neteler at geog.uni-hannover.de
Thu Apr 13 13:57:01 EDT 2000

On Thu, Apr 13, 2000 at 09:39:04AM -0700, Rich Shepard wrote:
> On Thu, 13 Apr 2000, Markus Neteler wrote:
> > to make it more complex:
> > ps.map.new is also there!
> Markus,
>   I wondered about that, but I didn't see it.
You can see in CVS, you will see in forthcoming GRASS 5 beta7.

> > Suggestion:
> >  - remove p.map
> >  - remove ps.map.old
> > 
> > Rename p.map.new to p.map
> > Rename ps.map.new to ps.map
>   I don't understand the differences. But, I am curious why we cannot have a
> single output/print module which encompases the variations in both p. and
> ps. Another variable could determine the output device (screen, html page,
> printer, plotter) and make the appropriate adjustments. In my opinion, this
> makes it much easier to maintain/improve and to use.
>   I've read the man pages for ps.map, p.map/p.map.new I see some differences
> among them, but nothing on the man pages explains when to use one or the
> other -- and why.

Well, p.* and ps.* are have the same purpose, but different output
formats. If being merged, as you suggested, it should become


(new "output" command class).

A flag to select the output format would be required. Say:
-f ps
-f ppm
-f ?

That might be a good idea, if not too complicated for the export


If you want to unsubscribe from GRASS Development
Team internal mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'
length: 2129
max: 0

More information about the grass-dev mailing list