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

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 “field must be either lat/lon or geohash” 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: .

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”field must be either lat/lon or geohash”classname  is
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

Find Configuration Errors

Analyze Now