[GRASS5] Re: [bug #3246] (grass) d.vect.thematic fails when the map is in another mapset

[Michael Barton]

Maciek,

I fixed the problem with d.vect.thematic not working with maps from a
different mapset. I think I've also improved the interval thematic mapping.
Please check out the newest version I just committed to the cvs and posted
to my website.

I tend to agree with you that

min - max 

looks better than

>min - max

although the second one is more accurate.

What does everyone else think?

Michael
______________________________
Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
Arizona State University
Tempe, AZ  85287-2402
USA

voice: 480-965-6262; fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton


> From: Maciek Sieczka <werchowyna at epf.pl>
> Date: Thu, 19 May 2005 19:39:31 +0200
> To: Michael Barton <michael.barton at asu.edu>, Paolo Cavallini via RT
> <grass-bugs at intevation.de>
> Cc: grass devel <grass5 at grass.itc.it>
> Subject: Re: [GRASS5] Re: [bug #3246] (grass) d.vect.thematic fails when the
> map is in another mapset
> 
> From: "Michael Barton" <michael.barton at asu.edu>
> 
>> 1. This math interval difference only happens for the first interval
>> (min-value) for invterval mapping.
> 
> Actually it also happens for the last interval too - max in the legend and
> the actual max are never the same. Is it also by design?
> 
>> This is to make sure that ALL values are
>> included and each value is included only once. If I specify [>lower value
>> and <= higher value] for each interval, I miss the minimum value of the
>> total range. If I specify [>=lower value and <=higher value] for each
>> range,
>> some values get counted twice. So the actual range of values mapped is
>> correct, but the lower value shown in the legend is slightly below the
>> actual minimum. The "11.5948" instead of "11.60" is some kind of internal
>> rounding error that I have no idea how to correct.
>> 
>> 2. I use the notation >lower value - higher value because of several
>> requests by users to do so. This makes it clearer that the interval is
>> greater (i.e., not inclusive of) the minimum and less than or equal to
>> (i.e., inclusive of) the maximum.
>> 
>> Michael
> 
> Understood. But anyway if I use the d.vect.thematic -l output for
> publication it may look supsicious for the eventual reader.  I'm not
> complaining here - I rerally apprecaite your effort and just trying to be
> helpfull. This legend looks suspicious and if somebody could fix it would
> great.
> 
> And what about the bug remaining (as in the title)? Any chances it will be
> fixed?
> 
> Maciek
> 
>> ______________________________
>> Michael Barton, Professor of Anthropology
>> School of Human Evolution and Social Change
>> Arizona State University
>> Tempe, AZ  85287-2402
>> USA
>> 
>> voice: 480-965-6262; fax: 480-965-7671
>> www: http://www.public.asu.edu/~cmbarton
>> 
>> 
>>> From: Maciek Sieczka via RT <grass-bugs at intevation.de>
>>> Reply-To: Maciek Sieczka via RT <grass-bugs at intevation.de>
>>> Date: Tue, 17 May 2005 17:59:21 +0200 (CEST)
>>> Cc: <grass5 at grass.itc.it>, <michael.barton at asu.edu>
>>> Subject: [bug #3246] (grass) d.vect.thematic fails when the map is in
>>> another
>>> mapset
>>> 
>>> sorry for this doubled post Michael - I forgot to CC the grass5 list the
>>> 
>>> previous time
>>> 
>>> 
>>> 
>>> Michael
>>> 
>>> 
>>> 
>>> Unfortunatelly the bug remains - it is impossible to use d.vect thematic
>>> on a
>>> 
>>> map which is not in the same mapset where the session was started. There
>>> is
>>> 
>>> always " Table '(...)' doesn't exist." information. Could you please try
>>> to
>>> 
>>> fix it?
>>> 
>>> 
>>> 
>>> The GRASSRGB switch works like a charm. Thanks!
>>> 
>>> 
>>> 
>>> But there is incostistency in the legend provided by d.vect.thematic -l:
>>> 
>>> 
>>> 
>>> Value range:  57.920000 -  69.400000
>>> 
>>> Mapped by 1 intervals of 11.5948
>>> 
>>> 
>>> 
>>> Color(R:G:B) Value
>>> 
>>> ============ ==========
>>> 
>>> 250:0:0  >57.3408 - 69.5148
>>> 
>>> 
>>> 
>>> As you can see the calculated "Value range" is different than in the
>>> legend's
>>> 
>>> "Value" column. No matter what interval is used (here nint=1) there is
>>> always
>>> 
>>> a difference. Could it be fixed too?
>>> 
>>> 
>>> 
>>> Also I think that the ">" sign between the color and the the value in the
>>> 
>>> legend should be removed - it doesn't help in anything and worsens the
>>> clarity
>>> 
>>> of the information. How do you think?
>>> 
>>> 
>>> 
>>> Maciek
>>> 
>>> -------------------------------------------- Managed by Request Tracker
>> 
>> _______________________________________________
>> grass5 mailing list
>> grass5 at grass.itc.it
>> http://grass.itc.it/mailman/listinfo/grass5
>> 
>