-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Allow position aesthetics other than x and y? #3898
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
Comments
To add another use case besides ternary diagrams, a |
Discussion of geometry scales happened here: #3659 (comment) |
I think this is a good discussion to take, but not of high priority. It would be nice to come up with a more extendible setup than what we currently have |
Similar to @teunbrand's use case of mapping 3D to 2D, I think there are also use cases that map 1D to 2D.
|
This may not be exactly the same issue, but I have a ggplot extension which defines multiple I can apply the transformation manually in |
This is an issue so that we remember to come back to this. As noted by. @clauswilke here: #3561 (comment) , constructing ternary diagrams using ggplot requires a lot of copying of ggplot2 code, which has resulted in the current breaking of the ggtern package.
At the heart of the issue is that a ternary diagram is a transformation of 3 variables, rather than 2. Currently, x- and y-scales are hard-coded in the
Layout
and other places, which makes adding an additional aesthetic that should be treated as a position aesthetic impossible (see #2540 (comment) ). I can't find the thread, but this came up in the context ofcoord_sf()
, wheregeometry
is also sort of a position aesthetic (that only sort of acts like one).One approach would be to allow coords to define what is a position aesthetic. Currently there are a lot of definitions of "what is a position aesthetic" (#3342). If I remember correctly, this will break Coord and possibly Facet subclasses that are passed
scale_x
andscale_y
.Anyway, not pressing, just something that should be considered when coords are revisited.
The text was updated successfully, but these errors were encountered: