-
-
Notifications
You must be signed in to change notification settings - Fork 789
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
Feature Request: GEO Functions #292
Comments
Will take a look. Thanks for the feature request! |
I made a first version of the GEO feature support: After experimenting with the interface, I've found that I'm not particularly keen on displaying the latitude/longitude data and map in the sidebar. As an alternative, we can introduce a "Preview" menu item to the context menu that appears when a zset item is right-clicked. This would open a separate window to display the latitude/longitude data and map. Do you happen to have any suggestions, @rsmck? |
That's great! I agree that it clutters the side bar and doesn't seem the right place for it, Preview in the context menu would be great, perhaps (if possible) also mimic the QuickLook behaviour in the OS so allow space bar to trigger that preview and if moving up/down the list using the arrow keys update the already open preview (QuickLook) window to the relevant key - much like browsing images in Finder? |
This is great, thank you! :D |
It would be nice if the Medis UI could show geospatial sorted sets as lat/lon rather than just integer values, even better to perhaps render a pin on a map (but appreciate that's a much bigger UI change)
As a geospatial set is just stored internally as a standard sorted set within redis, I guess this would require some sort of implementation to support selecting how the set is interpreted.
The text was updated successfully, but these errors were encountered: