Opened 8 years ago
Last modified 6 years ago
#3125 new enhancement
d.legend.vect: take into account size_column/width_column in legend
| Reported by: | mlennert | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 7.6.2 |
| Component: | Default | Version: | unspecified |
| Keywords: | d.legend.vect, gsoc2016, symbol size | Cc: | |
| CPU: | Unspecified | Platform: | Unspecified |
Description
I don't know if this is foreseen, but it would be marvelous if d.legend.vect could take into account the size_column*size (+ the -r flag) and the width_column*width_scale info when drawing the symbols in the legend.
I know this is much more complicated, and maybe this would warrant a separate module, but being able to show the sizes of symbols in the legend is a basic necessity when using these features.
A possible solution could be to find the min, mean and max values and to create three symbols at their respective size that represent these values (including writing the value into the legend so that one can understand what each sized-symbol represents).
I imagine this would be way too much for the current GSoC, but I'm creating this ticket so we do not forget.
Attachments (1)
Change History (14)
follow-up: 2 comment:1 by , 8 years ago
by , 8 years ago
| Attachment: | d.legend.vect_symbol_size.diff added |
|---|
Patch to add flag to use symbol_size also for point symbols
comment:2 by , 8 years ago
Replying to mlennert:
One related issue that should be dealt with ASAP: when doing proportionate symbols with size_column, the size parameter for symbols represents a scaling factor, not a size. However, d.legend.vect uses it as a size indicator meaning that when you set your scaling factor to a small value (values can easily close to zero, such as 0.001) the symbol in the legend also becomes very small.
Probably the best solution would be to allow the use d.legend.vect's symbol_size also for symbols, maybe through a flag to d.legend.vect ("Use symbol_size also for point symbols").
I've added a patch to show what I mean, but I'm acting a bit blindly, here, for lack of thorough understanding of d.legend.vect, so this definitely needs to be checked.
follow-up: 4 comment:3 by , 8 years ago
This was definitely planned, maybe not for this GSoC, but this is partially the reason the legend information is exported from d.vect - to allow for more complex legends. The temporary solution now could be to write -1 instead of size and then d.legend.vect interprets it to use symbol_size for vector point, we avoid another flag.
comment:4 by , 8 years ago
Replying to annakrat:
This was definitely planned, maybe not for this GSoC, but this is partially the reason the legend information is exported from d.vect - to allow for more complex legends. The temporary solution now could be to write -1 instead of size and then d.legend.vect interprets it to use symbol_size for vector point, we avoid another flag.
I'm not sure I understand: where do you suggest to write -1 ? Into the legend file ? But then only if size_column is set ?
comment:6 by , 8 years ago
comment:7 by , 8 years ago
| Milestone: | 7.0.5 → 7.3.0 |
|---|
comment:10 by , 6 years ago
| Milestone: | 7.4.1 → 7.4.2 |
|---|
comment:11 by , 6 years ago
| Milestone: | 7.4.2 → 7.6.0 |
|---|
All enhancement tickets should be assigned to 7.6 milestone.
One related issue that should be dealt with ASAP: when doing proportionate symbols with size_column, the size parameter for symbols represents a scaling factor, not a size. However, d.legend.vect uses it as a size indicator meaning that when you set your scaling factor to a small value (values can easily close to zero, such as 0.001) the symbol in the legend also becomes very small.
Probably the best solution would be to allow the use d.legend.vect's symbol_size also for symbols, maybe through a flag to d.legend.vect ("Use symbol_size also for point symbols").