Coordinates not included – 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 Elasticsearch is trying to index or search geospatial data, but the required coordinates are missing or improperly formatted. To resolve this issue, ensure that the data you’re trying to index includes the necessary geospatial coordinates and that they are correctly formatted. Also, check your mapping to ensure it’s correctly set up for geospatial data. If you’re using a pipeline, verify that it’s correctly extracting and formatting the coordinates.

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 ” coordinates not included ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .

Log Context

Log “coordinates not included” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 return new GeometryCollection<>(geometries);
 }  // We expect to have coordinates for all the rest
 if (coordinates == null) {
 throw new ElasticsearchParseException("coordinates not included");
 }  return switch (shapeType) {
 case CIRCLE -> {
 if (radius == null) {


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?

Get expert answers on Elasticsearch/OpenSearch