Couldn t validate latitude longitude values – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when the latitude/longitude values provided in Elasticsearch are outside the valid range. Latitude should be between -90 and 90, and longitude should be between -180 and 180. To resolve this issue, you can validate your data before indexing to ensure it falls within the correct range. Alternatively, you can use a script to clean up the existing data in your index. Another solution could be to use a “lenient” parameter to ignore malformed lat/long values, but this could lead to inaccurate search results.

This guide will help you check for common problems that cause the log ” couldn’t validate latitude/ longitude values ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: query, index.

Log Context

Log “couldn’t validate latitude/ longitude values” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 }  QueryValidationException exception = checkLatLon();
 if (exception != null) {
 throw new QueryShardException(context; "couldn't validate latitude/ longitude values"; exception);
 }  if (GeoValidationMethod.isCoerce(validationMethod)) {
 GeoUtils.normalizePoint(center; true; true);