Exception parsing coordinates: – 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 analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Exception parsing coordinates: ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: Node.

Log Context

Log “Exception parsing coordinates:”classname  is GeoJsonParser.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 } else if (ShapeParser.FIELD_COORDINATES.match(fieldName; subParser.getDeprecationHandler())) {
 CoordinateNode tempNode = parseCoordinates(subParser; ignoreZValue.value());
 if (coordinateNode != null && tempNode.numDimensions() != coordinateNode.numDimensions()) {
 throw new ElasticsearchParseException("Exception parsing coordinates: " +
 "number of dimensions do not match");
 coordinateNode = tempNode;
 } else if (ShapeParser.FIELD_GEOMETRIES.match(fieldName; subParser.getDeprecationHandler())) {
 if (shapeType == null) {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content