-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Shape field type cannot handle polygons with high precision coordinates #78499
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
Comments
Pinging @elastic/es-analytics-geo (Team:Analytics) |
@filipski can you include the command you used to index the polygon? |
The call is made with help of: |
Is that enough to get you going? |
Yes, it reproduces in master:
the error:
|
Just to set the right expectations, this error is expected as the provided polygon self-intersects on the float space and this index works on that space. When I asked you to open an issue was not for making this polygon indexable but for improving the error message which is not very helpful at the moment. |
The error message should be more clear now and there is nothing to here as shape type works on the float space. |
The bug is an outcome of https://discuss.elastic.co/t/coordinates-precision/285434
Elasticsearch version (
bin/elasticsearch --version
): 7.12.1OS version (
uname -a
if on a Unix-like system): Linux 5.4.0-86-generic #97~18.04.1-Ubuntu SMP Sat Sep 18 03:11:22 UTC 2021 x86_64 x86_64 x86_64 GNU/LinuxDescription of the problem including expected versus actual behavior:
Steps to reproduce:
Provide logs (if relevant):
Intersections introduced by rounding:
while original values of coordinates of those segments are:
The text was updated successfully, but these errors were encountered: