What is PyWPS
• PyWPS is an implementation of the Web Processing Service
standard from the Open Geospatial Consortium
• PyWPS is written in Python
• Started in the Spring of 2006
• Supports all available tools in Python for geospatial operations
What PyWPS is NOT
• a client
• a GUI
• a server with pre-installed processes
The OGC Web Processing Service
• OGC open web standard for remote geo-spatial processing.
• Integrated with web data services: WFS, WCS.
• Three basic requests:
• Three basic input/output classes:
• Complex - for geo-spatial data and services
• BouningBox - for geo-spatial data extent
The OGC Web Processing Service
Essential PyWPS Functionality
• Communication bridge with WPS.
• Fetches input data referenced in Execute requests.
• Creates a container for the process instance.
• Manage processes: communication, reporting, logging.
• Data storage for final data outputs.
• Client notification, status reporting
• Jachym Cepicky starts working on a project to link GRASS with UMN
• Scholarship funded by the German Foundation for Environment.
• September: PyWPS is presented at FOSS4G 2006.
• October: Project homepage hosted by Intevation GmbH.
• November: Version 1.0.0 is released; other developers join the
2007 - 2010
• Version 2.0.0 released in October of 2007
• Introduced the Process class;
• WPS plugin for OpenLayers;
• Improved stability.
• Version 3.0.0 released in November of 2008
• New implementation of the WPS 1.0.0 standard.
• The WPS Cookbook is published.
• A deliverable of the NETMAR project.
• Introduces the WPS standard.
• Presents PyWPS as implementation.
• Still today a valuable introduction to WPS.
• Practical examples of SOAP envelopes and Taverna
Workflow management system
• Staple GIS software in Industry and Academia.
• PyWPS featuring regularly in scientific publications.
• 2013 FOSS4G-CEE:
• New implementation starts being discussed;
• First lines of code are written.
• 2014 WPS Workshop organised by the Luxembourg Institute of
Science and Technology (LIST):
• Broad architecture for PyWPS-4 devised;
• Move to a new Licence discussed (MIT);
• Application to OSGeo
• Development picks ups throughout 2015:
• Student at LIST;
• Google Summer of Code (GSoC).
• PyWPS enters the OSGeo incubation process in April of 2015.
• Big push from OSGeo mentorship (Tom Kralidis)
• Consolidation of documentation and websites.
• PyWPS.org goes live.
• More successful GSoC applications.
• Official release of PyWPS 4.0.0 some time this Summer ...
Motivation for PyWPS-4
• PyWPS is now a decade old.
• Python version 3 taking over.
• New bindings for other libraries (e.g PyGRASS).
• New data formats (e.g. GeoJSON, KML, TopoJSON).
• Version 2.0 of the WPS standard.
• Less restrictive licence (MIT).
• A four level approach:
• No validation - always considered valid.
• Simple validation - uses just the mimeType.
• Strict validation - attempts to open Complex inputs with
GDAL, comparing with mimeType.
• Very strict validation - uses an XML schema.
• Plus custom validation, already including: ESRI Shapefile, GeoJSON,
• WPS server should run Execute requests concurrently.
• but in totally insulated fashion;
• no shared resources or data.
• a temporary folder is created for each Execute;
• resulting data is moved to publishing folder;
• temporary folder is deleted at execution end.
• PyWPS-4 aims at a safer approach (e.g Docker, vagrant)
• PyWPS can process various Execute requests in parallel:
• configurable number;
• plus a queue of waiting requests.
• PyWPS-4 now uses the Multiprocessing module:
• os.fork() abandoned;
• PyWPS should now run on Windows too.
• Process metadata now stored in a database (SQLite, PostgreSQL -
logging, request queueing, etc). - GSoC project
• Local database to support WPS 2.0.
• New requests in WPS 2.0: Pause, Release, Delete.
• Improved security with process containerising.
• Administrative web interface.
• External services to publish outputs.
• REST API
• Support for other languages beyond English.
Application to OSGeo
• Motion to enter incubation approved in April of 2015.
• Process mentored by Tom Kralidis.
• PyWPS-3 to feature in the next OSGeoLive release.
• PyWPS now has a Project Steering Committee (PSC)
• currently composed by 5 members
• PSC sets the roadmap, technical standards, release schedule, code
• Monthly meetings (IRC)
• Mailing list https://lists.osgeo.org/mailman/listinfo/pywps-dev
• 35 members
• IRC #geopython at irc.freenode.net server
• Gitter https://gitter.im/PyWPS
• Attending code sprints, conferences, ...