Geo_point field type does not accept > 3 dimensions – How to solve this Elasticsearch error

Geo_point field type does not accept > 3 dimensions – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” geo_point field type does not accept > 3 dimensions ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: Node.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log”[geo_point] field type does not accept > 3 dimensions”classname  is GeoUtils.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

} else if (element == 2) {
  lat = subParser.doubleValue();
  } else if (element == 3) {
  GeoPoint.assertZValue(ignoreZValue; subParser.doubleValue());
  } else {
  throw new ElasticsearchParseException("[geo_point] field type does not accept > 3 dimensions");
  }
  } else {
  throw new ElasticsearchParseException("numeric value expected");
  }
  }

 

Run the Check-Up to get a customized report like this:

Analyze your cluster