Testing showed overlaps that were degenerating (due to a bug or entirely plausible due to edge length tolerancing) to 2 or less vertices were triggering an error in a vertex reordering routine. To solve this:
Guard the call to the vertex ordering routine and a few other lines of code with conditional for non-degenerate overlaps
It is ok to have a degenerate overlap in many cases so this should never have triggered an error
Use a debug log statement in the vertex ordering routine in case it is every called with <3 vertices in the polygon.
Testing showed overlaps that were degenerating (due to a bug or entirely plausible due to edge length tolerancing) to 2 or less vertices were triggering an error in a vertex reordering routine. To solve this: