py wps301whatsnewwhatsnext

13
PyWPS 3.1.0: what’s new, what’s next Release Jachym Cepicky September 17, 2009

Upload: jachym-cepicky

Post on 10-May-2015

417 views

Category:

Technology


0 download

TRANSCRIPT

Page 1: Py wps301whatsnewwhatsnext

PyWPS 3.1.0: what’s new, what’s nextRelease

Jachym Cepicky

September 17, 2009

Page 2: Py wps301whatsnewwhatsnext
Page 3: Py wps301whatsnewwhatsnext

CONTENTS

1 PyWPS 3.1.0 31.1 Support on MS Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.2 New JavaScript (OpenLayers-based) generic WPS client . . . . . . . . . . . . . . . . . . . . . . . . 31.3 Bugfixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.4 Updated examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.5 Example usage: INSPIRE Transformation service . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 What’s going to be developed 52.1 WSDL and SOAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.2 WPS 2.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Fin 74 Indices and tables 9

i

Page 4: Py wps301whatsnewwhatsnext

ii

Page 5: Py wps301whatsnewwhatsnext

PyWPS 3.1.0: what’s new, what’s next, Release

PyWPS (Python Web Processing Service) is an implementation of the Web processing Service standard from OpenGeospatial Consortium.

It has been started in Mai 2006 as a project supported by DBU and is currently (2009) mainly sponsored by HS-RS.It offers an environment for programming own processes (geofunctions or models) which can be accessed from thepublic. The main advantage of PyWPS is, that it has been written with native support for GRASS GIS. Access toGRASS modules via web interface should be as easy as possible.

2009-06-01 PyWPS 3.1.0

Contents:

CONTENTS 1

Page 6: Py wps301whatsnewwhatsnext

PyWPS 3.1.0: what’s new, what’s next, Release

2 CONTENTS

Page 7: Py wps301whatsnewwhatsnext

CHAPTER

ONE

PYWPS 3.1.0

What’s new in PyWPS 3.1.0

1.1

Currently is is not possible to run PyWPS in asynchronous mode

pywps/Wps/Execute.py:

194 try:195 # this is the parent process196 if os.fork():197 # exit here198 return199 # this is the child process200 else:201 # continue execution202 pass

We have to use the subprocess module.

Tested on Windows XP SP2 and OSGeo4Win package.

1.2

var wps = new OpenLayers.WPS("http://foo/bar/wps", ....);wps.getCapabilities();

...

wps.describeProcess("someProcess");

...

someProcess.getInput("someIdentifier").setValue("something");someProcess.assync = true;wps.execute("someProcess");

3

Page 8: Py wps301whatsnewwhatsnext

PyWPS 3.1.0: what’s new, what’s next, Release

1.3

About 40 bugs fixed, in Templates, program code, fixes for MS Windows, ...

1.4

Ready-to-use examples of processes in doc/examples/processes.

1.5

INSPIRE Draft Implementing rule for Transformation Service

• GML 3.1.x

• WFS 2.x

• ...HS-RS Transformation Service

4 Chapter 1. PyWPS 3.1.0

Page 9: Py wps301whatsnewwhatsnext

CHAPTER

TWO

WHAT’S GOING TO BE DEVELOPED

2.1According to WPS 1.0.0, the server should (optionally) support WSDL and SOAP interfaces. The SOAP is onlyenvelop to existing request types (GetCapabilities, DescribeProcess, Execute).

PyWPS trunk currently supports basic WSDL and SOAP interfaces.:

<?xml version="1.0" encoding="UTF-8"?><!-- WPS GetCapabilities request encoded in SOAP --><!-- Equivalent GET request is http://foo.bar/foo?Service=WPS&Version=1.0.0&Request=GetCapabilities&Language=en-CA --><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xmlns:xsd="http://www.w3.org/2001/XMLSchema"xsi:schemaLocation="http://www.w3.org/2003/05/soap-envelopehttp://www.w3.org/2003/05/soap-envelope"><soap:Body>

<GetCapabilities xmlns="http://www.opengis.net/wps/1.0.0"xmlns:ows="http://www.opengis.net/ows/1.1" xmlns:xlink="http://www.w3.org/1999/xlink"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.opengis.net/wps/1.0.0 ../wpsGetCapabilities_request.xsd"language="en-CA" service="WPS"><AcceptVersions>

<ows:Version>1.0.0</ows:Version></AcceptVersions>

</GetCapabilities></soap:Body>

</soap:Envelope>

2.2

Changes in WPS standard are going to be implemented.

2.2.1

During the first teleconference the group decided to create separate procedures for each state change:

• pause -> pauseProcess

• resume -> resumeProcess

5

Page 10: Py wps301whatsnewwhatsnext

PyWPS 3.1.0: what’s new, what’s next, Release

• cancel -> cancelProcess

2.2.2

Instead of observing given URL

2.2.3

• Eliminate the Service, Version, Request, and Identifier request parameters.

• Eliminate the double URL encoding required for DataInputs, ResponseDocument, and RawDataOutput

• Merge the DescribeProcess with the Execute operation

• Repeat selected contents of the Capabilities response with the DescribeProcess response

6 Chapter 2. What’s going to be developed

Page 11: Py wps301whatsnewwhatsnext

CHAPTER

THREE

FIN

Jachym Cepicky

Help Service - Remote Sensing [email protected]://les-ejk.cz/,http://pywps.wald.intevation.org

7

Page 12: Py wps301whatsnewwhatsnext

PyWPS 3.1.0: what’s new, what’s next, Release

8 Chapter 3. Fin

Page 13: Py wps301whatsnewwhatsnext

CHAPTER

FOUR

INDICES AND TABLES

• Index

• Module Index

• Search Page

9