Color rules are built from features category values (use=cat) or numeric data column (use=attr) defined by column option. For 3D vector maps is allowed to define color rules based on points or centroids z-coordinate (use=z). 3D vector lines are not supported.
The raster option allows user to specify a raster map from which to copy the color table, similarly raster_3d option for 3D raster map.
The rules color table type will cause v.colors to read color table specifications from given file and will build the color table accordingly. See r.colors manual page for details.
If the user specifies the -w flag, the current color table file for the input map will not be overwritten. This means that the color table is created only if the vector map does not already have a color table. If this option is not specified, the color table will be created if one does not exist, or modified if it does.
Alternatively the color rules can be stored in a string column (rgb_column) by saving the RRR:GGG:BBB values suitable for use with d.vect.
v.colors map=soils_general layer=1 color=wave
v.to.db map=soils_general layer=1 option=area column=AREA v.colors map=soils_general layer=1 color=wave use=attr column=AREA
v.colors map=soils_general layer=1 color=wave use=attr column=AREA rgb_column=GRASSRGB # See some GRASSRGB values: v.db.select map=soils_general where="cat < 4" cat|OBJECTID|AREA|PERIMETER|GSLNC250_|GSLNC250_I|GSL_NAME|GRASSRGB 1|1|0|164616.125|2|1|NC113|212:42:127 2|2|0|30785.529297|3|2|NC096|212:42:127 3|3|0|87572.882812|4|3|NC097|212:42:127
v.colors -c map=soils_general rgb_column=GRASSRGB
Existing color table can be removed by -r flag.
v.colors -r map=soils_general
v.colors.out map=soils_general rules=soils.colr v.colors map=soils_general rules=soils.colr
v.db.dropcolumn map=soils_general column=GRASSRGB
See also wiki page Color tables (from GRASS User Wiki)
ColorBrewer is an online tool designed to help people select good color schemes for maps and other graphics.
Last changed: $Date$