Deegree has something which purports to be a 19107 implementation. Is also follows an interface/implementation design pattern. Unfortunately, at first blush, the methods are not the same as my copy of 19107/Topic 1, and GeoAPI is not referenced at all. Has anyone looked closer at this?
FYI, I'm looking at making a stand-alone "geometry" module (which implements GeoAPI geometry classes) by adapting _something_. Current alternatives are: 1] Adapt JTS because it has a well-documented lineage, and is active. 2] Adapt deegree because it says it's a 19107 implementation. 3] Fake something where most of the methods throw UnsupportedOperationException. Near term needs are quite constrained: GM_Object, GM_Point, and dependent classes. Any advice from people who have thought about this more than me? Bryce ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
