-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Geo: inconsistent handling of out of bounds coordinates in different geo shapes #43916
Labels
:Analytics/Geo
Indexing, search aggregations of geo points and shapes
>bug
Team:Analytics
Meta label for analytical engine team (ESQL/Aggs/Geo)
Comments
imotov
added
>bug
:Analytics/Geo
Indexing, search aggregations of geo points and shapes
labels
Jul 3, 2019
Pinging @elastic/es-analytics-geo |
I'd like to take this. |
@Hohol I am currently refactoring this code as part of #40908 so making this change now doesn't make much sense. Ping me by email or by PM on https://discuss.elastic.co/ and we can find something else to work on that matches your interest. |
imotov
added a commit
to imotov/elasticsearch
that referenced
this issue
Oct 8, 2019
This is the first iteration in improving of handling of out of bounds geopoints with a latitude outside of the -90 - +90 range and a longitude outside of the -180 - +180 range. Relates to elastic#43916
imotov
added a commit
that referenced
this issue
Oct 9, 2019
This is the first iteration in improving of handling of out of bounds geopoints with a latitude outside of the -90 - +90 range and a longitude outside of the -180 - +180 range. Relates to #43916
imotov
added a commit
that referenced
this issue
Oct 9, 2019
This is the first iteration in improving of handling of out of bounds geopoints with a latitude outside of the -90 - +90 range and a longitude outside of the -180 - +180 range. Relates to #43916
imotov
added a commit
to imotov/elasticsearch
that referenced
this issue
Oct 11, 2019
Brings handling of out of bounds points in linestrings in line with points. Now points with latitude above 90 and below -90 are handled the same way as for points by adjusting the longitude by moving it by 180 degrees. Relates to elastic#43916
imotov
added a commit
that referenced
this issue
Oct 23, 2019
Brings handling of out of bounds points in linestrings in line with points. Now points with latitude above 90 and below -90 are handled the same way as for points by adjusting the longitude by moving it by 180 degrees. Relates to #43916
imotov
added a commit
that referenced
this issue
Oct 23, 2019
Brings handling of out of bounds points in linestrings in line with points. Now points with latitude above 90 and below -90 are handled the same way as for points by adjusting the longitude by moving it by 180 degrees. Relates to #43916
This was referenced Feb 3, 2020
rjernst
added
the
Team:Analytics
Meta label for analytical engine team (ESQL/Aggs/Geo)
label
May 4, 2020
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
>bug
Team:Analytics
Meta label for analytical engine team (ESQL/Aggs/Geo)
We allow out of bounds coordinates in linestrings and polygons, but not in points. In the following example the indexing of LINESTRING succeeds but the indexing of MULTIPOINT with the same set of coordinates fails.
The text was updated successfully, but these errors were encountered: