Michael wrote:
v.report
Ismael wrote:
v.to.db
Michael:
Yes. The cool (and sometimes confusing) thing
about GRASS is that often there are several ways
of getting the result you want.
n.b. in this case v.report is just a more obvious
wrapper-frontend to v.to.db.
Hamish
Hi all,
yes,yesYES thank you for your inputs 
it was a simple case of me not having a table with the info in to start
with, so once i remedied that with v.to.db (hello old friend, where have
you been hiding?) reports and map queries were a breeze, as well as easy
calculations directly on the table in sql (in pgadmin) to answer the
number-crunching I desired.
A happy chappy
and although I noted a coupla odd things in the digitiser (which I'm
still to check in north carolina dataset and give feedback on) i managed
to NOT do any bad combination of mouse-clicks and ruin the vector in
question 
soon i'll earn the badge of guru-beginner
-shane.
On Mon, 2012-01-30 at 12:53 -0800, Hamish wrote:
Michael wrote:
>>> v.reportIsmael wrote:
>> v.to.dbMichael:
> Yes. The cool (and sometimes confusing) thing
> about GRASS is that often there are several ways
> of getting the result you want.n.b. in this case v.report is just a more obvious
wrapper-frontend to v.to.db.Hamish