PyWPS
Status report
J´achym ˇCepick´y1
1http://les-ejk.cz, http://geosense.cz
FOSS4G-Europe 2014
PyWPS
Status report
J´achym ˇCepick´y1
1http://les-ejk.cz, http://geosense.cz
FOSS4G-Europe 2014
2014-07-13
PyWPS
Hallo
my name is J´achym ˇCepick´y
2014-07-13
PyWPS
today, I’m talking here on behalf of the PyWPS development team
2014-07-13
PyWPS
PyWPS development started in 2006, just early enough, to be first
time presented at first FOSS4G in Lausanne. It is implementation of
OGC WPS standard on the server side and it’s written in Python
programming language. Curent version is distributed under the
GNU/GPL license. New PyWPS (we call it 4) is developed under MIT
license.
2014-07-13
PyWPS
I already metioned, PyWPS is written in Python. Among other
implementations of the standard, PyWPS is known for it’s simplicity,
regarding installation and setup. Instalation is matter of several
minutes. After that, user must write her own scripts, which are then
interpreted as processes.
2014-07-13
PyWPS
Since beginning, PyWPS contained support for GRASS GIS modules.
2014-07-13
PyWPS
GDAL/OGR or
2014-07-13
PyWPS
R
PyWPS-4
PyWPS-4
2014-07-13
PyWPS
So, why did we start to rewrite PyWPS from scratch?
2014-07-13
PyWPS
In 2006, the world of GeoPython was different
2014-07-13
PyWPS
• There was no GRASS Python API
• Python was in 2.2 version
• For working with xmls, you had to do everything manually
• There were no libraries, which would help you to deal with OGC
Services
• Most used format was ESRI Shapefile and we started to talk
about GML.
2014-07-13
PyWPS
Today, we have
• Python 3
• Native GRASS Python API
• new projects, like lxml, owslib, werkzeug
• new formats - GeoJSON, TopoJSON (anybody heard about
KML, recently? . . . )
https:
//github.com/jachym/pywps-4/issues/milestones
https:
//github.com/jachym/pywps-4/issues/milestones
2014-07-13
PyWPS
On this URL, we started to creat roadmap. Currently, we are
distinguishing between PyWPS 4.0 and 4.1.
PyWPS 4.0: What do we have
Validators
Server implementation based on werkzeug
IOHandler
File Storage
PyWPS 4.0: What do we have
Validators
Server implementation based on werkzeug
IOHandler
File Storage
2014-07-13
PyWPS
• Validators - gml, shp, 4 stupnˇe
• Server implementation based on werkzeug - popular library for
server-side apps creation
• IOHandler is universal objekt for transparent transformation of
data, beteween data stream, file object, in memory object nad
other representations.
• File Storage – output files hanlder
Plans for PyWPS 4.1:
Data outputs via GeoServer, MapServer and/or QGIS
MapServer
Administrative REST API
Plans for PyWPS 4.1:
Data outputs via GeoServer, MapServer and/or QGIS
MapServer
Administrative REST API
2014-07-13
PyWPS
PyWPS 4.1 should contain
• Outpu via GeoServer, MapServer, QGIS Server
• Administrative REST API
• Database storage, external service storage (FTP, Dropbox, ...)
2014-07-13
PyWPS
what does break us
2014-07-13
PyWPS
The team is curently of of time and there are no external resources
currently, to move faster forward.
We have to confess, that for open source project about this size, lack
of resources is critical. We are able to maitain current version of
PyWPS fixing, but heavy works on PyWPS 4 are impossible.
2014-07-13
PyWPS
This year, we had luck and we got 4 interesting proposals for Google
Summer of code. As result, we have now one student working on
process chaining on current version of PyWPS and we are looking
forward to port her work into PyWPS 4.
2014-07-13
PyWPS
Yearlier this year, thanks to COST framework, PyWPS had change to
meet at code sprint at Henri Tudor research center in Luxembourg. It
was join event with 52North WPS and we hope, next year the WPS
comming together will be even bigger, and our collegues from Zoo or
Geoserver or other projects will join us as well.
Intevation GmbH
Help Service - Remote Sensing
Deutsche Bundesstiftung Umwelt
Netmar project
COST Framework
Intevation GmbH
Help Service - Remote Sensing
Deutsche Bundesstiftung Umwelt
Netmar project
COST Framework
2014-07-13
PyWPS
I would like to thank to existing and past sponsors of PyWPS and
encourage new comming sponsors, to help with the development.
The companies and projects supported the project with either
hardware or man-power, so PyWPS could be at the spot, where it is
now.
Questions?
http://pywps.intevation.org
Questions?
http://pywps.intevation.org
2014-07-13
PyWPS
Conclusion
Thank you

