Changes between Version 102 and Version 103 of PetascopeUserGuide


Ignore:
Timestamp:
Dec 30, 2015 2:30:20 PM (21 months ago)
Author:
pbaumann
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PetascopeUserGuide

    v102 v103  
    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://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.
     12== Petascope servlet endpoints ==
     13
     14Once the petascope servlet is deployed (see installation guide]), the following service endpoints are available:
     15 * `/rasdaman` : context path
     16    * `./ows` : serving OGC Web Services (OWS) like WCS, WCPS and WCS-T:
     17       * `./wcs`'       * `./wcps` (deprecated; use {{{rasdaman/ows?SERVICE=WCS&REQUEST=ProcessCoverages&...}}} instead)
     18       * `./wms`
     19    * `./rasql` : direct RasQL.
     20For example, assuming that the service's IP address is `123.456.789.1` and the service port is `8080`, the following request URLs would deliver the Capabilities documents for OGC WMS and WCS, respectively:
     21{{{
     22http://123.456.789.1:8080/rasdaman/ows?SERVICE=WMS&REQUEST=GetCapabilities
     23http://123.456.789.1:8080/rasdaman/ows?SERVICE=WCS&REQUEST=GetCapabilities
     24}}}
     25
     26== Coordinate Reference System (CRS) handling ==
     27
     28Petascope relies 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.
    1329
    1430==== Related Pages ====