Hey Martin, On 12/13/12 7:36 PM, "Martin Desruisseaux" <[email protected]> wrote:
>Hello Joe, Adam and all > >[...snip...] > >On SIS side, SIS would uses only the GeoAPI geometry interfaces. We >would have no direct JTS dependency in SIS. However JTS would be used >indirectly just by letting the user put himself the JTS JAR files in the >classpath - it should be detected automatically and used though the >wrappers. This would be a temporary solution until we have a real ISO >19107 implementation, and would probably be needed anyway for JTS >inter-operability... Thanks for the history above on ISO 19107, etc. The big thing at Apache is to not introduce "surprises" downstream, e.g., the need to download an LGPL library in order to do something interesting, while obfuscating it with APIs as part of the core ALv2 library. So I would not be in favor of any JTS dependency, even optional. I realize this is limiting in some fashion as JTS is fairly feature rich geometry library. But one of the goals of SIS is to provide a fully ALv2 compatible, "no surprises" and feature rich package which means, unless JTS relicenses itself as ALv2 (which there have been some discussions regarding), then we can't use it in SIS. I am committed to helping with some alternative, so whatever we want to do as a community, even going all the way to rolling our own, let's simply do it, move forward, and deliver something awesome! Cheers, Chris > >In the particular case of Envelope, there is already a quite elaborated >class available [6]. But this is about the only one on the geometric side. > > Martin > > >[1] >http://www.oracle.com/technetwork/java/javafx/overview/faq-1446554.html#6 >[2] http://www.opengeospatial.org/standards/as >[3] http://www.geoapi.org/snapshot/pending/index.html >[4] http://www.geoapi.org/implementations.html >[5] http://www.opengeospatial.org/event/1301tcagenda >[6] >http://www.geotoolkit.org/apidocs/org/geotoolkit/geometry/GeneralEnvelope. >html >
