this bug's URL: http://intevation.de/rt/webrt?serial_num=821
-------------------------------------------------------------------------
Subject: No raster legend in ps.map
Platform: Linux/Intel
Linux distro: RedHat
linux cpu: AMD (K6, ...)
Xwindows version: Xfree 3.3.6
Xwindows manager: KDE 2.x
TclTk version: tcl/tk 8.2
grass downloaded at: Hannover site
grass binary for platform: I compiled the sources myself
grass sources source: no, I got a source code package from the server, pre-2
c compiler name: gcc
When using
colormap y
end
in a ps.map input file, no colormap / legend turned up.
(It could of cource be me, I have not used that feature before, but as far as I could see from Markus' book and from the electronical documentation those two commands should produce a legend for my raster map)
-------------------------------------------- Managed by Request Tracker
Request Tracker wrote:
When using
colormap y
end
in a ps.map input file, no colormap / legend turned up.
The command is called "colortable".
--
Glynn Clements <glynn.clements@virgin.net>
At 07:54 01.11.01 +0000, you wrote:
Request Tracker wrote:
> When using
> colormap y
> end
> in a ps.map input file, no colormap / legend turned up.
The command is called "colortable".
Sorry for that, I used the command 'colortable' (The internet connection on my grass-box is currently down, so I had to report the bugs by memory)
Morten
Hanne og Morten Sickel wrote:
> > When using
> > colormap y
> > end
> > in a ps.map input file, no colormap / legend turned up.
>
>The command is called "colortable".
Sorry for that, I used the command 'colortable' (The internet connection on
my grass-box is currently down, so I had to report the bugs by memory)
I tried a quick test. ps.map does add the colour table, but it sets
the file's bounding box to the image, so the colour table is outside
of the bounding box.
GV will, by default, only display the bounding box. If you select the
paper size from the menu, you should see the colour table. When
printing the file, you should get the colour table.
As a workaround, you can delete the "%%BoundingBox:" line from the top
of the PostScript file.
I'll look into how much work is involved in fixing the bounding box
calculation. If it's too much, I'll just remove the "%%BoundingBox:"
line; no bounding box specification is better than one which is
incorrect.
--
Glynn Clements <glynn.clements@virgin.net>