[DOCS] Update info about geo_shape bounding boxes#61214
Merged
lockewritesdocs merged 2 commits intoelastic:masterfrom Aug 17, 2020
Merged
[DOCS] Update info about geo_shape bounding boxes#61214lockewritesdocs merged 2 commits intoelastic:masterfrom
lockewritesdocs merged 2 commits intoelastic:masterfrom
Conversation
Collaborator
|
Pinging @elastic/es-docs (>docs) |
Collaborator
|
Pinging @elastic/es-analytics-geo (:Analytics/Geo) |
thomasneirynck
approved these changes
Aug 17, 2020
Contributor
thomasneirynck
left a comment
There was a problem hiding this comment.
thanks 💯 @lockewritesdocs !
|
|
||
| If <<geo-bounds-wrap-longitude,`wrap_longitude`>> is set to `true` | ||
| (the default), the bounding box can overlap the international date line. If | ||
| these shapes also include `geo_shape` fields, the `geo_bounds` aggregation |
Contributor
There was a problem hiding this comment.
I think this behavior applies equally to just points, so I think we can remove this if.
e.g.:
If <<geo-bounds-wrap-longitude,`wrap_longitude`>> is set to `true`
(the default), the bounding box can overlap the international date line and returns a bounds where the `top_left` longitude is larger than the `top_right` longitude.
lockewritesdocs
pushed a commit
to lockewritesdocs/elasticsearch
that referenced
this pull request
Aug 17, 2020
* Adding information about geo_shape bounding boxes. * Fixing cross link and incorporating review feedback.
lockewritesdocs
pushed a commit
to lockewritesdocs/elasticsearch
that referenced
this pull request
Aug 17, 2020
* Adding information about geo_shape bounding boxes. * Fixing cross link and incorporating review feedback.
lockewritesdocs
pushed a commit
to lockewritesdocs/elasticsearch
that referenced
this pull request
Aug 17, 2020
* Adding information about geo_shape bounding boxes. * Fixing cross link and incorporating review feedback.
lockewritesdocs
pushed a commit
that referenced
this pull request
Aug 17, 2020
lockewritesdocs
pushed a commit
that referenced
this pull request
Aug 17, 2020
lockewritesdocs
pushed a commit
that referenced
this pull request
Aug 17, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Per #55812, this PR adds clarifications around the
geo_boundsaggregation where thetop_leftarea of the bounding box can exceed thetop_right.Closes #55812
Backports: