Longitude must be a number – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when the value provided for longitude in a geolocation query is not a number. Elasticsearch expects longitude and latitude values to be numeric for geospatial queries. To resolve this issue, ensure that the longitude value is a valid number. If the value is being sourced from user input or an external system, validate the data before sending it to Elasticsearch. If the error persists, check for any mapping issues in your Elasticsearch index, as the field might be incorrectly mapped as a non-numeric type.

This guide will help you check for common problems that cause the log ” longitude must be a number ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .

Log Context

Log “longitude must be a number” class name is GeoPoint.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 throw new ElasticsearchParseException("latitude must be a number");
 try {
 lon = Double.parseDouble(vals[1].trim());
 } catch (NumberFormatException ex) {
 throw new ElasticsearchParseException("longitude must be a number");
 if (vals.length > 2) {
 GeoPoint.assertZValue(ignoreZValue; Double.parseDouble(vals[2].trim()));
 return reset(lat; lon);


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?