Geometry error message improvement

[jhnwllr]

(from GBIF helpdesk)

Just quickly, as it is the weekend, I think you need to check your
geometry. I see

MULTIPOLYGON (((3.9824 51.8131, 4.9905 51.8131, 4.9905 52.5711,
3.9824 52.5711, 3.9824 51.8131)), ((4.2092 51.8228, 5.1048 51.8228,
5.1048 52.4541, 4.2092 52.4541, 4.2092 51.8228)))

which gives an error, as it intersects. You can try drawing it on
https://arthur-e.github.io/Wicket/ for example.

I'll check with the developer for RGBIF whether we can improve the error
messages for this.

[MattBlissett]

Note the API does give an error message:

curl -i --user ********:******** -H "Content-Type: application/json" -X POST --data '{"format":"SIMPLE_CSV","predicate":{"type":"within","geometry":"MULTIPOLYGON (((3.9824 51.8131, 4.9905 51.8131, 4.9905 52.5711, 3.9824 52.5711, 3.9824 51.8131)), ((4.2092 51.8228, 5.1048 51.8228, 5.1048 52.4541, 4.2092 52.4541, 4.2092 51.8228)))"}}' 'https://api.gbif-uat.org/v1/occurrence/download/request'
HTTP/2 400
content-type: text/plain
...

Invalid geometry: Self-intersection at or near point (4.9905, 52.4541, NaN)

The content type is text/plain which matches the response type, but I'm willing to change the response to JSON if that makes things easier, i.e.

HTTP/2 400
content-type: application/json
...

"Invalid geometry: Self-intersection at or near point (4.9905, 52.4541, NaN)"