Couldn’t validate latitude/ longitude values – Elasticsearch Error How To Solve Related Issues


Couldn’t validate latitude/ longitude values – Elasticsearch Error How To Solve Related Issues

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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” couldn’t validate latitude/ longitude values ” 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 and 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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

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

throw new QueryShardException(shardContext; "field [" + fieldName + "] is not a geo_point field");
  }
 
  QueryValidationException exception = checkLatLon();
  if (exception != null) {
  throw new QueryShardException(shardContext; "couldn't validate latitude/ longitude values"; exception);
  }
 
  if (GeoValidationMethod.isCoerce(validationMethod)) {
  GeoUtils.normalizePoint(center; true; true);
  }

 

Optimize Elasticsearch Performance

Try The Tool