GIScience/ohsome-api

Internal Server Error (500 status code) with message "found non-noded intersection [...]"

apibugsreporting opened this issue · 0 comments

apibugsreporting commented

Bug Description

I found several requests obtaining 500 status codes with the error message "found non-noded intersection between LINESTRING XXX and LINESTRING YYY"

General Information

Please include the following general information about the issue and list any additional steps needed to reproduce the bug.

  • Version of the ohsome API [e.g. 1.5.0]
    • 1.6.1
  • Which API instance was requested [e.g. remote instance at https://api.ohsome.org/v1, local instance with an h2 file or connected to the cluster, etc.]
    • Remote instance at https://api.ohsome.org/v1
  • Affected endpoint(s) [e.g. /contributions/count]
    • All (or many) endpoints seem to be affected
  • URL of your request (and request body if applicable)
    • https://api.ohsome.org/v1/elements/count/groupBy/boundary?types=point%2Cline%2C&keys=highway&format=json&showMetadata=false&time=2014-10-28&bpolys=%7B%22type%22%3A%22FeatureCollection%22%2C%22features%22%3A%5B%7B%22type%22%3A%22Feature%22%2C%22properties%22%3A%7B%22id%22%3A%22XIFZ%22%7D%2C%22geometry%22%3A%7B%22type%22%3A%22Polygon%22%2C%22coordinates%22%3A%5B%5B%5B8.704561%2C49.403252%5D%2C%5B8.720%2C49.4351%5D%2C%5B8.704580%2C49.429%5D%2C%5B8.739%2C49.400%5D%2C%5B8.704561%2C49.403252%5D%5D%5D%7D%7D%2C%7B%22type%22%3A%22Feature%22%2C%22properties%22%3A%7B%22id%22%3A%22bzLuQ%22%7D%2C%22geometry%22%3A%7B%22type%22%3A%22Polygon%22%2C%22coordinates%22%3A%5B%5B%5B8.704561%2C49.403252%5D%2C%5B8.731%2C49.429%5D%2C%5B8.7196%2C49.411%5D%2C%5B8.720%2C49.4246%5D%2C%5B8.704561%2C49.403252%5D%5D%5D%7D%7D%5D%7D&timeout=98
  • Used HTTP method [GET or POST]
    • Both
  • Utilized tool/library for the request [e.g. cURL, Postman, ohsome-py, etc.]

Expected Behaviour

A 500 status code (Internal Server Error) should not be returned. There is probably some uncaught exception in the code.

Further Information

Additional Information

Several test reports revealing this issue are available at the following URLs (they might take some time to load):