sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From desruisse...@apache.org
Subject svn commit: r1839656 - in /sis/site/trunk/content: downloads.mdtext epsg.mdtext
Date Thu, 30 Aug 2018 09:41:11 GMT
Author: desruisseaux
Date: Thu Aug 30 09:41:11 2018
New Revision: 1839656

URL: http://svn.apache.org/viewvc?rev=1839656&view=rev
Log:
Documentation tuning.

Modified:
    sis/site/trunk/content/downloads.mdtext
    sis/site/trunk/content/epsg.mdtext

Modified: sis/site/trunk/content/downloads.mdtext
URL: http://svn.apache.org/viewvc/sis/site/trunk/content/downloads.mdtext?rev=1839656&r1=1839655&r2=1839656&view=diff
==============================================================================
--- sis/site/trunk/content/downloads.mdtext [UTF-8] (original)
+++ sis/site/trunk/content/downloads.mdtext [UTF-8] Thu Aug 30 09:41:11 2018
@@ -114,8 +114,8 @@ If you accept those terms of use, then t
     </dependencies>
 
 Above dependency uses a read-only embedded Derby database.
-Note that the requirement to uncompress the `sis-embedded-data.jar` file
-slows down `CRS.forCode(…)` and `CRS.findCoordinateOperation(…)` method executions.
+Note that the need to uncompress the `sis-embedded-data.jar` file
+slows down `CRS​.forCode(…)` and `CRS​.findCoordinateOperation(…)` 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 [How to use EPSG geodetic dataset](epsg.html) page for more information.

Modified: sis/site/trunk/content/epsg.mdtext
URL: http://svn.apache.org/viewvc/sis/site/trunk/content/epsg.mdtext?rev=1839656&r1=1839655&r2=1839656&view=diff
==============================================================================
--- sis/site/trunk/content/epsg.mdtext [UTF-8] (original)
+++ sis/site/trunk/content/epsg.mdtext [UTF-8] Thu Aug 30 09:41:11 2018
@@ -148,7 +148,7 @@ However this simplicity come with the fo
   * no option for choosing which data to use (and consequently which license to accept),
   * no possibility to choose the database engine (i.e. the database software is fixed to
Derby),
   * no possibility to add user data (i.e. the database is read-only),
-  * slower execution of `CRS.forCode(…)` and `CRS.findCoordinateOperation(…)`, unless
the JAR file is uncompressed.
+  * slower execution of `CRS.forCode(…)` and `CRS.findCoordinateOperation(…)` methods,
unless the JAR file is uncompressed.
 
 This dependency can be declared as below
 (see the [download](downloads.html#epsg) page for more information about Maven dependency
declaration).
@@ -166,11 +166,11 @@ Note that `sis-epsg` and `sis-embedded-d
 
 The performance issue can be avoided if the JAR file is uncompressed.
 But uncompressed `sis-embedded-data.jar` file is more than 5 times larger than the compressed
file.
-Given that `CRS.forCode(…)` and `CRS.findCoordinateOperation(…)` should not be invoked
too often,
+Given that `CRS​.forCode(…)` and `CRS​.findCoordinateOperation(…)` should not be
invoked too often,
 and that performance degradation does not apply to the `CoordinateOperation` 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 `sis-embedded-data.jar` locally.
+or by uncompressing the `sis-embedded-data.jar` file locally.
 
 
 



Mime
View raw message