[Re: [GRASS5] Ps.map wish/question]

[Maciek Sieczka]

(if I may ask one thing since ps.map is being discussed)

Could it be possible to use the colortable stored in GRASSRGB for rendering thematic vector layers with ps.map? So far a vector map can be assigned only a single color. If one needs to output a thematic vector layer (which happens to many of us I believe) it has to be converted to raster first. Besides all the burden and time required, the effect is that the output postscript file is *huge* because of raster contained and the quality is never as good as it could be if a vector map with colortable was supported directly in ps.map. And ps.map is capable of drawing vectors beautifully...

The next necessary thing would be a support for rendering legends of thematic vector maps in ps.map.

What are the chances such functionality would be available in ps.map someday? Besides that there has to be somebody willing to work on this :).

Best
Maciek

---------------------------------------------------------------
> Glynn Clements <glynn at gclements.plus.com> napisał(a):
> 
> Hamish wrote:
> 
> > 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.
> 
> Only a few d.* commands have ps.map equivalents. For most of those,
> ps.map only has an approximate equivalent. Also, you can't combine
> ps.map commands in the same way that you can combine d.* commands.
> 
> The most obvious example is that there is no ps.map equivalent of:
> 
> 	d.rast map1
> 	d.rast -o map2
> 
> as ps.map only allows a single raster, and doesn't have an equivalent
> of the -o switch (and that could only be implemented for level 3
> PostScript; earlier versions don't support masked images).
> 
> More generally, the d.* commands draw directly to the monitor, whereas
> ps.map commands tend to be stored up, and the rendering only starts
> once all of the commands have been read. The order in which commands
> are "executed" (i.e. rendered) doesn't necessarily correspond to their
> order in the input file.
> 
> -- 
> Glynn Clements <glynn at gclements.plus.com>
> 
> _______________________________________________
> grass5 mailing list
> grass5 at grass.itc.it
> http://grass.itc.it/mailman/listinfo/grass5