Expected a single points but got a list – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.2-8.9

Briefly, this error occurs when Elasticsearch expects a single point for geospatial data but receives a list instead. This could be due to incorrect formatting of the input data. To resolve this, ensure that your geospatial data is correctly formatted as a single point, not a list. If you’re using an array, make sure it contains only two elements (longitude and latitude). Also, check your mapping to ensure the field is correctly set as a geo_point type. If the error persists, consider reindexing your data with the correct format.

This guide will help you check for common problems that cause the log ” expected a single points but got a list ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .

Log Context

Log “expected a single points but got a list” class name is GeoJson.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 return children.get(0).numDimensions();
 }  public Point asPoint() {
 if (children != null) {
 throw new ElasticsearchException("expected a single points but got a list");
 return coordinate;
 }  public MultiPoint asMultiPoint() {


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?