Self-intersecting polylines now called out???

Eric,

Yes, that was recently added.
The system now checks the hatch immediately after being placed, and if it has no Area, then it alerts the user as such. We had seen some recent tech support tickets that indicated it is a more widespread problem than we originally thought, so we felt it was worthwhile to alert the user immediately upon placement.

--J

You have to fix this!!!!!! Boundaries that clearly have no intersection are being flagged 90% of the time. Simple shapes are even an issue. If you use a revcloud to create the boundary it flags is almost every time. Maybe there is a better way to get a non linear boundary that I can use.

First of all thank you for addressing it!! We have lost many hours of productivity hunting down where the lines are intersecting. To followup with what Alan mentioned, I agree that it seems to only get it right 90 percent of the time, very close intersections don’t seem to trigger it. I trust that you guys will stay on it to work out the kinks.

Alan King and Eric McNair, can you both please open tickets and send us drawings where this error is either triggering when it shouldn't, or not triggering when it should? Seeing the examples so we can replicate the issue here is the only way we can fix those situations.
How to Submit a Technical Support Ticket

-Amanda