#3125: d.legend.vect: take into account size_column/width_column in legend
-------------------------------------------------+-------------------------
Reporter: mlennert | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.5
Component: Default | Version: unspecified
Keywords: d.legend.vect, gsoc2016, symbol | CPU: Unspecified
size |
Platform: Unspecified |
-------------------------------------------------+-------------------------
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.
#3125: d.legend.vect: take into account size_column/width_column in legend
-------------------------+-------------------------------------------------
Reporter: mlennert | Owner: grass-dev@…
Type: | Status: new
enhancement |
Priority: normal | Milestone: 7.0.5
Component: Default | Version: unspecified
Resolution: | Keywords: d.legend.vect, gsoc2016, symbol
CPU: | size
Unspecified | Platform: Unspecified
-------------------------+-------------------------------------------------
Comment (by 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").
#3125: d.legend.vect: take into account size_column/width_column in legend
-------------------------+-------------------------------------------------
Reporter: mlennert | Owner: grass-dev@…
Type: | Status: new
enhancement |
Priority: normal | Milestone: 7.0.5
Component: Default | Version: unspecified
Resolution: | Keywords: d.legend.vect, gsoc2016, symbol
CPU: | size
Unspecified | Platform: Unspecified
-------------------------+-------------------------------------------------
Comment (by mlennert):
Replying to [comment:1 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.
#3125: d.legend.vect: take into account size_column/width_column in legend
-------------------------+-------------------------------------------------
Reporter: mlennert | Owner: grass-dev@…
Type: | Status: new
enhancement |
Priority: normal | Milestone: 7.0.5
Component: Default | Version: unspecified
Resolution: | Keywords: d.legend.vect, gsoc2016, symbol
CPU: | size
Unspecified | Platform: Unspecified
-------------------------+-------------------------------------------------
Comment (by 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.
#3125: d.legend.vect: take into account size_column/width_column in legend
-------------------------+-------------------------------------------------
Reporter: mlennert | Owner: grass-dev@…
Type: | Status: new
enhancement |
Priority: normal | Milestone: 7.0.5
Component: Default | Version: unspecified
Resolution: | Keywords: d.legend.vect, gsoc2016, symbol
CPU: | size
Unspecified | Platform: Unspecified
-------------------------+-------------------------------------------------
Comment (by mlennert):
Replying to [comment:3 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 ?
#3125: d.legend.vect: take into account size_column/width_column in legend
-------------------------+-------------------------------------------------
Reporter: mlennert | Owner: grass-dev@…
Type: | Status: new
enhancement |
Priority: normal | Milestone: 7.0.5
Component: Default | Version: unspecified
Resolution: | Keywords: d.legend.vect, gsoc2016, symbol
CPU: | size
Unspecified | Platform: Unspecified
-------------------------+-------------------------------------------------
Comment (by annakrat):
In [changeset:"69133" 69133]:
{{{
#!CommitTicketReference repository="" revision="69133"
d.vect: if size_column is used, write -1 to legend; symbol_size will be
then used for point legend, see #3125
}}}
#3125: d.legend.vect: take into account size_column/width_column in legend
-------------------------+-------------------------------------------------
Reporter: mlennert | Owner: grass-dev@…
Type: | Status: new
enhancement |
Priority: normal | Milestone: 7.0.5
Component: Default | Version: unspecified
Resolution: | Keywords: d.legend.vect, gsoc2016, symbol
CPU: | size
Unspecified | Platform: Unspecified
-------------------------+-------------------------------------------------
Comment (by mlennert):
Replying to [comment:5 annakrat]:
> In [changeset:"69133" 69133]:
> {{{
> #!CommitTicketReference repository="" revision="69133"
> d.vect: if size_column is used, write -1 to legend; symbol_size will be
then used for point legend, see #3125
> }}}
Thanks, Anna. This solves the "side issue" of this bug. The enhancement
wish is still valid, obviously.