Invalid LinearRing found coordinates are not closed – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when the coordinates provided for a geo_shape in Elasticsearch are not forming a closed loop, which is a requirement for LinearRing. To resolve this issue, ensure that the first and last points of your coordinates are the same, thus forming a closed shape. Also, check that your coordinates have at least four points, as a valid LinearRing must have at least four coordinates.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” invalid LinearRing found (coordinates are not closed) ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .

Log Context

Log “invalid LinearRing found (coordinates are not closed)” class name is GeoShapeType.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 coordinates.children.get(coordinates.children.size() - 1).coordinate
 ) == false) {
 if (coerce) {
 coordinates.children.add(coordinates.children.get(0));
 } else {
 throw new ElasticsearchParseException("invalid LinearRing found (coordinates are not closed)");
 }
 }
 }  @Override

 

How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?