Supports only POINT among WKT primitives – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.8-7.15

Briefly, this error occurs when Elasticsearch tries to process a Well-Known Text (WKT) shape other than a POINT. Elasticsearch supports only POINT WKT primitives for certain operations. To resolve this issue, you can either convert your WKT shape to a POINT or use a different method that supports your specific WKT shape. Alternatively, you can use a GeoJSON object, which has broader support for different shape types in Elasticsearch.

This guide will help you check for common problems that cause the log ” [{}] supports only POINT among WKT primitives; ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “[{}] supports only POINT among WKT primitives;” class name is CartesianPoint.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 geometry = WellKnownText.fromWKT(StandardValidator.instance(ignoreZValue); false; value);
 } catch (Exception e) {
 throw new ElasticsearchParseException("Invalid WKT format"; e);
 }
 if (geometry.type() != ShapeType.POINT) {
 throw new ElasticsearchParseException("[{}] supports only POINT among WKT primitives; " +
 "but found {}"; PointFieldMapper.CONTENT_TYPE; geometry.type());
 }
 org.elasticsearch.geometry.Point point = (org.elasticsearch.geometry.Point) geometry;
 return reset(point.getX(); point.getY());
 }

 

 [ratemypost]

Opster
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.