Exception parsing coordinates found Z value but – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.1

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 Elasticsearch encounters a Z value in the coordinates while parsing geo-points. Elasticsearch only supports 2D geo-points (latitude and longitude), and the Z value represents the third dimension (altitude), which is not supported. To resolve this issue, you can either remove the Z value from your geo-point data before indexing or use a script to strip the Z value during the indexing process. Alternatively, you can use a mapping to ignore malformed geo-points.

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 ” Exception parsing coordinates: found Z value [{}] but [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .

Log Context

Log “Exception parsing coordinates: found Z value [{}] but [{}]” class name is GeoPoint.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 return builder.latlon(lat; lon);
 }  public static double assertZValue(final boolean ignoreZValue; double zValue) {
 if (ignoreZValue == false) {
 throw new ElasticsearchParseException("Exception parsing coordinates: found Z value [{}] but [{}] "
 + "parameter is [{}]"; zValue; IGNORE_Z_VALUE; ignoreZValue);
 }
 return zValue;
 }
}

 

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?