Re: [jts-dev] TopologyException: found non-noded intersection

[Martin Davis <mtnclimb@xxxxxxxxx>]

Inserting the coordinate from the TopologyException is not a general fix.  In general there may be many locations where the topology cannot be determined robustly under the current JTS algorithm.  The location in the exception is just the "first" one.

I'm actually surprised that it fixes this case - just a lucky situation, I think.

On Tue, Mar 29, 2016 at 12:11 AM, Felix Obermaier <obe@xxxxxxxxxxxxx> wrote:

Hello list,

On NTS Google groups came up with two polygons that, when doing a difference operation, threw a TopologyException.
https://groups.google.com/forum/#!topic/nettopologysuite/6YTDe0pMMgI



While using GeometryPrecisionReducer solves the issue, I was wondering whether inserting the topology-exception location coordinate into the input coordinates would solve the problem, too.
So I did a quick proof of concept for the problem at hand and found out it worked.
(https://groups.google.com/group/nettopologysuite/attach/c9b8d04e0ec55/TopologyExceptionCatch.cs?part=0.1&authuser=0&view=1). Has anyone already persued this approach and dismissed it, or is there some interest in modifying it to viable solution?