John Cartwright wrote: > Hello All, > > it doesn't look as if the GeometryConverter class has changed that much > since we submitted the original patch > (http://jira.codehaus.org/browse/GEOT-393). If I can get it to work w/ > 2.4/2.5, is it something that would be considered for inclusion in 2.5? > Actually now that we have the idea of unsupported modules you will find it much easier to contribute code to GeoTools (ie you can do it yourself). Why not start an unsupported/informix plugin and use the improved geometry converter as the initial code?
---Aside: Ignore this if Boring --- Aside; one direction to go that would be sweet is to make use of Commons converters; we have started using this at the Expression level (and it is how "123" becomes an Integer) and how a Geometry becomes a Java 2D Shape for rendering on screen. Indeed this technique is how ISO Geometry will be used in GeoTools; or how you could ask GeoTools to work directly with Oracle Geometry :-D - yes everyone still wants curve > By the way, has anyone looked at incorporating hibernate spatial into > geotools? > There are lots of of OR mapper + Spatial projects; one that worked with GeoTools for a while is JPOX. You are welcome to start a community plugin using hibernate spatial. We have done something similar in the past but it was for a commercial client and was not released to the community. In general it was not worth making actual objects out of your hibernate requests; but instead work from the returned data and build up a Feature. Think of the Feature / FeatureType data structure being handled as a dynamic bean and you have the right idea. Jody ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geotools-gt2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
