In 2016, the geoJSON specification became more strict and many old geoJSONs will not work in new tools like Mapbox, or throw errors. GeoJSONLint has not updated and many of its polygons are broken. It’s important to “rewind" your geoJSONs so that they fit with this more tight format.
So I check and effectivly my polygon is of the wrong orientation, but if instead of 539 points, I reduce it to 200, now the polygon index with success.
What I would like to know is ES have a policy of indexation that for polygon that get more complex, more then 200 points, it needs to align with the specs for successfull indexation?
No, there is no such rule. However if you're simplifying your polygon by removing points then you may also be correcting it, perhaps by removing a self-intersection. If you share the shape here we should be able to tell you more precisely what's happening.
Looking at my points, I figured that I can delete either one of the three and the indexation passed. Since the 3 of them are on the same longitude and very close on latitude is there a rule for that on the creation of a geoshape???
No, there's no rule like this. But there is a rule against self-intersecting shapes, and this sequence of three points is self-intersecting: they're all on the same longitude and the third point's latitude is between the other two, so the boundary of your shape goes back on itself.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.