Coordinates cannot be specified as objects – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when the format of the coordinates provided in a geo-point field is incorrect. Elasticsearch expects coordinates to be specified as an array or a string, not as objects. To resolve this issue, you can either provide the coordinates as a string in the format “lat,lon” or as an array in the format [lon,lat]. Ensure that the longitude comes first in the array format. Also, check your mapping to ensure the field is correctly set as a geo-point type.

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

Log Context

Log “coordinates cannot be specified as objects” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 private static CoordinateNode parseCoordinates(XContentParser parser; boolean ignoreZValue) throws IOException {
 if (parser.currentToken() == XContentParser.Token.START_OBJECT) {
 throw new ElasticsearchParseException("coordinates cannot be specified as objects");
 }  XContentParser.Token token = parser.nextToken();
 // Base cases
 if (token != XContentParser.Token.START_ARRAY


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?