Sandro,
I don't think the bug affects any code directly in JTS. However, obviously
it might affect client code using this functionality.
As you say, a unit test would be nice to have. I'll try and work on one.
Martin
On Thu, Jan 22, 2015 at 2:39 AM, Sandro Santilli <[email protected]> wrote:
> On Wed, Jan 21, 2015 at 11:36:03AM -0800, Martin Davis wrote:
>
> > This requires some special-purpose coding using the JTS noding package.
> A
> > SegmentIntersector class needs to be created which only counts nodes, and
> > does not store them. This is then run using the MCIndexNoder class.
> >
> > In fact, I just commited code to do exactly this:
> > https://sourceforge.net/p/jts-topo-suite/code/950/
> >
> > (The counting code is added to the InteriorIntersectionFinder class, and
> > the NodingFunctions.nodeCount function shows how to use it.)
>
> Does the bugfix you report (to not short-circuit) only affect the new
> functionality (node-count) or also any other pre-existing one ?
>
> I'm asking because the commit does not include any test for exploiting
> the reported bug...
>
> --strk;
>
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Jts-topo-suite-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jts-topo-suite-user
