Coordinates not included – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

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.

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?