Geo coordinates must be numbers – Elasticsearch Error How To Solve Related Issues



Geo coordinates must be numbers – 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 “geo coordinates must be numbers” 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”geo coordinates must be numbers”classname  is GeoJson.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

* Parser a singe set of 2 or 3 coordinates
  */
  private static Point parseCoordinate(XContentParser parser) throws IOException {
  // Add support for coerce here
  if (parser.currentToken() != XContentParser.Token.VALUE_NUMBER) {
  throw new ElasticsearchParseException("geo coordinates must be numbers");
  }
  double lon = parser.doubleValue();
  if (parser.nextToken() != XContentParser.Token.VALUE_NUMBER) {
  throw new ElasticsearchParseException("geo coordinates must be numbers");
  }

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

Cant Insert Geo Shapes into elasticsearch -views   672



Find Configuration Errors

Analyze Now