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

X-Pack Maps Draw Shape to Filter not intuitive when index patterns have multiple geo fields #99239

Closed
maihde opened this issue May 4, 2021 · 2 comments
Labels
[Deprecated-Use Team:Presentation]Team:Geo Former Team Label for Geo Team. Now use Team:Presentation enhancement New value added to drive a business result

Comments

@maihde
Copy link
Contributor

maihde commented May 4, 2021

Describe the feature: Currently, the draw shape, draw bounds, and draw distance tools will show a list of all indexes and all possible geo-fields. It would be more intuitive and less prone to user error if this list was restricted to the list of actual geo fields being used by the layers.

Describe a specific use case for the feature: We have an index pattern that has 5-6 different geospatial fields, but when users are using a map they are often only using one of those in a layer.

@botelastic botelastic bot added the needs-team Issues missing a team label label May 4, 2021
@wylieconlon wylieconlon added [Deprecated-Use Team:Presentation]Team:Geo Former Team Label for Geo Team. Now use Team:Presentation triage_needed and removed needs-team Issues missing a team label labels May 4, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-gis (Team:Geo)

@thomasneirynck thomasneirynck added enhancement New value added to drive a business result and removed triage_needed labels May 4, 2021
@maihde maihde mentioned this issue May 6, 2021
8 tasks
maihde added a commit to spectriclabs/kibana that referenced this issue May 6, 2021
This commit addresses elastic#99239 as a proof of concept.  The filter list is
now constrained only to geo fields that are actually used within the
layer sources.  Because the ultimate filter created is independent of
the index pattern, the UI instead shows the field type and deduplicates
when the same field exist in multiple index pattern.

This commit leaves room to refactor out some unneeded types and does not
yet add unittests.
maihde added a commit to spectriclabs/kibana that referenced this issue May 6, 2021
This commit addresses elastic#99239 as a proof of concept.  The filter list is
now constrained only to geo fields that are actually used within the
layer sources.  Because the ultimate filter created is independent of
the index pattern, the UI instead shows the field type and deduplicates
when the same field exist in multiple index pattern.

This commit leaves room to refactor out some unneeded types and does not
yet add unittests.
@nreese
Copy link
Contributor

nreese commented Jun 22, 2021

Closed by #100735

@nreese nreese closed this as completed Jun 22, 2021
maihde added a commit to spectriclabs/kibana that referenced this issue Jul 21, 2021
This commit addresses elastic#99239 as a proof of concept.  The filter list is
now constrained only to geo fields that are actually used within the
layer sources.  Because the ultimate filter created is independent of
the index pattern, the UI instead shows the field type and deduplicates
when the same field exist in multiple index pattern.

This commit leaves room to refactor out some unneeded types and does not
yet add unittests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Deprecated-Use Team:Presentation]Team:Geo Former Team Label for Geo Team. Now use Team:Presentation enhancement New value added to drive a business result
Projects
None yet
Development

No branches or pull requests

5 participants