Author: buildbot
Date: Tue May 24 01:11:50 2016
New Revision: 988987
Log:
Staging update by buildbot for sis
Added:
websites/staging/sis/trunk/content/examples/coordinates/
websites/staging/sis/trunk/content/examples/coordinates/AmericanCities.csv
websites/staging/sis/trunk/content/examples/coordinates/CanadianCities.csv
websites/staging/sis/trunk/content/examples/crs/
websites/staging/sis/trunk/content/examples/crs/EquivalentDefinition.wkt
websites/staging/sis/trunk/content/examples/crs/MissingIdentifier.wkt
websites/staging/sis/trunk/content/examples/crs/WrongAxisOrder.wkt
Removed:
websites/staging/sis/trunk/content/examples/EquivalentDefinition.wkt
websites/staging/sis/trunk/content/examples/MissingIdentifier.wkt
websites/staging/sis/trunk/content/examples/WrongAxisOrder.wkt
Modified:
websites/staging/sis/trunk/content/ (props changed)
websites/staging/sis/trunk/content/command-line.html
websites/staging/sis/trunk/content/index.html
Propchange: websites/staging/sis/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue May 24 01:11:50 2016
@@ -1 +1 @@
-1745008
+1745294
Modified: websites/staging/sis/trunk/content/command-line.html
==============================================================================
--- websites/staging/sis/trunk/content/command-line.html (original)
+++ websites/staging/sis/trunk/content/command-line.html Tue May 24 01:11:50
2016
@@ -93,7 +93,12 @@
visibility: hidden;
}
h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
-<p>A command-line interface is provided for extracting information from data
files or authority codes.</p>
+<p>A command-line interface is provided for extracting information from data
files or authority codes,
+and for performing coordinate operations.
+That command-line tool is provided for allowing users to experiment some
Apache SIS functionalities
+without writing Java code.
+For each example, key Java methods are listed for allowing users to reproduce
the functionality
+in their own application.</p>
<div class="toc">
<ul>
<li><a href="#install">Installation</a><ul>
@@ -102,8 +107,9 @@ h2:hover > .headerlink, h3:hover > .head
</li>
<li><a href="#usage">Usage</a></li>
<li><a href="#examples">Examples</a><ul>
-<li><a href="#crs">Extracting ISO 19111 Coordinate Reference System
(CRS)</a></li>
-<li><a href="#identifier">Extracting EPSG identifier from a Coordinate
Reference System</a></li>
+<li><a href="#crs">Getting ISO 19111 Coordinate Reference Systems
(CRS)</a></li>
+<li><a href="#identifier">Getting a verified EPSG identifier from a Coordinate
Reference System</a></li>
+<li><a href="#coordinateOperation">Performing coordinate conversions or
transformations</a></li>
<li><a href="#metadata">Extracting ISO 19115 Metadata</a></li>
</ul>
</li>
@@ -163,33 +169,43 @@ For executing a command, the syntax is:<
<tr><td><code>metadata</code></td> <td>Show metadata information for the
given file.</td></tr>
<tr><td><code>crs</code></td> <td>Show Coordinate Reference System
(CRS) information for the given file or code.</td></tr>
<tr><td><code>identifier</code></td> <td>Show identifiers for metadata and
referencing systems in the given file.</td></tr>
+ <tr><td><code>transform</code></td> <td>Convert or transform coordinates
from given source CRS to target CRS.</td></tr>
</table>
-<p>The set of legal options and the expected number of file arguments depends
on the command being executed.
+<p>The set of legal options and the expected number of file arguments depend
on the command being executed.
However all commands support the <code>--help</code> option, which lists the
options available for that command.
Available options will be from the following list:</p>
<table>
- <tr><td><code>--format</code></td> <td>The output format:
<code>xml</code>, <code>wkt</code>, <code>wkt1</code> or
<code>text</code>.</td></tr>
- <tr><td><code>--locale</code></td> <td>The locale to use for the command
output.</td></tr>
- <tr><td><code>--timezone</code></td> <td>The timezone for the dates to be
formatted.</td></tr>
- <tr><td><code>--encoding</code></td> <td>The encoding to use for the command
output.</td></tr>
- <tr><td><code>--colors</code></td> <td>Whether colorized output shall be
enabled.</td></tr>
- <tr><td><code>--brief</code></td> <td>Whether the output should contains
only brief information.</td></tr>
- <tr><td><code>--verbose</code></td> <td>Whether the output should contains
more detailed information.</td></tr>
- <tr><td><code>--debug</code></td> <td>Prints full stack trace in case of
failure.</td></tr>
- <tr><td><code>--help</code></td> <td>Lists the options available for a
specific command.</td></tr>
+ <tr><td><code>--sourceCRS</code></td> <td>The Coordinate Reference System of
input data.</td></tr>
+ <tr><td><code>--targetCRS</code></td> <td>The Coordinate Reference System of
output data.</td></tr>
+ <tr><td><code>--format</code></td> <td>The output format:
<code>xml</code>, <code>wkt</code>, <code>wkt1</code> or
<code>text</code>.</td></tr>
+ <tr><td><code>--locale</code></td> <td>The locale to use for the command
output.</td></tr>
+ <tr><td><code>--timezone</code></td> <td>The timezone for the dates to be
formatted.</td></tr>
+ <tr><td><code>--encoding</code></td> <td>The encoding to use for the
command output.</td></tr>
+ <tr><td><code>--colors</code></td> <td>Whether colorized output shall be
enabled.</td></tr>
+ <tr><td><code>--brief</code></td> <td>Whether the output should contains
only brief information.</td></tr>
+ <tr><td><code>--verbose</code></td> <td>Whether the output should contains
more detailed information.</td></tr>
+ <tr><td><code>--debug</code></td> <td>Prints full stack trace in case of
failure.</td></tr>
+ <tr><td><code>--help</code></td> <td>Lists the options available for a
specific command.</td></tr>
</table>
<p>The <code>--locale</code>, <code>--timezone</code> and
<code>--encoding</code> options apply to the command output sent to the
standard output stream,
but usually do not apply to the error messages sent to the standard error
stream.
The reason is that command output may be targeted to a client, while the error
messages are usually for the operator.</p>
<h1 id="examples">Examples<a class="headerlink" href="#examples"
title="Permanent link">¶</a></h1>
-<h2 id="crs">Extracting ISO 19111 Coordinate Reference System (CRS)<a
class="headerlink" href="#crs" title="Permanent link">¶</a></h2>
-<p>SIS can read Coordinate Reference System (CRS) definitions from various
sources:</p>
+<p>The following examples first show how to get a Coordinate Reference System
(CRS) from different kinds of definitions.
+CRS contain necessary information for locating points on Earth.
+Those information include the geodetic datum, the map projection (if any), the
axes and their units of measurement.
+When two such CRS are known (the <em>source</em> and the <em>target</em>), it
is possible to convert or transform points between those CRS.
+However the coordinate operation depends not only on the source and target
CRS, but also on the <em>area of interest</em> as shown
+by the example transforming city coordinates in USA and in Canada.
+Then another example show how to get a wider set of metadata, with the CRS as
only one specific element of those metadata.</p>
+<h2 id="crs">Getting ISO 19111 Coordinate Reference Systems (CRS)<a
class="headerlink" href="#crs" title="Permanent link">¶</a></h2>
+<p>Apache SIS can read Coordinate Reference System (CRS) definitions from
various sources:</p>
<ul>
-<li>Code from the EPSG geodetic dataset</li>
-<li><em>Well Known Text</em> (WKT) format version 1 and 2</li>
-<li><em>Geographic Markup Language</em> (GML) version 3.2</li>
+<li>Codes from the EPSG geodetic dataset</li>
+<li>Texts in <em>Well Known Text</em> (WKT) format version 1 and 2</li>
+<li>XML files conform to <em>Geographic Markup Language</em> (GML) schema
version 3.2</li>
</ul>
<p>The easiest way to see a CRS definition is to use an EPSG code.
The <a href="http://www.epsg.org/";>EPSG geodetic dataset</a> is a widely-used
source of definitions for thousands of Coordinate Reference Systems.
@@ -229,7 +245,7 @@ documented in <a href="downloads.html#ep
</details></p>
<p>The above output is compatible with version 2 of <em>Well Known Text</em>
(WKT) format.
However some applications are restricted to WKT version 1.
-For an output using the legacy WKT 1 format, one can add the <code>--format
wkt1</code> option to the above command.</p>
+For an output using the legacy WKT 1 format, one can add the <code>--format
wkt1</code> option to the above command-line.</p>
<p>The âWKT 2â specification allows some flexibility in keyword names and
in the way to specify units of measurement.
By default, the command-line uses this flexibility for producing less verbose
but still legal WKT 2 output.
If an output closer to WKT 2 recommendations is desired, one can add the
<code>--format wkt2</code> option to the above command.
@@ -237,15 +253,29 @@ The result will be slightly more verbose
<p>Apache SIS can also read and write CRS definitions in the <em>Geographic
Markup Language</em> (GML) format.
For GML output, one can add the <code>--format xml</code> option to the above
command.
The result will be much more verbose than WKT outputs.</p>
-<h2 id="identifier">Extracting EPSG identifier from a Coordinate Reference
System<a class="headerlink" href="#identifier" title="Permanent
link">¶</a></h2>
+<p>Java methods for accessing functionalities shown in above examples are:</p>
+<ul>
+<li>Convenience static methods in <code>org.apache.sis.referencing</code>
package:<ul>
+<li><code>CRS.forCode(String)</code></li>
+<li><code>CRS.fromWKT(String)</code></li>
+<li><code>CRS.fromXML(String)</code></li>
+</ul>
+</li>
+<li>Classes in other packages (less convenient but give more control):<ul>
+<li><code>org.apache.sis.io.wkt.WKTFormat</code> â control WKT version,
syntax highlighting, <em>etc.</em></li>
+<li><code>org.apache.sis.xml.MarshallerPool</code> â control GML version,
link resolutions, <em>etc.</em></li>
+</ul>
+</li>
+</ul>
+<h2 id="identifier">Getting a verified EPSG identifier from a Coordinate
Reference System<a class="headerlink" href="#identifier" title="Permanent
link">¶</a></h2>
<p>Because the EPSG geodetic dataset is so commonly used,
a very common practice is to specify a CRS using only its EPSG code instead
than its full definition.
Such codes can be written in different ways. For example all the following
strings are for the same code:</p>
<ul>
-<li><code>EPSG:4326</code></li>
-<li><code>urn:ogc:def:crs:EPSG::4326</code></li>
-<li><code>http://wwwâ.opengisâ.net/def/crs/epsg/0/4326</code> (not yet
supported on the command-line)</li>
-<li><code>http://wwwâ.opengisâ.net/gml/srs/epsgâ.xml#4326</code> (not
yet supported on the command-line)</li>
+<li><code>"EPSG:4326"</code></li>
+<li><code>"urn:ogc:def:crs:EPSG::4326"</code></li>
+<li><code>"http://wwwâ.opengisâ.net/def/crs/epsg/0/4326";</code> (not yet
supported on the command-line)</li>
+<li><code>"http://wwwâ.opengisâ.net/gml/srs/epsgâ.xml#4326";</code> (not
yet supported on the command-line)</li>
</ul>
<p>In a <em>Well Known Text</em> (WKT) string, the code can appear at the
bottom of the definition
in an optional element like <code>ID["EPSG", 4326]</code> or
<code>AUTHORITY["EPSG", "4326"]</code>.
@@ -255,7 +285,7 @@ Sometime Apache SIS can find a missing c
but in which the <code>ID["EPSG", 27572]</code> element has been intentionally
omitted.
Furthermore, the <em>âNTF (Paris) / Lambert zone IIâ</em> name has been
replaced by <em>âNTF (Paris) / zone to be discovered by the demoâ</em> name.
Executing the following command:</p>
-<div class="codehilite"><pre>sis identifier
http://sis.staging.apache.org/examples/MissingIdentifier.wkt
+<div class="codehilite"><pre>sis identifier
http://sis.apache.org/examples/crs/MissingIdentifier.wkt
</pre></div>
@@ -264,13 +294,13 @@ Executing the following command:</p>
</pre></div>
-<p>As we can see, SIS has been able to find back the identifier code and the
actual CRS name.</p>
+<p>As we can see, Apache SIS has been able to find back the identifier code
and the actual CRS name.</p>
<p>Sometime a WKT declares wrongly an EPSG code.
The most frequent case is a WKT that defines a Coordinate Reference System
with (<em>longitude</em>, <em>latitude</em>) axes,
but declare an EPSG code for a CRS with (<em>latitude</em>,
<em>longitude</em>) axes.
-Apache SIS can detect such mismatch.
+Apache SIS can detect such mismatches.
For example executing the following command:</p>
-<div class="codehilite"><pre>sis identifier
http://sis.staging.apache.org/examples/WrongAxisOrder.wkt
+<div class="codehilite"><pre>sis identifier
http://sis.apache.org/examples/crs/WrongAxisOrder.wkt
</pre></div>
@@ -304,7 +334,7 @@ The next example asks the identifier of
<p>Executing the following command:</p>
-<div class="codehilite"><pre>sis identifier
http://sis.staging.apache.org/examples/EquivalentDefinition.wkt
+<div class="codehilite"><pre>sis identifier
http://sis.apache.org/examples/crs/EquivalentDefinition.wkt
</pre></div>
@@ -317,6 +347,90 @@ The next example asks the identifier of
<em>âMercator (variant A)â</em> projection with a <em>âScale factor at
natural originâ</em> parameter value of 0.755799⦠on the WGS84 datum is
numerically equivalent to a
<em>âMercator (variant B)â</em> projection with a <em>âLatitude of 1st
standard parallelâ</em> parameter value of 41° on the same datum.
This recognition allowed SIS to return the EPSG:3994 code even if it stands
for a CRS defined as a <em>âMercator (variant B)â</em> projection rather
than variant A.</p>
+<p>Java methods for accessing functionalities shown in above example are:</p>
+<ul>
+<li>Convenience static method in <code>org.apache.sis.referencing</code>
package:<ul>
+<li><code>IdentifiedObjects.lookupURN(IdentifiedObject, Citation)</code></li>
+</ul>
+</li>
+<li>Class in other package (less convenient but give more control):<ul>
+<li><code>org.apache.sis.referencing.factory.IdentifiedObjectFinder</code></li>
+</ul>
+</li>
+</ul>
+<h2 id="coordinateOperation">Performing coordinate conversions or
transformations<a class="headerlink" href="#coordinateOperation"
title="Permanent link">¶</a></h2>
+<p>Coordinates represented in a given CRS can be transformed into coordinates
represented in another CRS.
+The coordinate transformations depend mostly on the <em>source</em> and
<em>target</em> CRS, but the <em>area of interest</em>
+can also have an influence; while optional, that area should be specified when
it is known.</p>
+<p>The following example transform coordinates from the North American Datum
1927 (EPSG:4267) to WGS84 (EPSG:4326).
+The example is run twice: once for cities in USA, then once for cities in
Canada:
+(Note: the application may log warnings to the console. Those warnings can be
ignored)</p>
+<div class="codehilite"><pre>wget
http://sis.apache.org/examples/coordinates/AmericanCities.csv
+wget http://sis.apache.org/examples/coordinates/CanadianCities.csv
+sis transform --sourceCRS EPSG:4267 --targetCRS EPSG:4326 AmericanCities.csv
+sis transform --sourceCRS EPSG:4267 --targetCRS EPSG:4326 CanadianCities.csv
+</pre></div>
+
+
+<p>The first execution should print the following header, followed by
transformed coordinate values.
+Note the operation code (EPSG:1173), domain of validity (United State) and
accuracy.</p>
+<div class="codehilite"><pre># Source: NAD27 (EPSG:4267)
+# Destination: WGS 84 (EPSG:4326)
+# Operations: NAD27 to WGS 84 (4) (EPSG:1173)
+# Domain: United States (USA) - onshore
+# Accuracy: 10.0 metres
+</pre></div>
+
+
+<p>The second execution should print the following header, followed by
transformed coordinate values.
+Note that the operation code (EPSG:1172), domain of validity (Canada) and
accuracy are not the same
+than in previous example.</p>
+<div class="codehilite"><pre># Source: NAD27 (EPSG:4267)
+# Destination: WGS 84 (EPSG:4326)
+# Operations: NAD27 to WGS 84 (3) (EPSG:1172)
+# Domain: Canada - onshore and offshore
+# Accuracy: 20.0 metres
+</pre></div>
+
+
+<p>The difference between those two operations become more visible by adding
the <code>--verbose</code> option
+to the above <code>sis transform</code> commands.
+This option shows the coordinate operation in Well Known Text (WKT) or
pseudo-WKT format.
+When transforming coordinates in USA, the operation contains the following
parameter values:</p>
+<div class="codehilite"><pre>Method["Geocentric translations (geog2D
domain)"],
+ Parameter["X-axis translation", -8.0, Unit["metre", 1]],
+ Parameter["Y-axis translation", 160.0, Unit["metre", 1]],
+ Parameter["Z-axis translation", 176.0, Unit["metre", 1]]
+</pre></div>
+
+
+<p>But when transforming coordinates in Canada, the operation rather contains
the following parameter values:</p>
+<div class="codehilite"><pre>Method["Geocentric translations (geog2D
domain)"],
+ Parameter["X-axis translation", -10.0, Unit["metre", 1]],
+ Parameter["Y-axis translation", 158.0, Unit["metre", 1]],
+ Parameter["Z-axis translation", 187.0, Unit["metre", 1]],
+</pre></div>
+
+
+<p>As seen in the above examples, the parameter values differ slightly with
the geographic area of the coordinates to transform.
+Those parameters could also be different if <em>datum shift grids</em> are
available. For example in USA:</p>
+<div class="codehilite"><pre>Method["NADCON"],
+ Parameter["Latitude difference file", "conus.las"],
+ Parameter["Longitude difference file", "conus.los"],
+</pre></div>
+
+
+<p>Java methods for accessing functionalities shown in above examples are:</p>
+<ul>
+<li>Convenience static method in <code>org.apache.sis.referencing</code>
package:<ul>
+<li><code>CRS.findOperation(CoordinateReferenceSystem,
CoordinateReferenceSystem, GeographicBoundingBox)</code></li>
+</ul>
+</li>
+<li>Class in other package (less convenient but give more control):<ul>
+<li><code>org.apache.sis.referencing.operation.DefaultCoordinateOperationFactory</code></li>
+</ul>
+</li>
+</ul>
<h2 id="metadata">Extracting ISO 19115 Metadata<a class="headerlink"
href="#metadata" title="Permanent link">¶</a></h2>
<p>SIS can read the header of a data file and print the metadata in an ISO
19115 structure.
The data file given in argument can be a local file or a URL.
@@ -370,6 +484,18 @@ As of SIS 0.7, only CF-compliant NetCDF
</details></p>
<p>Adding the <code>--format xml</code> option to the above command will
format the same metadata in a XML document.
The output is not shown in this page because of its verbosity.</p>
+<p>Java methods for accessing functionalities shown in above examples are:</p>
+<ul>
+<li>Convenience static methods in <code>org.apache.sis.xml</code> package:<ul>
+<li><code>XML.marshal(â¦)</code></li>
+<li><code>XML.unmarshal(â¦)</code></li>
+</ul>
+</li>
+<li>Class in other package (less convenient but give more control):<ul>
+<li><code>org.apache.sis.xml.MarshallerPool</code></li>
+</ul>
+</li>
+</ul>
<h1 id="performance">Performance consideration<a class="headerlink"
href="#performance" title="Permanent link">¶</a></h1>
<p>If there is a large amount of files to process, invoking the above command
many time may be inefficient
since it would restart a new JVM on every invocation.
Added:
websites/staging/sis/trunk/content/examples/coordinates/AmericanCities.csv
==============================================================================
--- websites/staging/sis/trunk/content/examples/coordinates/AmericanCities.csv
(added)
+++ websites/staging/sis/trunk/content/examples/coordinates/AmericanCities.csv
Tue May 24 01:11:50 2016
@@ -0,0 +1,27 @@
+#
+# Coordinates of some cities in USA. The coordinates are given
+# with only 3 significant digits, which implies an uncertainty
+# of more than 100 metres. With such uncertainty, it does not
+# matter if the geodetic datum is WGS84, NAD83 or NAD27 since
+# the error is greater than the difference between those datums.
+#
+# Axis order is latitude first, then longitude. Units are degrees.
+#
+
+# San-Francisco
+37.783, -122.417
+
+# New-York
+40.713, -74.006
+
+# Los Angeles
+34.050, -118.250
+
+# Houston
+29.763, -95.383
+
+# Chicago
+41.837, -87.685
+
+# Miami
+25.775, -80.209
Added:
websites/staging/sis/trunk/content/examples/coordinates/CanadianCities.csv
==============================================================================
--- websites/staging/sis/trunk/content/examples/coordinates/CanadianCities.csv
(added)
+++ websites/staging/sis/trunk/content/examples/coordinates/CanadianCities.csv
Tue May 24 01:11:50 2016
@@ -0,0 +1,27 @@
+#
+# Coordinates of some cities in Canada. The coordinates are given
+# with only 3 significant digits, which implies an uncertainty of
+# more than 100 metres. With such uncertainty, it does not matter
+# if the geodetic datum is WGS84, NAD83 or NAD27 since the error
+# is greater than the difference between those datums.
+#
+# Axis order is latitude first, then longitude. Units are degrees.
+#
+
+# Vancouver
+49.250, -123.100
+
+# Toronto
+43.700, -79.400
+
+# Montreal
+45.500, -73.567
+
+# Regina
+50.455, -104.607
+
+# Saskatoon
+52.133, -106.683
+
+# St. John's
+47.568, -52.707
Added: websites/staging/sis/trunk/content/examples/crs/EquivalentDefinition.wkt
==============================================================================
--- websites/staging/sis/trunk/content/examples/crs/EquivalentDefinition.wkt
(added)
+++ websites/staging/sis/trunk/content/examples/crs/EquivalentDefinition.wkt
Tue May 24 01:11:50 2016
@@ -0,0 +1,16 @@
+PROJCRS["Scaled Mercator",
+ BASEGEODCRS["WGS 84",
+ DATUM["World Geodetic System 1984",
+ ELLIPSOID["WGS 84", 6378137.0, 298.257223563]],
+ UNIT["degree", 0.017453292519943295]],
+ CONVERSION["Scaled Mercator",
+ METHOD["Mercator (variant A)"],
+ PARAMETER["Scale factor at natural origin", 0.7557992272019596],
+ PARAMETER["Latitude of natural origin", -0.0],
+ PARAMETER["Longitude of natural origin", 100.0]],
+ CS[Cartesian, 2],
+ AXIS["Easting (X)", east],
+ AXIS["Northing (Y)", north],
+ UNIT["metre", 1],
+ BBOX[-60.00, 155.00, -25.00, -170.00],
+ REMARK["This CRS is numerically equivalent to EPSG:3994 but defined as a
Mercator variant A instead of B. This example can be used for testing Apache
SIS capability to detect map projection equivalence."]]
Added: websites/staging/sis/trunk/content/examples/crs/MissingIdentifier.wkt
==============================================================================
--- websites/staging/sis/trunk/content/examples/crs/MissingIdentifier.wkt
(added)
+++ websites/staging/sis/trunk/content/examples/crs/MissingIdentifier.wkt Tue
May 24 01:11:50 2016
@@ -0,0 +1,21 @@
+PROJCRS["NTF (Paris) / zone to be discovered by the demo",
+ BASEGEODCRS["NTF (Paris)",
+ DATUM["Nouvelle Triangulation Francaise",
+ ELLIPSOID["Clarke 1880 (IGN)", 6378249.2, 293.4660212936269]],
+ PRIMEM["Paris", 2.5969213],
+ UNIT["grade", 0.015707963267948967]],
+ CONVERSION["Lambert zone II",
+ METHOD["Lambert Conic Conformal (1SP)"],
+ PARAMETER["Latitude of natural origin", 52.0],
+ PARAMETER["Longitude of natural origin", 0.0],
+ PARAMETER["Scale factor at natural origin", 0.99987742],
+ PARAMETER["False easting", 600000.0],
+ PARAMETER["False northing", 2200000.0]],
+ CS[Cartesian, 2],
+ AXIS["Easting (E)", east],
+ AXIS["Northing (N)", north],
+ LENGTHUNIT["metre", 1],
+ SCOPE["Large and medium scale topographic mapping and engineering survey."],
+ AREA["France mainland onshore between 50.5 grads and 53.5 grads North."],
+ BBOX[42.33, -4.87, 51.14, 8.23],
+ REMARK["In this example, the EPSG:27572 identifier has been intentionally
omitted. This example can be used for testing Apache SIS capability to retrieve
the identifier by comparing the CRS with the definitions found in the EPSG
database."]]
Added: websites/staging/sis/trunk/content/examples/crs/WrongAxisOrder.wkt
==============================================================================
--- websites/staging/sis/trunk/content/examples/crs/WrongAxisOrder.wkt (added)
+++ websites/staging/sis/trunk/content/examples/crs/WrongAxisOrder.wkt Tue May
24 01:11:50 2016
@@ -0,0 +1,12 @@
+GEODCRS["WGS 84 (longitude, latitude, height)",
+ DATUM["World Geodetic System 1984",
+ ELLIPSOID["WGS 84", 6378137.0, 298.257223563]],
+ CS[ellipsoidal, 3],
+ AXIS["Longitude (L)", east, Unit["degree", 0.017453292519943295]],
+ AXIS["Latitude (B)", north, Unit["degree", 0.017453292519943295]],
+ AXIS["Ellipsoidal height (h)", up, Unit["metre", 1]],
+ SCOPE["Used by the GPS satellite navigation system."],
+ AREA["World."],
+ BBOX[-90.00, -180.00, 90.00, 180.00],
+ ID["EPSG", 4979, "8.9", URI["urn:ogc:def:crs:EPSG:8.9:4979"]],
+ REMARK["THIS IS NOT A VALID EPSG:4979 CRS! The two first axes have been
intentionally swapped. This example can be used for testing Apache SIS
capability to detect wrong axis order."]]
Modified: websites/staging/sis/trunk/content/index.html
==============================================================================
--- websites/staging/sis/trunk/content/index.html (original)
+++ websites/staging/sis/trunk/content/index.html Tue May 24 01:11:50 2016
@@ -122,11 +122,14 @@ The SIS storage modules will provide a c
<p>The latest SIS release is 0.7, released May 2016.
Apache SIS requires a Java 6 Runtime Environment.
The EPSG geodetic dataset (optional but recommended) can be <a
href="epsg.html">installed separately</a>.</p>
+<p>Apache SIS is a Java library for use by other applications.
+Leveraging the full SIS capabilities or getting the best performance require
that users write their own applications on top of SIS.
+However a command-line tool is provided for allowing users to experiment some
SIS functionalities before writing code.</p>
<ul>
<li><a href="downloads.html">Downloads</a> as a <code>zip</code> files, or as
Maven dependencies.</li>
<li>Developer guide (<a href="book/en/developer-guide.html">English</a> | <a
href="book/fr/developer-guide.html">French</a>) â note that this is work in
progress.</li>
<li><a href="apidocs/index.html">Online Javadoc</a> for API documentation.</li>
-<li><a href="command-line.html">Command-line interface</a> for an overview of
a command-line tool.</li>
+<li><a href="command-line.html">Command-line interface</a> for an overview of
the command-line tool.</li>
<li><a href="http://cwiki.apache.org/confluence/display/SIS";>SIS Wiki</a> for
"drawing board" and roadmap.</li>
<li><a href="code-patterns.html">Recommended code patterns</a> for writing
more robust applications.</li>
</ul>
