Latitude must be a number – 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.

This guide will help you check for common problems that cause the log ” latitude must be a number ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: Node.


Log Context

Log “latitude must be a number”classname  is GeoPoint.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

final double lat;
 final double lon;
 try {
 lat = Double.parseDouble(vals[0].trim());
 } catch (NumberFormatException ex) {
 throw new ElasticsearchParseException("latitude must be a number");
 }
 try {
 lon = Double.parseDouble(vals[1].trim());
 } catch (NumberFormatException ex) {
 throw new ElasticsearchParseException("longitude must be a number");

 

Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content