Field must be either lat/lon or geohash – Elasticsearch Error How To Solve Related Issues

Field must be either lat/lon or geohash – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch Version: 1.7-8.0

This guide will help you check for common problems that cause the error message”field must be either lat/lon or geohash”. To understand what might cause it to appear, read bellow frequent issues related to the Elasticsearch concepts: .

Advanced users might want to skip right to trying out the Elasticsearch Error Check-Up, which analyses ES to discover the cause of many errors to provide actionable recommendations (JSON based, no fee and just 2 minutes to complete).

Log Context

Log”field must be either lat/lon or geohash”classname  is GeoUtils.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

}
  }
  }
  if (geohash != null) {
  if(!Double.isNaN(lat) || !Double.isNaN(lon)) {
  throw new ElasticsearchParseException("field must be either lat/lon or geohash");
  } else {
  return point.parseGeoHash(geohash; effectivePoint);
  }
  } else if (numberFormatException != null) {
  throw new ElasticsearchParseException("[{}] and [{}] must be valid double values"; numberFormatException; LATITUDE;

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 How to use geo_point with geohash in Elasticsearch with a Java class? -views 10,982 ,score 5

Bulk(helpers) Indexing Error in Elastic search Python -views   6,573,score 1

 

 

About Opster

Opster detects, prevents, optimizes and automates everything needed to run mission-critical Elasticsearch

Find Configuration Errors

Analyze Now