Changes between Version 6 and Version 7 of IndexCrss

Timestamp:

Feb 27, 2014, 2:40:26 PM (11 years ago)

Author:

Piero Campalani

Comment:

parametrizations

IndexCrss

@@ +1 @@
+[[TOC]]
+
 = Index CRSs 
 
@@ -59 +61 @@
 
 
-== Change label of the axes
+== Changing axis labels
 
-TBD
-Parametrized
+A final section is dedicated to the customization of axis label when using an Index CRS. This can be useful when migrating existing application to 9.x releases. Prior versions of `rasdaman` do not support index CRSs.
+
+The management of CRSs metadata was usually done ''in house'', with default axis labels to `x`, `y`, `z`, `t`, and so on, independently of the native CRS assigned to a coverage. The outsourcing of CRS metadata handling to the [SecoreUserGuide SECORE] resolver (official [http://external.opengeospatial.org/twiki_public/CRSdefinitionResolver/WebHome OGC resolver] for CRS related resources) imposes less freedom on the choice of axis labels on one hand (you have to use the official abbreviations), while developing a more transparent and more ruled framework.
+
+While geodetic reference systems from [http://www.epsg-registry.org/ EPSG] are not customizable (let's say they are read-only CRSs), our index CRSs (and as well [PetascopeTimeHandling time] ones) are constructed by splitting each concept into a ''template'' and a ''parametrization'' of the template. 
+
+Indeed you can see in our resolver that every `OGC:Index`''n''`D` CRS is associated with its template `OGC:.Index`''n''`D-template`, the latter being the template and the former being its parametrization. You can notice the period `.` prefix in the templates CRS code, which (like in unix file systems) denotes an hidden resource: indeed users shall not reference the templates when setting the native CRS (URI) to a coverage, but rather always use the parametrizations. A Parametrized CRS (P-CRS) is like piggy-backed on a template: it provides one or more parameters to the enduser for customizing the content of the template ''target'' CRS definition. Parameters are set by the user by means of key-value pairs in the query of a URI.
+
+When default values for all the parameters offered by a P-CRS, then querying the P-CRS URI without any query part (`?key=value[&key=value[&...]]`) is doable: the template resource is returned (that is, the template resource where parameters values have been set to their defaults defined in the P-CRS), and the user can blissfully ignore the (relative) complexities of parametrization.
+
+Our index CRSs indeed are P-CRSs with parameters to customize the labels of the axes, which by default are `i`, `j` and `k` (4+ dimensinal index CRSs are yet to be defined).
+This was also due to the necessity to avoid label clashes when 2+ index CRSs of the same kind are used within the same coverage.
+
+If a P-CRS is requested with no subelement expansion (see #364), then the behind-the-scenes definition of a P-CRS can be visualized.
+For instance, our `OGC:Index1D` CRS is:
+
+{{{
+#!xml
+<ParameterizedCRS gml:id="param-index1d-crs"
+                   xmlns="http://www.opengis.net/crs-nts/1.0"
+               xmlns:gml="http://www.opengis.net/gml/3.2" 
+             xmlns:xlink="http://www.w3.org/1999/xlink">
+  <gml:identifier codeSpace="http://www.ietf.org/rfc/rfc3986">
+    http://kahlua.eecs.jacobs-university.de:8080/def/crs/OGC/0/Index2D
+  </gml:identifier>
+  <parameters>
+    <parameter name="first-axis-label">
+      <value>"i"</value>
+      <target>//gml:CartesianCS/gml:axis[1]/gml:CoordinateSystemAxis/gml:axisAbbrev</target>
+    </parameter>
+    <parameter name="second-axis-label">
+      <value>"j"</value>
+      <target>//gml:CartesianCS/gml:axis[2]/gml:CoordinateSystemAxis/gml:axisAbbrev</target>
+    </parameter>
+  </parameters>
+  <targetCRS xlink:href="http://kahlua.eecs.jacobs-university.de:8080/def/crs/OGC/0/.Index2D-template"/>
+</ParameterizedCRS>
+}}}
+
+The content is sufficiently intuitive to understand that it provides two parameters -- `'first-axis-label'` and `'second-axis-label'` -- with defaults to `'i'` and `'j'`, respectively.
+Thus if we want to use index CRSs but with the ''good old'' `x`/`y` labels, we need to set this URI as native reference system: [http://kahlua.eecs.jacobs-university.de:8080/def/crs/OGC/0/Index2D?first-axis-label=%22x%22&second-axis-label=%22y%22 http://kahlua.eecs.jacobs-university.de:8080/def/crs/OGC/0/Index2D?first-axis-label="x"&second-axis-label="y"].