this bug's URL: http://intevation.de/rt/webrt?serial_num=2690
-------------------------------------------------------------------------
Subject: System Response when no colortable is present
Platform: GNU/Linux/i386
grass obtained from: CVS
grass binary for platform: Compiled from Sources
GRASS Version: CVS
Dear developers,
not really a bug, but a proposal for a message when importing Raster-maps without colortables. The Problem appears when importing a rastermap without a proper colortable. When trying to display this map, nothing appears on the screen even when setting the region to the imported map. The system should then give a message, that no appropriate colortable is present and give a hint to using r.colors. Especially for new users it might be a great help so that they can be sure, no errors occured during import and they additionally should set a colortable.
Cheers
Stephan Holl
-------------------------------------------- Managed by Request Tracker
Request Tracker wrote:
this bug's URL: http://intevation.de/rt/webrt?serial_num=2690
Subject: System Response when no colortable is present
not really a bug, but a proposal for a message when importing
Raster-maps without colortables. The Problem appears when importing a
rastermap without a proper colortable. When trying to display this
map, nothing appears on the screen even when setting the region to the
imported map. The system should then give a message, that no
appropriate colortable is present and give a hint to using r.colors.
Especially for new users it might be a great help so that they can be
sure, no errors occured during import and they additionally should set
a colortable.
A map with no defined colour table should automatically use the
"rainbow" colour table.
If this isn't happening, file a bug report with details of how to
reproduce the problem.
--
Glynn Clements <glynn@gclements.plus.com>
On Mon, 15 Nov 2004 23:07, Glynn Clements wrote:
If this isn't happening, file a bug report with details of how to
reproduce the problem.
It happened to me the other day.
v.in.ascii to get points data then v.to.rast to convert to a raster.
There were some points that appeared (about 4 out of thousands).
I was really wondering if v.to.rast actually works in 5.7 till I tried
r.colors and it suddenly appeared.
Regards
Gordon
--
Gordon Keith
Programmer/Data Analyst
Marine Acoustics
CSIRO Marine Research
http://www.marine.csiro.au
There are things that we know that we know,
there are things that we know that we don't know and
there are things that we don't know that we don't know.
Gordon Keith wrote:
> If this isn't happening, file a bug report with details of how to
> reproduce the problem.
It happened to me the other day.
v.in.ascii to get points data then v.to.rast to convert to a raster.
There were some points that appeared (about 4 out of thousands).
I was really wondering if v.to.rast actually works in 5.7 till I tried
r.colors and it suddenly appeared.
That's a separate problem; v.to.rast explicitly sets a random
colourtable.
In the test cases I've tried, it seems to work ok. If you know of a
case which doesn't work, please submit a bug report with sufficient
details to allow reproduction.
--
Glynn Clements <glynn@gclements.plus.com>
Gordon Keith wrote:
> That's a separate problem; v.to.rast explicitly sets a random
> colourtable.
>
> In the test cases I've tried, it seems to work ok. If you know of a
> case which doesn't work, please submit a bug report with sufficient
> details to allow reproduction.
The case I have involves floating point data.
v.in.ascii in=bathydata out=test
d.rast test
seems to display points only where test==int(test)
Right. The random colour table only defines colours for discrete
(integral) values; most of the others define one or more ranges which
cover the entire range of the data.
r.colors test color=random
gives the message:
ERROR: Can't make random color table for floating point map
so v.to.rast probably needs to do something sensible with floating
point maps.
It should probably just not bother creating a colour table. The
default rainbow colour table should be adequate (it works with
floating-point maps, and it doesn't include black or white, so there's
no chance of the vectors accidentally blending with the background).
--
Glynn Clements <glynn@gclements.plus.com>