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

[Maps] Global fit data to bounds option #29991

Closed
alexfrancoeur opened this issue Feb 4, 2019 · 4 comments · Fixed by #64702
Closed

[Maps] Global fit data to bounds option #29991

alexfrancoeur opened this issue Feb 4, 2019 · 4 comments · Fixed by #64702
Assignees
Labels

Comments

@alexfrancoeur
Copy link

alexfrancoeur commented Feb 4, 2019

In the Maps app today, we have layer specific "fit data to bounds" options. However, with the ability to search and filter across multiple layers (and dashboard embeddability options in the future), it'd be great if we could fit data to bounds on a global level. Similar to the control seen in region and coordinate maps.

image

@alexfrancoeur alexfrancoeur added release_note:enhancement [Deprecated-Use Team:Presentation]Team:Geo Former Team Label for Geo Team. Now use Team:Presentation labels Feb 4, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-gis

@alexfrancoeur
Copy link
Author

@nreese I would love to see this as a control. But for the embeddability use case, it'd be interesting to have a global config that is just "automatically fit to data". That way, when a map is embedded any filters applied to the dashboard will automatically fit to the map. This could kill two birds with one stone (#2054)

@alexfrancoeur
Copy link
Author

@thomasneirynck this would be a good addition to the new "tools" menu

@thomasneirynck
Copy link
Contributor

this might be a little tight, but now that ES supports the geo_bounds agg, we can introduce this. I put on 7.8 label, just to indicate priority.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants