-
Notifications
You must be signed in to change notification settings - Fork 25
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
Problem with ship_traffic legend #279
Comments
I have noticed this and this is part of the work I am actively working on right now - hoping to get this fixed soon. |
Is there a workaround? I'd love to give a live demo tomorrow during my final presentation here at NATO CMRE in Italy, 11:00 Italy time. |
I'll have a look this evening. This legend is already generated with a workaround so I don't expect it will be hard to hide (or simply filter out) those annoying numbers (which is probably the correct thing to do tbh as the vessel types are supposed to be grouped into the named categories) |
Here is the simple fix I've found so far: tiles * labels * points.opts(show_legend=False) * legend.opts(xaxis='bare',yaxis='bare', title='') Looks like |
@rsignell-usgs I've updated the deployment to fix the legend and which also includes some new hover functionality (WIP): https://ship-traffic.pyviz.demo.anaconda.com/ship_traffic |
I just had to discover a similar fix for the Census example. Seems like the automatic legend (which I totally don't remember us implementing!) needs a way to pass a mapping from category value (12) to category name (Tug). |
@jlstevens , awesome! Just in time for my live demo!!!! |
I think that a mapping option would make sense! When using categorical datashader operations in holoviews, I would hope we don't need the mapping as we would set the names explicitly. |
I'm guessing something changed with one of the packages, because when I run the interactive ship traffic cell, I get two legends. The first one is coming from the
points
datashader object but I can't figure out how to turn it off! Help @jlstevens !The text was updated successfully, but these errors were encountered: