Failed to parse bounding box Conflicting definition found – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Briefly, this error occurs when there is a conflict in the definition of the bounding box in Elasticsearch. This could be due to incorrect or inconsistent coordinates provided for the bounding box. To resolve this issue, you should first verify the coordinates provided for the bounding box. Ensure that the coordinates are correct and consistent. If the error persists, check the format of the bounding box definition. It should be in the correct format as expected by Elasticsearch. Lastly, ensure that the bounding box definition does not conflict with any other definitions in your Elasticsearch query.

This guide will help you check for common problems that cause the log ” failed to parse bounding box. Conflicting definition found ” 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 bounding box. Conflicting definition found” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (envelope != null) {
 if (Double.isNaN(top) == false || Double.isNaN(bottom) == false || Double.isNaN(left) == false ||
 Double.isNaN(right) == false) {
 throw new ElasticsearchParseException("failed to parse bounding box. Conflicting definition found "
 + "using well-known text and explicit corners.");
 GeoPoint topLeft = new GeoPoint(envelope.getMaxLat(); envelope.getMinLon());
 GeoPoint bottomRight = new GeoPoint(envelope.getMinLat(); envelope.getMaxLon());
 return new GeoBoundingBox(topLeft; bottomRight);


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?