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
[FEATURE] datetime formatting: enhance default formatting #13186
Comments
@muendlein Bokeh already supports multiple levels of datetime tick format context: https://docs.bokeh.org/en/latest/docs/user_guide/styling/plots.html#datetime-tick-context Are you proposing that this existing feature be used by default? I'm not sure there is anything that will satisfy everyone here, which makes me slightly inclined to preserve the status quo and simply make customization features as accessible and known a possible. |
@bryevdv Thank you for pointing out that multiple levels are already available! My proposal is two-fold:
Both of my points are essentially covered by the plotly library (example: https://plotly.com/python/time-series/#time-series-with-range-slider). |
@muendlein Did you want to submit a PR for consideration? Speaking plainly I think this will move much faster, even it if requires some iteration and back and forth, if someone champions a concrete proposal to start from. |
Problem description
Note: This probably needs some discussion.
Currently the default formatting provides ticks with mixed formats (see screenshots below). In my opinion this makes it extremely difficult to read the axis and to be honest I don't see any benefit over just having the same formatting for all ticks.
The first screenshot is probably an extreme example with three different formats but it highlights pretty well what the problem is.
Code for reference:
Feature description
Improve default formatting by avoiding mixed formats. Perhaps it might also be possible to adapt a Matlab style formatting which provides an additional label for the whole axis.
Potential alternatives
keep it as it is
Additional information
No response
The text was updated successfully, but these errors were encountered: