Jody Garnett a écrit :
> I have deployed 2.3-M2. I was going to go update GeoTools to reflect the changes
Thanks a lot!
Just for as a reminder, if we stick with monthly deployment, the 2.3-M3 release
will be in 2 weeks. We have:
2.3-M1: The current version used by GeoTools.
2.3-M2: contains new methods and deprecated methods.
2.3-M3 (currently trunk): deprecated methods removed.
If you update GeoTools to 2.3-M2, it is nicer for users because they benefit
from the "deprecate now, delete in next release" cycle, but it is more work for
you since you have to add new methods will keeping the deprecated ones.
If you update GeoTools directly to 2.3-M3 (in two weeks), it would be less work
for you since the deprecated methods have been removed. Most of the changes in
GeoTools would be simply methods renaming, which are easier and faster to
handle. However the consequence would be no "deprecate, then delete" cycle for
> did we figure out what was happening with
From the email I have read on the OGC CRS working group, they are considering
changing the type from SingleCRS to CoordinateReferenceSystem. In other words
the specification would become exactly the way GeoAPI currently is.
Their change proposal is not yet approved (it may be a long road), but I have
not seen any opposition on this particulal issue up to date.
For GeoAPI, the net result is a nothing else than a method renaming, from
getCoordinateReferenceSystems() to getComponents() in order to align on the
naming used in the specification. They would be no change in functionalities.
Given that GeoAPI used the CoordinateReferenceSystem type since the begining and
given that we need more stability, I think that we may stick to the way GeoAPI
is now (on trunk) even if OGC finally reject their change proposal.