Changes between Version 100 and Version 101 of PetascopeUserGuide


Ignore:
Timestamp:
Jul 9, 2015 4:29:09 PM (23 months ago)
Author:
pbaumann
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PetascopeUserGuide

    v100 v101  
    1010Internally, incoming requests requiring coverage evaluation are translated into rasql queries by petascope. These queries are passed on to rasdaman, which constitutes the central workhorse. Results returned from rasdaman are forwarded to the client, finally.
    1111
    12 Starting from release 9.0, Petascope is ''dependent'' on a [SecoreUserGuide SECORE] Coordinate Reference System (CRS) resolver that can provide proper metadata on, indeed, coverage's native CRSs. One could either [SecoreDevGuide deploy] a local SECORE instance, or use the official [http://external.opengeospatial.org/twiki_public/CRSdefinitionResolver OGC SECORE resolver] (`http://www.opengis.net/def/crs/`). CRS resources are identified then by HTTP URIs, following the related [http://portal.opengeospatial.org/files/40077 OGC policy document] of 2011, based on the White Paper [http://portal.opengeospatial.org/files/?artifact_id=39467 'OGC Identifiers – the case for http URIs'].  These HTTP URIs must resolve to GML resources that describe the CRS, such as [http://kahlua.eecs.jacobs-university.de:8080/def/crs/EPSG/0/27700] that themselves contain only resolvable HTTP URIs pointing to additional definitions within the CRS; so for example [http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::27700] is not allowed because, though it is a resolvable HTTP URI pointing at a GML resource that describes the CRS, internally it uses URNs which SECORE is unable to resolve.
     12Starting from release 9.0, Petascope is ''dependent'' on a [SecoreUserGuide SECORE] Coordinate Reference System (CRS) resolver that can provide proper metadata on, indeed, coverage's native CRSs. One could either [SecoreDevGuide deploy] a local SECORE instance, or use the official [http://external.opengeospatial.org/twiki_public/CRSdefinitionResolver OGC SECORE resolver] (`http://www.opengis.net/def/crs/`). CRS resources are identified then by HTTP URIs, following the related [http://portal.opengeospatial.org/files/40077 OGC policy document] of 2011, based on the White Paper [http://portal.opengeospatial.org/files/?artifact_id=39467 'OGC Identifiers – the case for http URIs'].  These HTTP URIs must resolve to GML resources that describe the CRS, such as [http://rasdaman.org:8080/def/crs/EPSG/0/27700] that themselves contain only resolvable HTTP URIs pointing to additional definitions within the CRS; so for example [http://www.epsg-registry.org/export.htm?gml=urn:ogc:def:crs:EPSG::27700] is not allowed because, though it is a resolvable HTTP URI pointing at a GML resource that describes the CRS, internally it uses URNs which SECORE is unable to resolve.
    1313
    1414==== Related Pages ====
     
    161161Concrete CRS definitions are a static XML tree of GML elements defining axis, geographic coordinate systems, datums, and so on. The candidate standard [http://www.ogcnetwork.net/system/files/11-135_OGC-NA_Name-Type-Specification-for-CRSs_2012-08-07.pdf OGC CRS Name-Type Specification] offers a new kind of CRS, a [SecoreUserGuide parametrized CRS], which can be bound to a concrete definition, a CRS ''template'', and which offers customization of one or more GML elements directly via key-value pairs in the query component of HTTP URL identifying the CRS.
    162162
    163 As a practical example, we propose the complete XML definition of the parametrized CRS defining ANSI dates, identified by the URI http://kahlua.eecs.jacobs-university.de:8080/def/crs/OGC/0/AnsiDate:
     163As a practical example, we propose the complete XML definition of the parametrized CRS defining ANSI dates, identified by the URI http://rasdaman.org:8080/def/crs/OGC/0/AnsiDate:
    164164
    165165{{{
     
    167167<ParameterizedCRS xmlns:gml="http://www.opengis.net/gml/3.2" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.opengis.net/CRS-NTS/1.0" xmlns:epsg="urn:x-ogp:spec:schema-xsd:EPSG:1.0:dataset" xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0" gml:id="param-ansi-date-crs">
    168168  <description>Parametrized temporal CRS of days elapsed from 1-Jan-1601 (00h00 UTC).</description>
    169   <gml:identifier codeSpace="http://www.ietf.org/rfc/rfc3986">http://kahlua.eecs.jacobs-university.de:8080/def/crs/OGC/0/AnsiDate</gml:identifier>
     169  <gml:identifier codeSpace="http://www.ietf.org/rfc/rfc3986">http://rasdaman.org:8080/def/crs/OGC/0/AnsiDate</gml:identifier>
    170170  <parameters>
    171171    <parameter name="axis-label">
     
    174174    </parameter>
    175175  </parameters>
    176   <targetCRS xlink:href="http://kahlua.eecs.jacobs-university.de:8080/def/crs/OGC/0/.AnsiDate-template"/>
     176  <targetCRS xlink:href="http://rasdaman.org:8080/def/crs/OGC/0/.AnsiDate-template"/>
    177177</ParameterizedCRS>
    178178}}}
    179179
    180 This single-parameter definition allow the customization of the concrete CRS ''template'' `OGC:.AnsiDate-template` (identified by http://kahlua.eecs.jacobs-university.de:8080/def/crs/OGC/0/.AnsiDate-template) on its unique axis label (`crsnts:parameter/crsnts:target`), via a parameter labeled `axis-label`, and default value `ansi`.
     180This single-parameter definition allow the customization of the concrete CRS ''template'' `OGC:.AnsiDate-template` (identified by http://rasdaman.org:8080/def/crs/OGC/0/.AnsiDate-template) on its unique axis label (`crsnts:parameter/crsnts:target`), via a parameter labeled `axis-label`, and default value `ansi`.
    181181
    182182This way, when we assign this parametrized CRS to a coverage, we can either leave the default `ansi` label to the time axis, or change it to some other value by setting the parameter in the URL query:
    183183
    184    * default `ansi` axis label: http://kahlua.eecs.jacobs-university.de:8080/def/crs/OGC/0/AnsiDate
    185    * custom `ansi_date` axis label: [http://kahlua.eecs.jacobs-university.de:8080/def/crs/OGC/0/AnsiDate?axis-label="ansi_date" http://kahlua.eecs.jacobs-university.de:8080/def/crs/OGC/0/AnsiDate?axis-label="ansi_date"]
     184   * default `ansi` axis label: http://rasdaman.org:8080/def/crs/OGC/0/AnsiDate
     185   * custom `ansi_date` axis label: [http://rasdaman.org:8080/def/crs/OGC/0/AnsiDate?axis-label="ansi_date" http://rasdaman.org:8080/def/crs/OGC/0/AnsiDate?axis-label="ansi_date"]
    186186
    187187=== 0-dimensional grids ===
     
    488488   * '''OGC 09-045:''' This draft document defines the embedding of WCPS into WPS as an application profile by specifying a concrete subtype of the ''Execute'' request type.
    489489
    490 There is a [http://kahlua.eecs.jacobs-university.de/~earthlook/tech/wcps-tutorial/sandbox-abs.php demo sandbox] and [http://kahlua.eecs.jacobs-university.de/~earthlook/videos/index.php demo video]; see also the [http://www.earthlook.org/tech/interface-wcps.php WCPS manual and tutorial].
     490There is a [http://rasdaman.org/~earthlook/tech/wcps-tutorial/sandbox-abs.php demo sandbox] and [http://rasdaman.org/~earthlook/videos/index.php demo video]; see also the [http://www.earthlook.org/tech/interface-wcps.php WCPS manual and tutorial].
    491491
    492492The ''Petascope'' implementation supports both XML and Abstract Syntax. You can use `http://your.server/rasdaman/ows/wcps` as service endpoints to which to send WCPS requests.