Author: buildbot Date: Thu Nov 23 23:16:05 2017 New Revision: 1021272 Log: Staging update by buildbot for sis Modified: websites/staging/sis/trunk/content/ (props changed) websites/staging/sis/trunk/content/gdal.html websites/staging/sis/trunk/content/index.html Propchange: websites/staging/sis/trunk/content/ ------------------------------------------------------------------------------ --- cms:source-revision (original) +++ cms:source-revision Thu Nov 23 23:16:05 2017 @@ -1 +1 @@ -1816137 +1816195 Modified: websites/staging/sis/trunk/content/gdal.html ============================================================================== --- websites/staging/sis/trunk/content/gdal.html (original) +++ websites/staging/sis/trunk/content/gdal.html Thu Nov 23 23:16:05 2017 @@ -94,9 +94,10 @@ } h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }
While Apache SIS provides its own map projection engine, some applications may want to also use the Proj.4 library. -It may be for using map projection methods not yet supported by Apache SIS, or for getting the exact same numerical -results than Proj.4. The two libraries can coexist and can be used through the same API, -provided that following prerequisites are meet.
+One reason may be to use map projection methods not yet supported by Apache SIS, +or for getting the exact same numerical results than Proj.4. +The two libraries can coexist and can be used through the same API, +provided that prerequisites are meet.Everything after "PROJ4::"
is forwarded as-is to the Proj.4 library.
-Note that despite the "epsg"
part in above definition string, CRS created by above method call is not
-conform to EPSG:4326 authoritative definition. It should rather be understood as a Proj.4-specific code.
+Note that despite the "epsg"
part in above definition string, the CRS created by above method call is not
+conform to EPSG:4326 authoritative definition. The string should rather be understood as a Proj.4-specific code.
Proj.4 definitions may differ from authoritative definitions in axis order, axis directions or units of measurement.
To get the authoritative definition, use CRS.forCode("EPSG::4326")
instead.
For creating a coordinate operation backed by Proj.4, there is nothing special to do;
we can invoke the same method regardless if the CRS are backed by Proj.4 or Apache SIS.
The following code will create a transform backed by Proj.4 if both sourceCRS
and targetCRS
-were created with CRS.forCode("Proj4::â¦")
calls.
CRS.forCode("Proj4::â¦")
calls.
+Note however that CoordinateOperation
backed by Proj.4 does not provide metadata about accuracy or domain of validity.
CoordinateOperation op = CRS.findOperation(sourceCRS, targetCRS, null); MathTransform mt = op.getMathTransform(); DirectPosition sourcePt = new DirectPosition2D(x, y); Modified: websites/staging/sis/trunk/content/index.html ============================================================================== --- websites/staging/sis/trunk/content/index.html (original) +++ websites/staging/sis/trunk/content/index.html Thu Nov 23 23:16:05 2017 @@ -114,7 +114,7 @@ The SIS storage modules will provide a c See the list of supported coordinate reference systems.