Py wps301whatsnewwhatsnext
0 likes333 views
PyWPS 3.1.0 includes several new features and bug fixes. It adds support for Windows, a new JavaScript WPS client, fixes over 40 bugs, and updates examples. Future plans include implementing WPS 2.0 specifications like controlling asynchronous processes and adding a status method. It will also simplify the KVP encoding.
Py wps301whatsnewwhatsnext
- 1. PyWPS 3.1.0: what’s new, what’s next Release Jachym Cepicky September 17, 2009
- 3. CONTENTS 1 PyWPS 3.1.0 3 1.1 Support on MS Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.2 New JavaScript (OpenLayers-based) generic WPS client . . . . . . . . . . . . . . . . . . . . . . . . 3 1.3 Bugfixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.4 Updated examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.5 Example usage: INSPIRE Transformation service . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2 What’s going to be developed 5 2.1 WSDL and SOAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.2 WPS 2.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3 Fin 7 4 Indices and tables 9 i
- 4. ii
- 5. 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 Open Geospatial 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 the public. The main advantage of PyWPS is, that it has been written with native support for GRASS GIS. Access to GRASS modules via web interface should be as easy as possible. 2009-06-01 PyWPS 3.1.0 Contents: CONTENTS 1
- 6. PyWPS 3.1.0: what’s new, what’s next, Release 2 CONTENTS
- 7. CHAPTER ONE PYWPS 3.1.0 What’s new in PyWPS 3.1.0 1.1 Support on MS Windows Currently is is not possible to run PyWPS in asynchronous mode pywps/Wps/Execute.py: 194 try: 195 # this is the parent process 196 if os.fork(): 197 # exit here 198 return 199 # this is the child process 200 else: 201 # continue execution 202 pass We have to use the subprocess module. Tested on Windows XP SP2 and OSGeo4Win package. 1.2 New JavaScript (OpenLayers-based) generic WPS client 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
- 8. PyWPS 3.1.0: what’s new, what’s next, Release 1.3 Bugfixes About 40 bugs fixed, in Templates, program code, fixes for MS Windows, ... 1.4 Updated examples Ready-to-use examples of processes in doc/examples/processes. 1.5 Example usage: INSPIRE Transformation service 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
- 9. CHAPTER TWO WHAT’S GOING TO BE DEVELOPED 2.1 WSDL and SOAP According to WPS 1.0.0, the server should (optionally) support WSDL and SOAP interfaces. The SOAP is only envelop 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&L <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-envelope http://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/199 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/wps/1.0.0 ../wpsGetCapabilities_re language="en-CA" service="WPS"> <AcceptVersions> <ows:Version>1.0.0</ows:Version> </AcceptVersions> </GetCapabilities> </soap:Body> </soap:Envelope> 2.2 WPS 2.0.0 Changes in WPS standard are going to be implemented. 2.2.1 CR 09-093 -WPS Change Request - Controlling Asynchronous Process During the first teleconference the group decided to create separate procedures for each state change: • pause -> pauseProcess • resume -> resumeProcess 5
- 10. PyWPS 3.1.0: what’s new, what’s next, Release • cancel -> cancelProcess 2.2.2 Change Request Summary - Add “Get Status Method” Instead of observing given URL 2.2.3 CR09-107 - Simplify KVP Encoding • 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
- 11. CHAPTER THREE FIN Jachym Cepicky Help Service - Remote Sensing s.r.o. jachym.cepicky@gmail.com http://les-ejk.cz/, http://www.bnhelp.cz http://pywps.wald.intevation.org 7
- 12. PyWPS 3.1.0: what’s new, what’s next, Release 8 Chapter 3. Fin
- 13. CHAPTER FOUR INDICES AND TABLES • Index • Module Index • Search Page 9