-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a new layer fails with Numeric Overflow exception #247
Comments
Seem to have pinpointed where the number conversion fails. The values in that map are strings, calling the setter on the Grails Entity converts them to number that are considering the locale, set in the front-end. Causing 5.911109415203301 to become 5.911109415203301E15. |
… prevent issues with number formatting when adding layers. AtlasOfLivingAustralia#247
Created a proposal for a simple workaround: It was getting very frustrating, making sure we always had the correct language selected when administering the layers. |
Creating a new layer sometimes fails with the following error:
This is caused by incorrect parsing of the floating point numbers of the bounding box returned by geoserver.
It only happens when setting the language to in our case nl_BE.
This causes the grails i18n to change the number format locale to use a different decimal separator.
A value of
5.911109415203301
therefor becomes5.068749233044934E15
, causing an overflow.Looking at a way to properly parse the bounding box values without being affected by the users locale.
Will create a PR to fix, current workaround is just to make sure we switch to English.
The text was updated successfully, but these errors were encountered: