Changes between Version 90 and Version 91 of PetascopeUserGuide


Ignore:
Timestamp:
Jun 6, 2014 12:36:24 PM (3 years ago)
Author:
mase
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PetascopeUserGuide

    v90 v91  
    118118
    119119When importing a coverage, a [http://www.researchgate.net/publication/237148512_Making_Time_Just_Another_Axis_in_Geospatial_Services/file/504635264eb4a97d90.pdf spatio-temporal CRS] needs to be assigned to it, in order to give a meaning to its domain. Composition of CRSs is possible via the OGC [http://link.springer.com/chapter/10.1007%2F978-3-642-29247-7_5 SECORE] CRS resolver. For instance a time-series of WGS84 images can have the following native CRS: `http://<secore-resolverX-domain>/def/crs-compound?1=http://<secore-resolverY-domain>/def/crs/EPSG/0/4326&2=http://<secore-resolverZ-domain>/def/crs/<AUTH>/<VERSION>/<CODE-OF-A-TIME-CRS>`
     120
     121Note: currently gml:CompoundCRS is not supported (#679) so, for example, `http://www.opengis.net/def/crs/EPSG/0/7415` would have to be represented by composing its components using the same format as above i.e. `http://<secore-resolverX-domain>/def/crs-compound?1=http://www.opengis.net/def/crs/EPSG/0/28992&2=http://www.opengis.net/def/crs/EPSG/0/5709`
    120122
    121123In order to verify the CRS assigned to a coverage offered by Petascope, there are several ways: i) check the `wcs:CoverageSummary/ows:BoundingBox@crs` attribute in a WCS ''!GetCapabilities'' response; ii) check the `@srsName` attribute in the `@{gml:SRSReferenceGroup}` attributes group in WCS ''!DescribeCoverage'' response (`gml:domainSet`); iii) use the WCPS function `crsSet(<coverage_name>)`; iv) directly check the metadata database: `petascopedb=# SELECT * FROM getCrs('<coverage_name>')`.