Skip to content
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

Hover tool support #91

Closed
2 of 4 tasks
jbednar opened this issue Mar 1, 2016 · 3 comments
Closed
2 of 4 tasks

Hover tool support #91

jbednar opened this issue Mar 1, 2016 · 3 comments
Assignees

Comments

@jbednar
Copy link
Member

jbednar commented Mar 1, 2016

Because datashader produces an image rather than a collection of glyphs, there is no direct information available to the plotting program about the precise numerical values of plotted data. This information can be made available separately from the image, in a way that a plotting program (e.g. Bokeh) can display using the "hover" or "tooltips" mechanism, revealing values corresponding to the current mouse pointer location. At a minimum this information could just be the numerical value of that pixel, but it can be expanded to include counts and minimum/maximum values (if e.g. average or total values are being plotted), various statistical measures, etc.

It may be useful to bin this information on a grid coarser than the aggregation grid, which simply involves a pass over the aggregate grid to merge adjacent cells' data. In this case, it would be helpful if the hover tool showed the outline of the grid cell whose data is being shown, for clarity.

Tasks (may need to be expanded):

  • Implement fixed example of making information visible by hovering
  • Decide on an API for making the information available from the pipeline in general
  • Extend InteractiveImage to make use of data other than the image itself, perhaps by optionally accepting a dictionary or tuple, and grabbing the image key's value in that dictionary
  • Update some of the examples to include hover information

Some of this implementation may overlap with the support for color keys/legends in issue #90, in that it requires the underlying library to make information available about the data shown in an image.

@apaytuvi
Copy link

apaytuvi commented Mar 2, 2016

I'm not too much into the project's code, but I can help if you want.

@jbednar
Copy link
Member Author

jbednar commented Mar 2, 2016

@apaytuvi, thanks! We'll certainly need testers, in any case, and would love to have feedback!

@tommycarstensen
Copy link

tommycarstensen commented Mar 21, 2017

Has this been implemented? I'm happy to be a tester.

Oh, I think this is now issue #126.

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

4 participants