Illegal latitude value for – Elasticsearch Error How To Solve Related Issues

Illegal latitude value for – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many errors 


This guide will help you check for common problems that cause the log “illegal latitude value for” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: query, index.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

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();

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 elasticsearch rails – illegal latitude value -views 3,312 ,score 2

illegal latitude value for [GeoDistanceSort] in Elasticsearch -views   289

Find Configuration Errors

Analyze Now