You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, it seems that you managed to simplify your Antarctica outline to one that Elasticsearch does accept in #39, even though it still looks to be oriented clockwise. It's possible that the shape that Elasticsearch has indexed is not the shape you asked for, because of the code linked in elastic/elasticsearch#27832 (comment).
I'd recommend fixing the mapping, or reversing the orientation of the Antarctica outline to make it anticlockwise as per the GeoJSON spec, to make sure that Elasticsearch indexes it correctly. If you do so, it looks like you can revert #39 and use the original higher-precision outline (suitably reversed). Meanwhile we're looking at this leniency in more detail in elastic/elasticsearch#27832.
The text was updated successfully, but these errors were encountered:
I was recently looking into issue #3 from the Elasticsearch side, along with the related issues elastic/elasticsearch#27832 and elastic/elasticsearch#17407.
elastic/elasticsearch#17407 (comment) also applies to your issue, as does the fix (setting
"orientation": "clockwise"
in the mapping).However, it seems that you managed to simplify your Antarctica outline to one that Elasticsearch does accept in #39, even though it still looks to be oriented clockwise. It's possible that the shape that Elasticsearch has indexed is not the shape you asked for, because of the code linked in elastic/elasticsearch#27832 (comment).
I'd recommend fixing the mapping, or reversing the orientation of the Antarctica outline to make it anticlockwise as per the GeoJSON spec, to make sure that Elasticsearch indexes it correctly. If you do so, it looks like you can revert #39 and use the original higher-precision outline (suitably reversed). Meanwhile we're looking at this leniency in more detail in elastic/elasticsearch#27832.
The text was updated successfully, but these errors were encountered: