[geos-devel] Incorporating JTS 1.2 changes

[Martin Davis]

They do affect relate().  In JTS 1.1 relate() would fail if run on an geometry containing repeated points (since this was an invalid geometry according to the JTS 1.1 model).  In JTS 1.2 repeated points are effectively removed before operations are performed, so repeated points are no longer a failure case.

The changes are not too major, so it should be not problem to roll them in.    They should be independent of the debugging work Yury is doing now.  Perhaps the best strategy is to let him carry on cleaning up the current code.  When that's complete, he can roll in the changes from 1.2 before continuing on to the overlay ops and other operations.

Martin Davis, Senior Technical Specialist
Vivid Solutions Inc.
Suite #1A-2328 Government Street   Victoria, B.C.   V8T 5G5
Phone: (250) 385 6040    Fax: (250) 385 6046
EMail: mbdavis at vividsolutions.com  Web: www.vividsolutions.com


> -----Original Message-----
> From: David Blasby [mailto:dblasby at refractions.net]
> Sent: Wednesday, October 16, 2002 11:10 AM
> To: geos-devel at geos.refractions.net
> Subject: Re: [geos-devel] Incorporating JTS 1.2 changes
> 
> 
> Martin Davis wrote:
> 
> > As people have probably seen, Version 1.2 of JTS has been 
> released to the world.   It incorporates a couple of 
> significant changes:
> >
> > - repeated points are now handled
> > - the robustness of line segment intersection has been improved.
> >
> > The GEOS project team probably need to think about if, when 
> and how these changes should be rolled into GEOS.
> 
> Are these changes going to affect the relate() functions?
> 
> If not, lets add these changes in when yuri starts on the 
> "intersection"-based functions.
> 
> I'd really like to get these changes in fairly soon so we 
> dont have to worry about code drift.
> 
> dave
> 
> 
> _______________________________________________
> geos-devel mailing list
> geos-devel at geos.refractions.net
> http://geos.refractions.net/mailman/listinfo/geos-devel
>