I have a process that includes the GeometryValidator transformer with a check on for self-intersections in 2D. The validation rightly captures those overlapping or crossing segments, but it also incorrectly catches vertices that snap to another segment. These kinds of geometries can be correct, as in the case of a trail that has a T-intersection and loops back onto itself.
I’ve not found a mechanism to allow these kinds of errors to be considered valid. Does anyone have a work-around?
