Illegal latitude value for – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” illegal latitude value for ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: query and index.

Log Context

Log “illegal latitude value [{}] for [{}]”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

// validation was not available prior to 2.x; so to support bwc
 // percolation queries we only ignore_malformed on 2.x created indexes
 if (!GeoValidationMethod.isIgnoreMalformed(validationMethod)) {
 for (GeoPoint point : shell) {
 if (!GeoUtils.isValidLatitude( {
 throw new QueryShardException(context; "illegal latitude value [{}] for [{}]";;
 if (!GeoUtils.isValidLongitude(point.lon())) {
 throw new QueryShardException(context; "illegal longitude value [{}] for [{}]"; point.lon();


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content