Hi Andy, Thanks for pointing out the licence issue.
In order to read geo data in WKT literal format, jena-spatial uses JTS as a parsing tool. Yes, it's not a required feature if no WKT literals are in geo data. I've refactored the code to resolve the problem. Now jena-spatial can work without JTS dependency. It's optional for a user to include JTS in jena-spatial. Please check out the latest code of jena-spatial from jena svn trunk. I'll also emphasise that in the documentation. By the way, I've committed a document file of "spatial-query.mdtext" [1] in the jena website svn. But the web page does not appear in jena website front. I get 404-not-found error when accessing "spatial-query.html" [2]. Could you please tell me why? Thanks! [1] https://svn.apache.org/repos/asf/jena/site/trunk/content/documentation/query/spatial-query.mdtext [2] http://jena.apache.org/documentation/query/spatial-query.html Best regards, Ying Jiang On Tue, Sep 3, 2013 at 2:44 AM, Andy Seaborne <[email protected]> wrote: > Hi Ying, > > There is a dependency on com.vividsolutions JTS. JTS does not have an > acceptable license (it's LGPL). > > It seems to be used via com.spatial4j. That's OK for com.spatial4j still to > be Apache Licensed because the dependency is not required. spatial4j uses: > > <optional>true</optional> > > i.e. an end user can add it if they wish but aren't required to. The Jena > project needs to provide somethgin without a hard dependency on JTS. > > The system needs to work without the com.vividsolutions::jts dependency. > > So if I understand the code correctly: > > public class SpatialQuery > .... > public static final SpatialContext ctx = SpatialContext.GEO ; > > > What capabilities does jena-spatial loose with this restriction? > > Andy >
