Author: buildbot
Date: Fri Sep 6 03:24:49 2013
New Revision: 877447
Log:
Staging update by buildbot for jena
Modified:
websites/staging/jena/trunk/content/ (props changed)
websites/staging/jena/trunk/content/documentation/query/spatial-query.html
Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Sep 6 03:24:49 2013
@@ -1 +1 @@
-1520483
+1520484
Modified:
websites/staging/jena/trunk/content/documentation/query/spatial-query.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/query/spatial-query.html
(original)
+++ websites/staging/jena/trunk/content/documentation/query/spatial-query.html
Fri Sep 6 03:24:49 2013
@@ -204,12 +204,12 @@ for a large scale enterprise search appl
<p>For 2) WKT, DBPedia uses <code>geo:geometry</code>, while Linked Geo Data
adopts <code>ogc:asWKT</code> and <code>geo:geometry</code>.</p>
-<p><em>The builtin predicates that can be automatically processed by
jena-spatial include: 1) <code>geo:lat</code>, <code>geo:long</code>; 2)
<code>geo:geometry</code>, <code>ogc:asWKT</code>.</em></p>
+<p><strong>The builtin predicates that can be automatically processed by
jena-spatial include: 1) <code>geo:lat</code>, <code>geo:long</code>; 2)
<code>geo:geometry</code>, <code>ogc:asWKT</code>.</strong></p>
<p><strong>Important note</strong> In order to read geo data in 2) WKT literal
format, jena-spatial uses <a
href="http://tsusiatsoftware.net/jts/main.html";>JTS Topology Suite</a>,
which is under LGPL licence. jena-spatial <strong>does not</strong> make a
hard dependency on JTS. In other words,
if an end user just uses the feature of 1), there's no need to depend on JTS
(i.e. nothing needs to be done). If he wants 2),
he can make it by setting the <code>SpatialContextFactory</code> of <a
href="https://svn.apache.org/repos/asf/jena/trunk/jena-spatial/src/main/java/org/apache/jena/query/spatial/EntityDefinition.java";>EntityDefinition</a>
to <code>JtsSpatialContextFactory</code>,
-which is an optional choice): </p>
+which is an optional choice. In this way, the JTS libs should be in the
classpath. Here's the sample code: </p>
<div class="codehilite"><pre><span class="n">import</span> <span
class="n">org</span><span class="p">.</span><span class="n">apache</span><span
class="p">.</span><span class="n">jena</span><span class="p">.</span><span
class="n">query</span><span class="p">.</span><span
class="n">spatial</span><span class="p">.</span><span
class="n">EntityDefinition</span>
<span class="p">...</span>
<span class="n">EntityDefinition</span> <span class="n">entDef</span> <span
class="p">=</span> <span class="n">new</span> <span
class="n">EntityDefinition</span><span class="p">(</span>"<span
class="n">entityField</span>"<span class="p">,</span> "<span
class="n">geoField</span>"<span class="p">);</span>
