-
Notifications
You must be signed in to change notification settings - Fork 611
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
Allow zoom/pan scale binding for geo data #8856
Comments
Heads-up @joelostblom – There's a way to mark an issue on GitHub as a duplicate, rather than closing it as completed: https://docs.github.com/en/issues/tracking-your-work-with-issues/marking-issues-or-pull-requests-as-a-duplicate. I think it would be better to use that, since it's a bit confusing to see "closed this as completed" in the log here. Thanks! |
Duplicate of #3306 |
Oh, I didn't know of that functionality. It's handy to have as a saved reply, thanks! |
Didn't know either. Will save that as well. |
Great to see the ability to use interval selections with geoData with the VL5.7 release. This makes brushing between geographic and non-geographic views a possibility, which is something I've wanted for a long time. Thank you.
Does this make the possibility of a bind scales option for longitude/latitude data a viable prospect? It would be great to allow zooming and panning of geodata (which often benefit from zooming more than many other data types) via an interval selection so that we don't have to rely on range sliders to control projection parameters.
It wouldn't need any change to the API as it could use exactly the same API as used for cartesian positioning (which currently generates the error
Cannot read properties of undefined (reading 'on') [Warning] Scale bindings are currently only supported for scales with unbinned, continuous domains.
when used with longitude/latitude projected data)The text was updated successfully, but these errors were encountered: