Geo coordinates greater than 3 dimensions are not supported – 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 you try to index a geo-point field in Elasticsearch with more than 3 dimensions (latitude, longitude, and altitude). Elasticsearch only supports up to 3 dimensions for geo-point fields. To resolve this issue, you can either reduce the dimensions of your geo-point data to 3 or less, or split the extra dimensions into separate fields. If the extra dimensions are not necessary, you can simply ignore them during indexing.

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 ” geo coordinates greater than 3 dimensions are not supported ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .

Log Context

Log “geo coordinates greater than 3 dimensions are not supported” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 alt = parser.doubleValue();
 // do not support > 3 dimensions
 if (parser.currentToken() == XContentParser.Token.VALUE_NUMBER) {
 throw new ElasticsearchParseException("geo coordinates greater than 3 dimensions are not supported");
 return new Point(lon; lat; alt);
 }  /**


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?