Details Ticket 3587


Comment | Reply | Take | Open


Serial Number 3587
Subject v.to.rast: assign a proper color table to the output
Area grass6.1
Queue grass
Requestors werchowyna@epf.pl
Owner none
Status resolved
Last User Contact Tue Aug 30 11:43:47 2005 (3 yr ago)
Current Priority 30
Final Priority 70
Due No date assigned
Last Action Tue Aug 30 11:43:52 2005 (3 yr ago)
Created Sat Aug 27 19:58:04 2005 (3 yr ago)

Transaction History Ticket 3587


Sat, Aug 27 2005 19:58:04    Request created by guest  
Subject: v.to.rast: assign a proper color table to the output

Platform: GNU/Linux/i386
grass obtained from: CVS
grass binary for platform: Compiled from Sources
GRASS Version: cvs 23.08.05

v.to.rast fails to create a colortable covering the whole data range in the output
raster. Usually only some or none cells are visible on the raster
produced by v.to.rast. This is missleading. At first I thought there was
something wrong with my data, but it showed it was all about the colortable.
r.colors fixes the problem but it is not obvious for the user.

Maciek
Sat, Aug 27 2005 20:03:43    Area changed to grass6.1 by msieczka  
Mon, Aug 29 2005 14:53:20    Mail sent by mneteler  
Related to the v.to.rast color table problem there might
be below code in:
vector/v.to.rast/support.c



int
update_fcolors (char *raster_name)
{
    struct Colors colors;

    /* G_read_fp_range(raster_name, G_mapset(), &range); */
    /* G_get_fp_range_min_max(&range, &min, &max);       */
    G_make_rainbow_colors(&colors, 0, 360);
    G_write_colors(raster_name, G_mapset(), &colors);

    return 0;
}


Should it be min max instead of 0 360?

Markus
Mon, Aug 29 2005 16:40:59    Mail sent by hmitaso@unity.ncsu.edu  
Return-Path <hmitaso@unity.ncsu.edu>
Delivered-To grass-bugs@lists.intevation.de
Message-ID <43131E6C.4040507@unity.ncsu.edu>
Date Mon, 29 Aug 2005 10:40:44 -0400
From Helena Mitasova <hmitaso@unity.ncsu.edu>
User-Agent Mozilla Thunderbird 1.0.2 (X11/20050317)
X-Accept-Language en-us, en
MIME-Version 1.0
To Markus Neteler via RT <grass-bugs@intevation.de>
Cc werchowyna@epf.pl, grass5@grass.itc.it
Subject Re: [GRASS5] [bug #3587] (grass) v.to.rast: assign a proper color table to the output
References <20050829125320.E15D01005A2@lists.intevation.de>
In-Reply-To <20050829125320.E15D01005A2@lists.intevation.de>
Content-Type text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding 7bit
X-PMX-Version 4.7.1.128075, Antispam-Engine: 2.0.3.2, Antispam-Data: 2005.8.29.13
X-Spam-Status No, hits=-4.9 tagged_above=-999.0 required=3.0 tests=BAYES_00
X-Spam-Level
Markus Neteler via RT wrote:
> Related to the v.to.rast color table problem there might
> be below code in:
> vector/v.to.rast/support.c
> 
> 
> 
> int
> update_fcolors (char *raster_name)
> {
>     struct Colors colors;
> 
>     /* G_read_fp_range(raster_name, G_mapset(), &range); */
>     /* G_get_fp_range_min_max(&range, &min, &max);       */
>     G_make_rainbow_colors(&colors, 0, 360);
>     G_write_colors(raster_name, G_mapset(), &colors);
> 
>     return 0;
> }
> 
> 
> Should it be min max instead of 0 360?

yes,  I am guessing that this color table was there for v.to.rast2 for 
the line direction angle - min,max should cover it.

Helena
> 
> Markus
> 
> -------------------------------------------- Managed by Request Tracker
> 
> _______________________________________________
> grass5 mailing list
> grass5@grass.itc.it
> http://grass.itc.it/mailman/listinfo/grass5


Tue, Aug 30 2005 11:43:47    Mail sent by mneteler  
I have update v.to.rast to use min/max instead of 0..360
for floating point maps for the rainbow color table.
Also updated:

- rainbow instead of random colors for integer maps.
- description.

Markus
Tue, Aug 30 2005 11:43:52    Status changed to resolved by mneteler  
Comment | Reply | Take | Open

You are currently authenticated as guest.
[Show Configuration] [Login as another user]

Users Guide - Mail Commands - Homepage of RequestTracker 1.0.7 - list any request