Opened 16 years ago
Last modified 15 years ago
#859 new enhancement
Assign vector colors from column
Reported by: | jctull | Owned by: | nobody |
---|---|---|---|
Priority: | minor: annoyance | Milestone: | Version 2.0.0 |
Component: | Vectors | Version: | Trunk |
Keywords: | vector color assignment rgb | Cc: | nikos.alexandris@… |
Must Fix for Release: | No | Platform: | All |
Platform Version: | Awaiting user input: | no |
Description
A great vector feature would be the ability to set color for vector features from an RGB column. This could be done similarly to GRASS's d.vect rgb_column assignment. See http://grass.itc.it/grass63/manuals/html63_user/d.vect.html
Change History (4)
comment:1 by , 16 years ago
Milestone: | Version 1.0.0 → Version 2.0.0 |
---|---|
Priority: | major: does not work as expected → minor: annoyance or enhancement |
comment:2 by , 16 years ago
I agree with the roadmap change, unless someone already has it in the pipeline, which I doubt.
I would still see an RGB code being the default, or perhaps it can be set as an option. This is the standard in GRASS, so we should consider inoperability. Again, maybe there can be an option to select between RGB columns or a single column that uses html codes.
follow-up: 4 comment:3 by , 15 years ago
Cc: | added |
---|
Hi all!
Any news with respect to assigning colors from an RGB list (=column in a vector map's attribute table)? And why not adopt grass's philosophy RRR:GGG:BBB.
I bombed into this ticket while searching for a way to automatically transfer the CORINE official colours from the grass database in qgis. It will be definetily a useful feature.
Cheers, Nikos
comment:4 by , 15 years ago
That format was exactly my thinking. I really hope to see this sometime. Otherwise, going from a raster to a vector AND maintaining color formatting is very difficult/impossible in Qgis. Is there another way?
Neat idea - maybe it would be better to use html style #AABBCC hex colour codes rather? Perhaps Magnus Homann would be interested in this....but I think its better left for 2.0 since we are trying to avoid further ui changes and renderer changes at this point.
Regards
Tim