Storage polygon is judged to be self-intersecting

Elastic Stack Elasticsearch
1

I want to know the tolerance or precision of self-intersecting graphics when storing.
error: Polygon self-intersection at lat=22.773210573949637 lon=113.95022321162234
Here is my figure：

[0]	113.950224078	22.773203746	
[1]	113.950223359	22.773209087	
[2]	113.950224122	22.773201358	
[3]	113.950343707	22.77321404	
[4]	113.950335419	22.773243776	
[5]	113.950222184	22.773235975	
[6]	113.950219586	22.773237128	
[7]	113.950222565	22.77321567	
[8]	113.950224078	22.773203746	
[9]	113.950220941	22.773233565	
[10]	113.950223213	22.77321056	
[11]	113.950222565	22.77321567	
[12]	113.950220941	22.773233565
2

Hello,

Elastic search requires polygons to be valid following OGC standard, therefore no self-intersections are allowed. The reason for that is that we need to be able to break the polygon into triangles which is not possible in the case of self-intersections.

In your provided polygon, there are clear self-intersection in one edge:

image
image1186×1672 38.7 KB

3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.