Expected geometry type but found – 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 Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

Take a self-guided product tour to see for yourself (no registration required).

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

Log Context

Log “Expected geometry type [{}] but found [{}]”classname  is GeoWKTParser.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

final boolean coerce)
 throws IOException; ElasticsearchParseException {
 final GeoShapeType type = GeoShapeType.forName(nextWord(stream));
 if (shapeType != null && shapeType != GeoShapeType.GEOMETRYCOLLECTION) {
 if (type.wktName().equals(shapeType.wktName()) == false) {
 throw new ElasticsearchParseException("Expected geometry type [{}] but found [{}]"; shapeType; type);
 switch (type) {
 case POINT:
 return parsePoint(stream; ignoreZValue; coerce);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content