Field ” + fieldName + ” is not a geo_point field – Elasticsearch Error How To Solve Related Issues

Field ” + fieldName + ” is not a geo_point field – 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 ” + fieldName + ” is not a geo_point field” 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: query, index.

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 [” + fieldName + “] is not a geo_point field”classname  is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

throw new QueryShardException(shardContext; "failed to find geo_point field [" + fieldName + "]");
  if (!(fieldType instanceof GeoPointFieldType)) {
  throw new QueryShardException(shardContext; "field [" + fieldName + "] is not a geo_point field");
  QueryValidationException exception = checkLatLon();
  if (exception != null) {
  throw new QueryShardException(shardContext; "couldn't validate latitude/ longitude values"; exception);

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 QueryParsingException failed to find geo_point field -views 11,503 ,score 6

Elasticsearch "failed to find geo_point field [location]" when the mapping is there for that field -views   2,552,score 2

Find Configuration Errors

Analyze Now