Author: buildbot
Date: Thu Aug 30 09:41:18 2018
New Revision: 1034528
Log:
Staging update by buildbot for sis
Modified:
websites/staging/sis/trunk/content/ (props changed)
websites/staging/sis/trunk/content/downloads.html
websites/staging/sis/trunk/content/epsg.html
Propchange: websites/staging/sis/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Aug 30 09:41:18 2018
@@ -1 +1 @@
-1839654
+1839656
Modified: websites/staging/sis/trunk/content/downloads.html
==============================================================================
--- websites/staging/sis/trunk/content/downloads.html (original)
+++ websites/staging/sis/trunk/content/downloads.html Thu Aug 30 09:41:18 2018
@@ -185,8 +185,8 @@ If you accept those terms of use, then t
<p>Above dependency uses a read-only embedded Derby database.
-Note that the requirement to uncompress the <code>sis-embedded-data.jar</code>
file
-slows down <code>CRS.forCode(â¦)</code> and
<code>CRS.findCoordinateOperation(â¦)</code> method executions.
+Note that the need to uncompress the <code>sis-embedded-data.jar</code> file
+slows down <code>CRSâ.forCode(â¦)</code> and
<code>CRSâ.findCoordinateOperation(â¦)</code> method executions.
For better flexibility and performance, it is also possible to use an
uncompressed
and writable Derby database, or to install the EPSG dataset on HSQL or
PostgreSQL.
See <a href="epsg.html">How to use EPSG geodetic dataset</a> page for more
information.</p>
Modified: websites/staging/sis/trunk/content/epsg.html
==============================================================================
--- websites/staging/sis/trunk/content/epsg.html (original)
+++ websites/staging/sis/trunk/content/epsg.html Thu Aug 30 09:41:18 2018
@@ -220,7 +220,7 @@ However this simplicity come with the fo
<li>no option for choosing which data to use (and consequently which license
to accept),</li>
<li>no possibility to choose the database engine (i.e. the database software
is fixed to Derby),</li>
<li>no possibility to add user data (i.e. the database is read-only),</li>
-<li>slower execution of <code>CRS.forCode(â¦)</code> and
<code>CRS.findCoordinateOperation(â¦)</code>, unless the JAR file is
uncompressed.</li>
+<li>slower execution of <code>CRS.forCode(â¦)</code> and
<code>CRS.findCoordinateOperation(â¦)</code> methods, unless the JAR file is
uncompressed.</li>
</ul>
<p>This dependency can be declared as below
(see the <a href="downloads.html#epsg">download</a> page for more information
about Maven dependency declaration).
@@ -238,11 +238,11 @@ Note that <code>sis-epsg</code> and <cod
<p>The performance issue can be avoided if the JAR file is uncompressed.
But uncompressed <code>sis-embedded-data.jar</code> file is more than 5 times
larger than the compressed file.
-Given that <code>CRS.forCode(â¦)</code> and
<code>CRS.findCoordinateOperation(â¦)</code> should not be invoked too often,
+Given that <code>CRSâ.forCode(â¦)</code> and
<code>CRSâ.findCoordinateOperation(â¦)</code> should not be invoked too
often,
and that performance degradation does not apply to the
<code>CoordinateOperation</code> instances created by those method calls,
the JAR file is distributed on the Maven repository in its compressed form.
If desired, better performance can be achieved by using one of the other
configurations described in this page,
-or by uncompressing <code>sis-embedded-data.jar</code> locally.</p>
+or by uncompressing the <code>sis-embedded-data.jar</code> file locally.</p>
<h1 id="jndi">Use Java Naming and Directory Interface<a class="headerlink"
href="#jndi" title="Permanent link">¶</a></h1>
<p>While Apache SIS uses Apache Derby by default, it is also possible to use
another database software like HSQL or PostgreSQL.
For using an arbitrary database, register a <code>javax.sql.DataSource</code>
instance through the Java Naming and Directory Interface (JNDI).
