Re: [Geotools-devel] Re: trunk/2.1 use of deprecation and replacement

[Jody G. <jga...@re...>]

James Macgill wrote:

>
>>
>> The break for 2.2.x is the change to a Geometry API and going away 
>> from JTS. Although I kind of think we should talk to Vivid first, and 
>> consider starting a GPL fork if we have to - the JTS algorthims are 
>> great and it would be sad to leave them behind for waters untested.
>
>
> Please do not misunderstand the 'move from JTS'!  The plan is only to 
> add a layer of abstraction so that we are not tied to JTS.  I want to 
> allow for alternative implementations (e.g. more compact, faster but 
> less robust...) but I do not want to drop the use of JTS completely.  
> Indeed, even after the geometry change JTS will still be the default 
> underlying engine for our geometries.  It is way too good and solid to 
> ever think of abandoning it!

I do understand :-)

And have talked to vivid about using Geometry interfaces several times now.

Everyone agrees the idea is sound - it is just that they may not be able 
to help.

It would be nice if we could work on a JTS 2.0 with them that supports 
GeoAPI interfaces.  I would be happy to volunteer on such a project 
(even if it was under the current JTS GPL license). We just may get more 
traction using the underlying engine directly (I think it is all based 
on Coordinate arrays), rather then making wrapping.

Jody