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

add EdgeTree support for lines/multilines #43949

Merged
merged 4 commits into from
Jul 9, 2019

Conversation

talevy
Copy link
Contributor

@talevy talevy commented Jul 3, 2019

The main change here is that edge-trees originally
checked whether the queried extent could be contained
within its shape. Since line-strings have no inner boundaries,
this check is not useful, the line crosses check + extent-check-bounds
is sufficient.

The main change here is that edge-trees originally
checked whether the queried extent could be contained
within its shape. Since line-strings have no inner boundaries,
this check is not useful, the line crosses check + extent-check-bounds
is sufficient.
@talevy talevy added WIP :Analytics/Geo Indexing, search aggregations of geo points and shapes labels Jul 3, 2019
@talevy talevy requested a review from imotov July 3, 2019 22:55
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-analytics-geo

Copy link
Contributor

@imotov imotov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. The name closed confused me a bit, since we are using it in the context of shapes for a slightly different purpose. I think in this context we want to indicate dimension. closed == true means we are dealing with area or 2 dimensional shapes and closed == false means that we are dealing with 1 dimensional shapes.

better define the difference between edge-trees representing
polygons vs. line-strings. Polygons have non-zero areas.

Also added tests for shapeType and closed line-strings.
@talevy talevy marked this pull request as ready for review July 8, 2019 18:52
@talevy talevy removed the WIP label Jul 8, 2019
@talevy
Copy link
Contributor Author

talevy commented Jul 9, 2019

test this please

@talevy talevy requested a review from imotov July 9, 2019 02:44
Copy link
Contributor

@imotov imotov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks!

@talevy talevy merged commit 74c3f5d into elastic:geoshape-doc-values Jul 9, 2019
@talevy talevy deleted the gdv-line branch July 9, 2019 19:43
talevy added a commit that referenced this pull request Sep 20, 2019
The main change here is that edge-trees originally
checked whether the queried extent could be contained
within its shape. Since line-strings have no inner boundaries,
this check is not useful, the line crosses check + extent-check-bounds
is sufficient.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Analytics/Geo Indexing, search aggregations of geo points and shapes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants