Version 2 (modified by pbaumann, 7 years ago) (diff)


Petascope User guide

Petascope is implemented as a war file of servlets which give access to coverages (in the OGC sense) stored in rasdaman.

Internally, 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.

For this purpose, petascope needs additional metadata (such as georeferencing) which is maintained in separate relational tables. Note that not all rasdaman raster objects and collections are available through petascope by default; rather, they need to be registered through the petascope administration interface.

For installation, this war file needs to be deployed and configured for use with some rasdaman server installation. See the installation section? for details.

Currently, petascope offers interfaces according to WCS 1.1, WCPS 1.0, WCS-T 1.4, and WPS 1.0. These are described below.


(see also WCPS manual and tutorial)

The WCPS service can handle most of the operations specified in the WCPS specification document. It can answer both XML and Abstract Syntax queries. The servlet will always respond to a GET request with a user friendly form for entering a query along with a greeting message. To send a query a post request must be sent. Two protocols are supported, XML (with two sub-variants) and Abstract Syntax:

  • To send a abstract syntax request: A post request must be sent. The query string must be sent in a post parameter named query.
  • To send a request as a XML file, a multi-part post request must be sent. Only one file must be sent. The Mime type has to be text/xml.
  • To send a request as XML: A post request must be sent. A post parameter named xml must be attached.

If you intend to implement forms-based access:

To obtain a proper query from an XML page a form must be used. The method should be post and action should be an URL pointing to the servlet access point. The form should contain either a file field or a text/hidden field that has the name xml or query. An error in the access method will generate the same user friendly form and greeting message as for the GET request. For a simple example check the reply you get from accessing the service check the user friendly form obtained by a GET request.


See the WCS standards for the moment being; further documentation to come.

Attachments (1)

Download all attachments as: .zip