PyWPS Status report

  • 1.
    PyWPS Status report J´achym ˇCepick´y1 1http://les-ejk.cz,http://geosense.cz FOSS4G-Europe 2014 PyWPS Status report J´achym ˇCepick´y1 1http://les-ejk.cz, http://geosense.cz FOSS4G-Europe 2014 2014-07-13 PyWPS Hallo my name is J´achym ˇCepick´y
  • 2.
    2014-07-13 PyWPS today, I’m talkinghere on behalf of the PyWPS development team
  • 3.
    2014-07-13 PyWPS PyWPS development startedin 2006, just early enough, to be first time presented at first FOSS4G in Lausanne. It is implementation of OGC WPS standard on the server side and it’s written in Python programming language. Curent version is distributed under the GNU/GPL license. New PyWPS (we call it 4) is developed under MIT license.
  • 4.
    2014-07-13 PyWPS I already metioned,PyWPS is written in Python. Among other implementations of the standard, PyWPS is known for it’s simplicity, regarding installation and setup. Instalation is matter of several minutes. After that, user must write her own scripts, which are then interpreted as processes.
  • 5.
    2014-07-13 PyWPS Since beginning, PyWPScontained support for GRASS GIS modules.
  • 6.
  • 7.
  • 8.
    PyWPS-4 PyWPS-4 2014-07-13 PyWPS So, why didwe start to rewrite PyWPS from scratch?
  • 9.
    2014-07-13 PyWPS In 2006, theworld of GeoPython was different
  • 10.
    2014-07-13 PyWPS • There wasno GRASS Python API • Python was in 2.2 version • For working with xmls, you had to do everything manually • There were no libraries, which would help you to deal with OGC Services • Most used format was ESRI Shapefile and we started to talk about GML.
  • 11.
    2014-07-13 PyWPS Today, we have •Python 3 • Native GRASS Python API • new projects, like lxml, owslib, werkzeug • new formats - GeoJSON, TopoJSON (anybody heard about KML, recently? . . . )
  • 12.
  • 13.
    PyWPS 4.0: Whatdo we have Validators Server implementation based on werkzeug IOHandler File Storage PyWPS 4.0: What do we have Validators Server implementation based on werkzeug IOHandler File Storage 2014-07-13 PyWPS • Validators - gml, shp, 4 stupnˇe • Server implementation based on werkzeug - popular library for server-side apps creation • IOHandler is universal objekt for transparent transformation of data, beteween data stream, file object, in memory object nad other representations. • File Storage – output files hanlder
  • 14.
    Plans for PyWPS4.1: Data outputs via GeoServer, MapServer and/or QGIS MapServer Administrative REST API Plans for PyWPS 4.1: Data outputs via GeoServer, MapServer and/or QGIS MapServer Administrative REST API 2014-07-13 PyWPS PyWPS 4.1 should contain • Outpu via GeoServer, MapServer, QGIS Server • Administrative REST API • Database storage, external service storage (FTP, Dropbox, ...)
  • 15.
  • 16.
    2014-07-13 PyWPS The team iscurently of of time and there are no external resources currently, to move faster forward. We have to confess, that for open source project about this size, lack of resources is critical. We are able to maitain current version of PyWPS fixing, but heavy works on PyWPS 4 are impossible.
  • 17.
    2014-07-13 PyWPS This year, wehad luck and we got 4 interesting proposals for Google Summer of code. As result, we have now one student working on process chaining on current version of PyWPS and we are looking forward to port her work into PyWPS 4.
  • 18.
    2014-07-13 PyWPS Yearlier this year,thanks to COST framework, PyWPS had change to meet at code sprint at Henri Tudor research center in Luxembourg. It was join event with 52North WPS and we hope, next year the WPS comming together will be even bigger, and our collegues from Zoo or Geoserver or other projects will join us as well.
  • 19.
    Intevation GmbH Help Service- Remote Sensing Deutsche Bundesstiftung Umwelt Netmar project COST Framework Intevation GmbH Help Service - Remote Sensing Deutsche Bundesstiftung Umwelt Netmar project COST Framework 2014-07-13 PyWPS I would like to thank to existing and past sponsors of PyWPS and encourage new comming sponsors, to help with the development. The companies and projects supported the project with either hardware or man-power, so PyWPS could be at the spot, where it is now.
  • 20.