Exchange silently fails when I try to use an invalid polygon in a spatial filter on a layer backed by SQL Server. The particular invalid polygon used was one where the sides cross themselves. Please see attached example.
At the very least I would like to see the error from GeoServer. It would be great if it could run a validation on the geometry and proactively let the user know that the geometry is invalid. It would also be great if it could attempt to automatically fix the polygon and let the user verify that the fixed polygon is still correct.
This scenario could also arise while drawing and modifying geometries. Similar warnings/errors and corrections should be used for those tools too.