If I read the documentation correctly it can optionally use the JTS library (which yes is LGPL and so no go for Apache projects) if that library is needed, it can be used without.
I'm not sure if the extra features that JTS provides are necessary for a GeoSPARQL implementation because I'm not up to speed on exactly what GeoSPARQL requires Rob On 9/12/12 2:51 PM, "Marco Neumann" <[email protected]> wrote: >it uses the JTS Topology Suite indexer which hasn't been updated for a >while but is open source under the LGPL license. > > > >On Wed, Sep 12, 2012 at 5:42 PM, Rob Vesse <[email protected]> wrote: > >> I remember some discussions a while back about one of the barriers to >> implementing GeoSPARQL in Jena being the lack of a good indexing >>library to >> use >> >> I notice that Lucene 4.0 has a new Spatial module - >> http://lucene.apache.org/core/4_0_0-BETA/spatial/index.html which is >> itself built on another library Spatial4j which is ASL licensed >> >> Would these be sufficient pieces to get us started? I haven't looked in >> detail as to whether these libraries provide the specific geospatial >> primitives and functions we'd need to implement GeoSPARQL >> >> Rob >> > > > >-- > > >--- >Marco Neumann >KONA > >Join us at SemTech Biz in New York City October 15-17, 2012 and save 15% >with code STMN >http://www.lotico.com/evt/SemTechBizNYC2012
