-
Notifications
You must be signed in to change notification settings - Fork 572
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Two legends when using same column for both fill and color aesthetics #304
Comments
mjwillson
changed the title
Two legends when using fill and color aesthetics
Two legends when using same column for both fill and color aesthetics
May 15, 2014
Note: in this specific case I managed to work around it like so:
|
Wow, a nice cheap hack. |
arnfred
added a commit
to arnfred/ggplot
that referenced
this issue
Jun 14, 2014
As shown in yhat#304 and yhat#89 the current legend is drawn once per aesthetic (outside of x and y). This behaviour creates duplicate information when we use for example color and fill along the same variable. I've reworked the legend to group information per variable and display for example one line showing both shape, color and alpha information. The reworked legend also address: yhat#273. New Features - Group legend information per variable - Implement alpha - Better position legend (The vertical position was centered according to the top of the frame before) - Fixed issue with legend overlapping - Fixed problem with legend inventing numeric values. For numeric columns with less than 5 unique values, the current legend would interpolate them to write 5 continuous values Things that doesn't work: - No custom rearrangement (say, making swapping line 1 and 2 in the legend) - Legend might be longer than plot. Currently it breaks in to two columns, but if the plot is drawn smaller then I can't see a way to adjust the legend to this behaviour Changes: - I've personally had the problem that the legend would interpolate between numeric values even when there were less than 5 unique values in the data. I've changed this behaviour so the legend puts a label for every value when there are less than 8. Currently the color scheme in this case is discrete, but I'm not convinced this is the best solution. I generally think distinguishing between discrete and continuous data types makes sense, but for some continuous cases we might want to use the set of values that are present in the data instead of interpolating. I'm unsure whether the way I've changed this is the right way to do it, so I welcome comments on this matter.
Merged
has2k1
pushed a commit
to has2k1/plotnine
that referenced
this issue
Apr 25, 2017
As shown in yhat/ggpy#304 and yhat/ggpy#89 the current legend is drawn once per aesthetic (outside of x and y). This behaviour creates duplicate information when we use for example color and fill along the same variable. I've reworked the legend to group information per variable and display for example one line showing both shape, color and alpha information. The reworked legend also address: yhat/ggpy#273. New Features - Group legend information per variable - Implement alpha - Better position legend (The vertical position was centered according to the top of the frame before) - Fixed issue with legend overlapping - Fixed problem with legend inventing numeric values. For numeric columns with less than 5 unique values, the current legend would interpolate them to write 5 continuous values Things that doesn't work: - No custom rearrangement (say, making swapping line 1 and 2 in the legend) - Legend might be longer than plot. Currently it breaks in to two columns, but if the plot is drawn smaller then I can't see a way to adjust the legend to this behaviour Changes: - I've personally had the problem that the legend would interpolate between numeric values even when there were less than 5 unique values in the data. I've changed this behaviour so the legend puts a label for every value when there are less than 8. Currently the color scheme in this case is discrete, but I'm not convinced this is the best solution. I generally think distinguishing between discrete and continuous data types makes sense, but for some continuous cases we might want to use the set of values that are present in the data instead of interpolating. I'm unsure whether the way I've changed this is the right way to do it, so I welcome comments on this matter.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Leads to a plot with two copies of the legend for type a / b. (Same happens if I leave out the geom_line)
The text was updated successfully, but these errors were encountered: