GIScience/ohsome-api

Parameter types2 is invalid, but a successful response is obtained

apibugsreporting opened this issue · 0 comments

Bug Description

According to the Ohsome documentation, the types (or types2) parameter "allows to specify OSM type(s) ‘node’ and/or ‘way’ and/or ‘relation’ OR simple feature type(s) ‘point’ and/or ‘line’ and/or ‘polygon’ and/or ‘other’". In the following request, the types2 parameter uses an invalid value ("P5:8'gH@-td!<]JP}"), but a successful response is obtained. Is this the expected behavior?

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]
    • /elements/perimeter/ratio
  • URL of your request (and request body if applicable)
    • https://api.ohsome.org/v1/elements/perimeter/ratio?filter=destination%21%3D*%20and%20type%3Anode%20or%20not%20length%3A%28%20..%20100%29&bboxes=gaIZM%3A8.650%2C49.417%2C8.72388%2C49.3979&types2=%20P5%3A8%27gH%40-td%21%3C%5DJP%7D&filter2=highway%20in%20%28secondary%2Cpath%2Cunclassified%2Ctrack%2Cprimary%2Cresidential%2Ccycleway%2Cservice%2Cfootway%29%20or%20id%3A%281%20..%209999%29&timeout=29
  • Used HTTP method [GET or POST]
    • Both
  • Utilized tool/library for the request [e.g. cURL, Postman, ohsome-py, etc.]

Expected Behaviour

The API should return a 400 status code, since the request is invalid.

Further Information

Additional Information

A test report revealing this issue is available at the following URL (it might take some time to load):