-
-
Notifications
You must be signed in to change notification settings - Fork 404
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
Polygons limited to 1 vdim #1963
Comments
We've recently refactored the data interface behind Path/Polygons and can now support multiple dimensions. Supporting this is one of the major outstanding features for the 1.9 release, so hopefully I'll have an update on this soon. |
@philippjfr — You rule! I guess close this if you feel its resolved or wait until 1.9. |
If you're plotting choropleths, then using the geopandas interface that I'm working in geoviews on will probably be the easiest thing. |
The PR was just merged Path, Contours and Polygon now support arbitrary numbers of value dimensions. |
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 bounds on
vdims
forhv.Polygons
is (1, 1) which I don't quite understand as other plots likehv.Scatter
have no upper bound.I'm recreating the texas choropleth example but I need more than 1 vdim so that when a user hovers over a Polygon they can see raw values that contextualize the normalized value I'm using for the heatmap levels. I might just be using
hv.Polygons
wrong, so if there is a way to add more visual dimensions let me know and I'll close this issue.Thanks!
The text was updated successfully, but these errors were encountered: