Longitude must be a number – Elasticsearch Error How To Solve Related Issues

Longitude must be a number – 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 “longitude must be a number” 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”longitude must be a number”classname  is GeoPoint.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

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");
  if (vals.length > 2) {
  GeoPoint.assertZValue(ignoreZValue; Double.parseDouble(vals[2].trim()));
  return reset(lat; lon);


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 elasticsearch mapping of geo_point with null_value -views 2,085 ,score 2

Error on inserting geo_point in elasticsearch through java -views   483



About Opster

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

Find Configuration Errors

Analyze Now