Hi,
recently I have added to the vector library support for color tables
as we know from raster engine. I have also rewritten existing
`v.colors` module [1] to C. Original python script which uses temp
raster maps has been moved to add-ons and renamed to `v.colors`. If
you set up color table for vector map using `v.colors`, the data are
rendered by `d.vect` colorized. The module can optionally write color
rules to the attribute table (if option `rgb_column` is given), in
this case you need to call `d.vect` with -a flag (as you are used to).
There is one open issue. How to write color tables for vector maps
which are not located in the current mapset. I was thinking about
'vector/<name>/colr2`, but it would require quite lot changes in
gislib (at least in G__ls()) etc, the second option which came to my
mind is 'vector2/<name>/colr2' as destination file for color table.
What do you think?
Martin
[1] http://grass.osgeo.org/grass70/manuals/html70_user/v.colors.html
--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
HI,
2011/8/22 Martin Landa <landa.martin@gmail.com>:
recently I have added to the vector library support for color tables
one note: this step introduced new dependency for vectorlib -
rasterlib. Probably it would be more clear solution to move color
tables/rules subroutines from rasterlib to gislib (leaving as todo).
Martin
--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
2011/8/22 Martin Landa <landa.martin@gmail.com>:
as we know from raster engine. I have also rewritten existing
`v.colors` module [1] to C. Original python script which uses temp
similarly to `r.colors.out` there is also new `v.colors.out` [1].
Martin
[1] http://grass.osgeo.org/grass70/manuals/html70_user/v.colors.out.html
--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
Martin Landa wrote:
There is one open issue. How to write color tables for vector maps
which are not located in the current mapset. I was thinking about
'vector/<name>/colr2`, but it would require quite lot changes in
gislib (at least in G__ls()) etc, the second option which came to my
mind is 'vector2/<name>/colr2' as destination file for color table.
What do you think?
I'd suggest using the same mechanism as for rasters, but with a
different top-level directory name, e.g. vcolr2/<mapset>/<name>.
OTOH, it may be better to replace this feature with "views", i.e. the
ability to create a new map which takes its data from some other map
but which can have its own metadata (colour table, etc).
--
Glynn Clements <glynn@gclements.plus.com>
Hi,
2011/8/22 Glynn Clements <glynn@gclements.plus.com>:
There is one open issue. How to write color tables for vector maps
which are not located in the current mapset. I was thinking about
'vector/<name>/colr2`, but it would require quite lot changes in
gislib (at least in G__ls()) etc, the second option which came to my
mind is 'vector2/<name>/colr2' as destination file for color table.
What do you think?
I'd suggest using the same mechanism as for rasters, but with a
different top-level directory name, e.g. vcolr2/<mapset>/<name>.
done in r47867.
Martin
--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa