Hi Micha and Hamish,
Do you see a way of fixing this?
I also tried it with a numeric variable that takes integer values only -- but the rgb_column created by v.colors still holds many missing values.
Many thanks!
Roy
To: [email protected]
From: Micha Silver <[email protected]>
Date: 12/19/2010 05:26PM
Cc: Hamish <[email protected]>, [email protected]
Subject: Re: [GRASS-user] SQL Error using "v.color"On 12/20/2010 12:07 AM, [email protected] wrote:
Here's the problem. That slash and "pse" (layer name) after the digit '1'.Hi Hamish and Micha,Many thanks for your help.To follow up on your earlier comment, submitting: v.db.connect -g map=pse layer=1 fs=";"yields: 1/pse;pse;cat;C://test/poverty/sqlite.db;sqlite
Any grep _expression_ with a character following the $GIS_OPT_LAYER will fail...Does this help?Thanks again,Roy-----Hamish <[email protected]> wrote: -----
To: Micha Silver <[email protected]>, [email protected]
From: Hamish <[email protected]>
Date: 12/19/2010 04:43PM
Cc: [email protected]
Subject: Re: [GRASS-user] SQL Error using "v.color"
Roy:
> Hi Micha, To follow up on my problem and your fix, I am no longer
> getting the error message i used to get. When i look at the attribute
> table, however, the RGB_column variable (which i named `hc2' in my
> example) -- created by v.colors -- has a lot of missing values. Do
> you have an idea why this is the case?
one thing to try is to remove the hc2 column (v.db.dropcol) and try again.
what does v.univar say about the numerical column?
Hamish
This mail was received via Mail-SeCure System.
--
Micha Silver
Arava Development Co. +972-52-3665918
http://surfaces.co.il
_______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
