Field must be either lat/lon or geohash – 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.

Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” field must be either lat/lon or geohash ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: Node.

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;


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content