Skip to main content
  • EN

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?

Hi @ragjr There’s no way to work around this as a line that closes on itself (where the first and last vertices are not identical) is indeed self-intersecting. However, I think that these lines could be identified after the GeometryValidator (if no repair is attempted) by comparing the coordinates of the first and last vertices against the issue location, e.g.:

 

@DanAtSafe Thanks for the reply. That seems to provide a work around to this issue in testing.

Reply


Community Stats

30,352
Posts
115,344
Replies
38,086
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.