Hello Landon
If you stick to GeoAPI interfaces, there is no change. Both GeoTools and
Geotidy
implement the same set of interfaces. This also means that you can try a
library
and switch to the other without any change in your code.
If you use directly GeoTools implementation classes, most of them have no or
few
changes. More specifically most classes in org.geotools.referencing (including
the CRS convenience class) and in the cs, crs and datum packages are unchanged.
You are at risk to suffer from changes if you play directly:
- The org.geotools.referencing.operation.projection package.
- factories implementation (especially the authority factories)
- WKT parser and formatter
But you should not. If you stick with GeoAPI interfaces or the classes that
most
peoples uses (CRS, GeodeticCalculator, toString() or toWKT() for WKT
formatting,
etc.), all the above is transparent to you. For most developpers, the CRS
utility class is the central point where they get most of their work done
(getting a CRS from a WKT string or a EPSG code, getting the transform between
two CRS, etc.) and the API of this class is absolutly unchanged.
In addition I commited myself to help with the port of Geotidy to Java 5 so it
can be used with GeoTools. So Geotidy may be back to Geotools if the community
wants it. But it can't be back now because not enough functionalities are ready.
Martin
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
