I understand your point. However....
If we change it (content or name), we also need to change the code in
d.vect.thematic, thematic.tcl, and possibly some other scripts.
This is modeled on r.univar.sh. But of course vectors are not like rasters.
Vectors have attributes in separate attribute tables. But they can have
multiple attribute tables. There was a reason for making it possible to
select the table and driver, but I don't remember exactly what it was. I
think it had to do with not being able to use PostgreSQL or other non-dbf
databases properly in d.vect.thematic.
So this can be done if necessary, but it needs to be done carefully and
completely, making sure that the changes cascade correctly through all
related pieces.
The best thing would be to put median and quartiles into v.univar and switch
the whole bunch over to that.
Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics and Complexity
Arizona State University
phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton
From: Markus Neteler via RT <grass-bugs@intevation.de>
Reply-To: Markus Neteler via RT <grass-bugs@intevation.de>
Date: Thu, 11 May 2006 23:03:34 +0200 (CEST)
To: <michael.barton@asu.edu>
Subject: [bug #4432] (grass) Transaction (mneteler)this bug's URL: http://intevation.de/rt/webrt?serial_num=4432
Thu, May 11 2006 23:03:34: Request 4432 was acted upon.
Transaction: Mail sent by mneteler
Queue: grass
Area: grass6
Subject: v.univar,v.univar.sh: input table or vector?
Owner: mbarton
Requestors: werchowyna@epf.pl
Status: open-------------------------------------------------------------------------
Hi,I think that v.univar.sh is wrongly implemented. It should
use v.db.select and not provide the possibility to
select database and driver, but only layer.
Otherwise the name should be db.univar.sh (which isn't
really desired).
Markus
-------------------------------------------- Managed by Request Tracker