Single coordinate found when expecting an array of – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Briefly, this error occurs when Elasticsearch expects an array of coordinates for geospatial data, but only receives a single coordinate. This usually happens when indexing geospatial data. To resolve this, ensure that your geospatial data is correctly formatted as an array of coordinates. If you’re using a mapping, verify that it’s correctly set up for geospatial data. Also, check your data source to ensure it’s providing the correct geospatial data format.

This guide will help you check for common problems that cause the log ” single coordinate found when expecting an array of ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .

Log Context

Log “single coordinate found when expecting an array of” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 CoordinateNode validate(CoordinateNode coordinates; boolean coerce) {
 if (coordinates.children == null || coordinates.children.isEmpty()) {
 if (coordinates.coordinate != null) {
 throw new ElasticsearchParseException("single coordinate found when expecting an array of " +
 "coordinates. change type to point or change data to an array of >0 coordinates");
 throw new ElasticsearchParseException("no data provided for multipoint object when expecting " +
 ">0 points (e.g.; [[lat; lng]] or [[lat; lng]; ...])");
 } else {


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?