Wrong error in case of given boundary polygon with invalid coordinates

[bonaparten]

Bug Description

The ohsome API returns an Internal Server Error and HTTP status code 500 in almost all cases of wrong given bpolys value (except for boundaries lying outside the underlying data-extract polygon).
The first tested request has obvious wrong coordinates with non-noded linestrings intersection. The response has the following message: found non-noded intersection between LINESTRING ( 8.422694 49.47198, 8.426363 49.473583 ) and LINESTRING ( 8.426373 49.473593, 8.422684 49.47191 ) [ (8.42608150325082, 49.47346001300383, NaN) ]

The second tested request has only one coordinates pair. The response has the following message: Invalid number of points in LineString (found 1 - must be 0 or >= 2)

Expected Behaviour

In both cases, the thrown exception should be caught and a BadRequestException should be thrown. The ohsome API should return a 400 status code with an appropriate message.

General Information

• Version of the ohsome API: 1.5.0
• API requested :https://api.ohsome.org/v1, local instance with an h2 file and connected to the cluster
• Affected endpoint(s): tested on /elements/count but probably all
• URL of your request: request1, request2
• Used HTTP method: GET
• Utilized tool/library for the request: cURL, Swagger