PyWPS

PyWPS-4.2.4 Released

2020-02-09T00:00:00+00:00

PyWPS-4.2.4 Released

New bugfix-release of PyWPS is finally produced, with following features

Added support for multiple languages (#510).
Added AWS S3 Storage option (#451).
Fixed type check (#507).
Fixed file storage (#504).
Fixed async keyword (#502).

PyWPS-4.2.2 Released

2019-09-25T00:00:00+00:00

PyWPS-4.2.2 Released

New bugfix-release of PyWPS is finally produced, with following bugfixes

Fixed scheduler extension (#480).
Fixed ValuesReference implementation (#471, #484).
Fixed AllowedValue range (#467, #464).
Add metalink support to facilitate outputs with multiple files (#466).
Rename async to async_ for Python 3.7 compatibility (#462).
Improve queue race conditions (#455).
Numerous bug-fixes, additional tests and documentation improvements.

PyWPS-4.2.0 Released

2018-12-20T00:00:00+00:00

PyWPS-4.2.0 Released

At long last, a new PyWPS release is out. A new chapter in the PyWPS 4 story is now complete and as 2018 comes to an end, it is time to look back at what happened since the major release in December of 2016.

PyWPS remains fully reliant on pro bono contributions without any sort of commercial organisation around it. This means the project largely depends on how the community is able to contribute at any given time. However, it also means there are no clients to attend or shareholders to appease, no hard deadlines or sales demos. PyWPS evolves organically, to the tune of the community’s wishes.

Relying on voluntary contributions does not mean progress is slow, much to the contrary. In recent times PyWPS has had more simultaneous contributors than at any moment before in its history. This is largely due to the major step taken with PyWPS 4 towards modern Python technologies, but also to regular contributions from the Google Summer of Code (GSoC) programme and various students thesis. During these two years the Project Steering Committe (PSC) was expanded to six members, and last May PyWPS finally graduated as an OSGeo project.

In order to manage development, the Project Steering Committe (PSC) meets regularly (usually at FOSS4G events) and performs basic housekeeping: issues are reviewed and split among a series of milestones that set out a development plan. As development progresses, new issues naturally pop up, and there is always a patch or an improvement that developers wish to include in the next release. Like the Red Queen from Alice in Wonderland, the backlog for the next release seems to always have as many issues resolved as new ones to resolve. Time drags on and the perfect tidy release remains ellusive. So in the end PyWPS 4.2 is mostly a commemorative release, celebrating two years since the major release and making official all the improvements introduced since.

What are then the main improvements introduced with PyWPS 4.2? Foremost is the progressive improvement of the class model, step by step making the library more solid, agile and easier to maintain. Among other things, the input/output handling classes were refactored, the test battery was expanded and streamlined with continuous integration tools. Other relevant improvements include:

Introduction of Jinja2 templates to automate the generation of outputs.
Support for process execution in HPC environments, using Slurm or GridEngine.
Support for streamed URL-based data inputs (e.g. OpenDAP).
Automated process documentation with Sphinx.
New validators for JSON, DODS links and netCDF formats.

And along the way, many bugs were fixed.

The organic nature of the project has meant that the goals set out by the PSC are not always met. For instance, PyWPS 4.2 still does not fully support version 2 of the WPS standard. But such is the nature of community driven projects: evolution goes along the needs of the community and not necessarily according to grand plans. There are instead other great improvements in the pipeline, like the containerisation of processes, or the automatic storage of outputs in a database. Please get involved if these developments interest you, or if you would like other improvements to be introduced.

A word also regarding the WSGI applications provided as example services using PyWPS. pywps-flask remains the most popular but a backlog of small issues has built up. During the holiday season developers will be lending attention to these issues. Usability issues with the containers of both pywps-flask and pywps-django will also be addressed during this time.

Finally the PSC would like to thank everyone that has contributed to PyWPS these past two years: from those doing the code heavy lifting, to testers, bug reporters, documentation contributors. Every bit of contribution is precious. Thank you all for making PyWPS what it is today!

Merry Christmas and a Happy New Year.

PyWPS recognized as OSGeo Project

2018-05-30T00:00:00+00:00

PyWPS finished the OSGeo incubation process

On April 11th 2018, OSGeo Board of Directors recognized [1] PyWPS project as an official OSGeo project, thanks to the efforts of the PyWPS Project Steering committee and Tom Kralidis, our incubation mentor. The incubation process started 9 years ago [2] and was one of the longest processes within the OSGeo ecosystem. Over this time, PyWPS demonstrated [3] a stable community, evolving into version 4 with completely new code base and license change, took part on several Google Summer of Code events, formed a Project Steering Committee [4] and many more.

About PyWPS

PyWPS (http://pywps.org) is an implementation of the Web Processing Service standard from the Open Geospatial Consortium. PyWPS is written in Python. It enables integration, publishing and execution of Python processes via the OGC WPS standard.

PyWPS is Open Source and released under an MIT license.

About OSGeo

The Open Source Geospatial Foundation (OSGeo http://osgeo.org) is a not-for-profit organization whose mission is to foster global adoption of open geospatial technology by being an inclusive software foundation devoted to an open philosophy and participatory community driven development.

[1] https://www.loomio.org/d/vcAgpzQl/recognize-pywps-as-a-new-osgeo-project-with-jachym-as-vp-of-pywps-within-our-organization-and-an-initial-committee-budget-of-2000-usd-for-2018

[2] https://trac.osgeo.org/osgeo/ticket/337

[3] https://github.com/geopython/pywps/wiki/ProjectGraduationChecklist

[4] http://pywps.org/development/psc.html

PyWPS 4.0.0 released

2016-12-07T00:00:00+00:00

PyWPS 4.0.0 released

The PyWPS Development team announces the release of PyWPS 4.0.0.

Changes

Features of this version:

PyWPS 4.0.0 is completely rewritten “from scratch” of the software
PyWPS 4.0.0 uses MIT License
It uses modern libraries for XML serialisation and deserialization
Jobs queue with database back-end implemented, introduces possibility to control process-job’s life cycle
Introduces input data validation (for levels NONE to VERYSTRICT)
Multiprocessing Python module for asynchronous jobs starting

To download this version, please go to http://pywps.org/download

NOTE:

PyWPS-4 is completely rewritten from scratch - the logic of process definition remained the same, but processes are not compatible with previous 3.x version.

What is PyWPS:

PyWPS (Python Web Processing Service) is implementation of Web Processing Service standard from Open Geospatial Consortium (OGC(R)). Processes can be written using GRASS GIS, but usage of other programs, like R package, GDAL or PROJ tools, is possible as well.

You can find more in our PyWPS-4.0.0 presentation on SlideShare

Happy GISing!

PyWPS Development team

P.S. Happy birthday, Jorge!

Documentation moved to ReadTheDocs.io

2016-09-05T00:00:00+00:00

Documentation moved to ReadTheDocs.io

We just moved documentation to ReadTHeDocs server for PyWPS and PyWPS-demo projects, check it out:

PyWPS at OSGeoLive

2016-08-08T00:00:00+00:00

PyWPS now part of OSGeoLive

This is PyWPS’ first official release into the OSGeo-Live project. You can see the live docs at:

Overview: http://live.osgeo.org/en/overview/pywps_overview.html
Quickstart: https://live.osgeo.org/en/quickstart/pywps_quickstart.html

Currently, there us PyWPS-3 version (stable) available at the DVD.

Once PyWPS 4.0.0 is released and stable our OSGeo Live efforts should concentrate on moving to 4.x.

PyWPS 4.0.0-beta1 released

2016-07-28T00:00:00+00:00

PyWPS 4.0.0-beta1 released

The PyWPS development team has just released the first beta version of the upcoming PyWPS 4.0. This new release is a complete re-write of PyWPS, taking full advantage of modern Python technologies.

For a bit of history and a quick overview of PyWPS-4 there is this presentation.

For a more in depth information please consult the article recently published by ISPRS.

The source code for this beta release is available at GitHub. Please follow the documentation to install PyWPS 4.0 and the accompanying demo application.

This beta release aims to fully comply with the WPS 1.0 standard and support seamless integration with GRASS GIS. Please report your feedback at the PyWPS mailling list, or open an issue at GitHub.

PyWPS at GeoPython conference

2016-07-06T00:00:00+00:00

PyWPS at GeoPython conference, Basel 2016

PyWPS project was at GeoPython conference in Basel, 2016. Luis gave talk about new PyWPS (the presentation can be downloaded and re-used from GitHub https://github.com/pywps/presentation). We were also code sprinting a bit, see our final report in the wiki https://github.com/geopython/pywps/wiki/Sprint-2016-Basel.

Next time we meet in Bonn at FOSS4G http://2016.foss4g.org

GRASS GIS back

2016-07-04T00:00:00+00:00

GRASS GIS back in PyWPS

In recent pull request https://github.com/geopython/pywps/pull/145, we have add support for temporary GRASS GIS http://grass.osgeo.org LOCATION and MAPSET along with GRASS environment suitable for running grass.script and pygrass code from PyWPS process. This shall be part of PyWPS 4.0 stable release.