The validateBoundingBox method fails with values having more than 5 decimal places.

What steps does it take to reproduce the issue?

Create a Dataset with a Geographic Bounding Box field.

Enter coordinates with more than 5 decimal places - for example, set South greather than North or West greather than East using 6 decimal places.

• When does this issue occur?

Geographic Bounding Box validation.

• Which page(s) does it occurs on?

Create/Edit Dataset

• What happens?

When a user creates a Geographic Bounding Box field and enters values with more than 5 decimal places, the validation is not correct. Dataverse saves the Dataset, but Solr cannot index the item and throws an exception.

• To whom does it occur (all users, curators, superusers)?

All users

• What did you expect to happen?

Dataverse thows error message: "Geographic Bounding Box has invalid coordinates. East must be greater than West and North must be greater than South. Missing values are NOT allowed."

Which version of Dataverse are you using?

First observed in version 6.4, and it still occurs in 6.6.

Any related open or closed issues to this bug report?

No

Screenshots:

No matter the issue, screenshots are always welcome.

To add a screenshot, please use one of the following formats and/or methods described here:

Are you thinking about creating a pull request for this issue?
Help is always welcome, is this bug something you or your organization plan to fix?

Yes.

The method verifyBoundingBoxCoordinatesWithinRange should compare BigDecimal values instead of Float for greater precision. This does not affect performance if used only to validate coordinates.