-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
TimeSeries chart too restrictive on required DataFrame structure? #1190
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
Not missing anything... |
Sure. just a warning, I work a lot with pandas, so maybe my viewpoint is biased that way.
with the time data only in the Index of the dataframe (accessible via df.index.to_series() as already used in several Bokeh examples) and one or more columns of a DataFrame.
|
I already started a discussion for better Bokeh interface some weeks ago at pandas here. Some people mentioned there a general pandas API that several plotting engines could hook up to? Maybe it's worth to contact pandas peeps about that? pandas-dev/pandas#6962 |
Discussion is now more than 3 months old. Can re-open if renewed interest. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
The new
TimeSeries
chart in 0.6.0 requires a multi-level index in the columns of thepd.DataFrame
.I believe most users would have the time axis data only once in the main index of the
pd.DataFrame
, e.g. when analyzing a bunch of measurements that were taken with several sensors, but at the same time. It feels like you guys implemented the more advanced version of supporting several different time data axes first without implementing the simple case of having just one time column? Or am I missing something?The text was updated successfully, but these errors were encountered: