Failed to parse WKT bounding box – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.6-8.9

Briefly, this error occurs when Elasticsearch is unable to parse the Well-Known Text (WKT) representation of a bounding box, which is used for geospatial data. This could be due to incorrect formatting or invalid values. To resolve this issue, ensure that the WKT bounding box is correctly formatted according to the WKT standard. Also, check that the coordinates are valid and within the acceptable range. If the error persists, consider reindexing your data or using a different method to represent your geospatial data.

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

Log Context

Log “failed to parse WKT bounding box” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 + "]"
 envelope = (Rectangle) geometry;
 } catch (ParseException | IllegalArgumentException e) {
 throw new ElasticsearchParseException("failed to parse WKT bounding box"; e);
 } else if (TOP_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {
 top = parser.doubleValue();
 } else if (BOTTOM_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {
 bottom = parser.doubleValue();


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?