Exception parsing coordinates: – Elasticsearch Error How To Solve Related Issues

Exception parsing coordinates: – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch 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 causing many errors 


This guide will help you check for common problems that cause the log “Exception parsing coordinates:” 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: .

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 discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

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) {


Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 ElasticSearch Mapper Parsing Exception while insertion of data -views 444 

Elasticsearch search parse exception but return a result -views   395



About Opster

Opster detects, prevents, optimizes and automates everything needed to run mission-critical Elasticsearch

Find Configuration Errors

Analyze Now