If that is the case it is really kind of clunky as it breaks the
relationship between the original value and the colour. I will have to
look into this further.
I went the route of doing a select distinct on the text attribute and
doing a v.db.update on RGBDATA for each distinct attribute with a
colour. The biggest issue of course is if you edit the attribute then
the colour is immediately wrong.
On 2015-01-28 03:04 PM, Markus Neteler wrote:
(cc list)
On Wed, Jan 28, 2015 at 10:50 PM, Richard Nairn
<[email protected]> wrote:
If I look at v.colors the column specification says it needs a numeric
column, not a text column - thus precluding a rules file for a text column?
Mhh, maybe you are right (I didn't use it too much yet, perhaps others
in the list have suggestions).
If yes, you could generate a numeric column and populate it for
example with v.db.update.
Markus
_______________________________________________
grass-user mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-user
