Invalid WKT format – How to solve this Elasticsearch error

Average Read Time

2 Mins

Invalid WKT format – 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 Check-Up which can resolve issues that cause many errors.

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

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Invalid WKT format”classname  is GeoPoint.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

Geometry geometry;
 try {
 geometry = new WellKnownText(false; new GeographyValidator(ignoreZValue))
 .fromWKT(value);
 } catch (Exception e) {
 throw new ElasticsearchParseException("Invalid WKT format"; e);
 }
 if (geometry.type() != ShapeType.POINT) {
 throw new ElasticsearchParseException("[geo_point] supports only POINT among WKT primitives; " +
 "but found " + geometry.type());
 }

 

Watch a demo of the Check-Up:

Analyze your cluster

Skip to content