A big +1 here. We are already spread pretty thin in GeoTools in terms of
developer resources vs number of modules so sharing maintainence burden
with another community outweighs any edge that the code that is sitting
unmaintained at the moment might have.
And as Andrea states what they have is
Jody Garnett ha scritto:
> Andrea has done a good job setting up a collaboration opportunity for
> us with the deegree team. Looks like there is an IRC breakout meeting
> later today:
> -
> http://www.timeanddate.com/worldclock/meetingdetails.html?year=2009&month=7&day=8&hour=9&min=30&sec=0&p1=215
I cant make this meeting at short notice, but I'd like to express my
support for the idea of collaboration.
The similarities between Deegree and Geoserver lead to quite
reasonable questions of "which horse do I back", which may result in
failure to commit to anything - having a collaboration makes
I went over the deegree geometry implementation with Ben.
It seems fine; very similar to jts-wrapper in places, not quite as far
along as gt-geometry module, but a very sensible starting place.
Interestingly their codebase has a trunk/tags per module - here are
some examples:
-
http://wald.intev
Andrea has done a good job setting up a collaboration opportunity for
us with the deegree team. Looks like there is an IRC breakout meeting
later today:
-
http://www.timeanddate.com/worldclock/meetingdetails.html?year=2009&month=7&day=8&hour=9&min=30&sec=0&p1=215&p2=240&p3=179&p4=1091
>From my st
