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

Box select support #92

Open
jbednar opened this issue Mar 1, 2016 · 4 comments
Open

Box select support #92

jbednar opened this issue Mar 1, 2016 · 4 comments

Comments

@jbednar
Copy link
Member

jbednar commented Mar 1, 2016

Once there is hover-tool support (issue #91), it would be great if we could support a box-select tool as well, providing essentially the same information as hovering but for a bounding box specified by the user interactively. Adding such support seems relatively straightforward once the hover tool support is in place, but it requires a dynamic query rather than static information provided when the plot is created. Even so, the data can presumably be computed directly from the static information already provided, and so it should not require re-running any of the stages of the datashader pipeline.

Lasso-tool support may make sense as well, again just as a selection of the existing aggregate bins.

@Tisagh
Copy link

Tisagh commented Mar 31, 2019

I found this while searching for some sort of select tool to use with Datashader.

I can subsample the data just fine and use in Bokeh or Holoviews with Bokeh on the backend but when using my full dataset neither can display the plots without slowing down the PC extremely. When I display with Datashader the selection tools don't work.

Is there a recommended work around for displaying datasets > 1M points with selection capabilities?

@jbednar
Copy link
Member Author

jbednar commented Mar 31, 2019

Sure, for now you just have to do it manually. My proposal above is for us to do most of the work for you, and to do it using the aggregated data so that it's super-fast, but you can always add selection tools and compute ranges "by hand". There's an example at https://github.com/pyviz-demos/glaciers , which can be run live on binder: https://mybinder.org/v2/gh/panel-demos/glaciers/master?urlpath=/proxy/5006/app

@Tisagh
Copy link

Tisagh commented Apr 1, 2019

Sure, for now you just have to do it manually. My proposal above is for us to do most of the work for you, and to do it using the aggregated data so that it's super-fast, but you can always add selection tools and compute ranges "by hand". There's an example at https://github.com/pyviz-demos/glaciers , which can be run live on binder: https://mybinder.org/v2/gh/panel-demos/glaciers/master?urlpath=/proxy/5006/app

Thank you

@ablythed ablythed added this to the wishlist milestone Jun 7, 2021
@jbednar
Copy link
Member Author

jbednar commented Jun 7, 2021

I think the recent link_selections support in HoloViews addresses some of this need, but it's still a relevant feature request: draw a box or lasso, then show via hover the aggregated values in that region.

@brendancol brendancol removed their assignment Jun 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants