Skip to content

Plotly Offline 3D Surface Plots: Customize the x & y tickvals/ticktext AND ensure readability of the axis labels #3822

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

Closed
jhthompson12 opened this issue Apr 30, 2019 · 2 comments

Comments

@jhthompson12
Copy link

Hello Plotly People, I am moving this from plotly.py in response to @jonmmease 's request.

Firstly, thank you very much for developing this incredible tool. You are all amazing. And apologies in advance if I did not submit this properly, this is my first time ever submitting a feature request.

This post is in response to a question I recently asked in detail on the Plotly forum found here.

In essence, when creating a surface plot, I would like to specify the values that are presented on the x and y axes AND set the maximum number of my custom axis tick mark values that will be displayed. At the moment, I can set the custom values with tickvals/ticktext, but the axis shows all of the ticktext that I provide. The nticks parameter almost provides the functionality that I'm looking for, but it doesn't seem to work with custom axis markers (nticks can only be used when tickmode = ‘auto’)

The following image shows how with a lot of tickvals/ticktext, the axis becomes unreadable.

Thank you for looking into this and please let me know if I need to provide any more information.

-Joe

@archmoj
Copy link
Contributor

archmoj commented Apr 30, 2019

@jhthompson12 have you tried increasing layout.scene.yaxis.aspectratio?
It maybe helpful to improve the example you provided.
https://plot.ly/python/3d-axes/

@etpinard
Copy link
Contributor

etpinard commented May 1, 2019

Thanks for writing in @jhthompson12

Your request is very similar to the one in #1812 most particularly from #1812 (comment), so I'll merge your ticket into #1812

@etpinard etpinard closed this as completed May 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants