20
PyWPS Status report achym ˇ Cepick´ y 1 1 http://les-ejk.cz, http://geosense.cz FOSS4G-Europe 2014 PyWPS Status report 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

PyWPS Status report

Embed Size (px)

DESCRIPTION

Report about current PyWPS status and development.

Citation preview

Page 1: PyWPS Status report

PyWPSStatus report

Jachym Cepicky1

1http://les-ejk.cz, http://geosense.cz

FOSS4G-Europe 2014

PyWPSStatus report

Jachym Cepicky1

1http://les-ejk.cz, http://geosense.cz

FOSS4G-Europe 2014

2014

-07-

13PyWPS

Hallomy name is Jachym Cepicky

Page 2: PyWPS Status report

2014

-07-

13PyWPS

today, I’m talking here on behalf of the PyWPS development team

Page 3: PyWPS Status report

2014

-07-

13PyWPS

PyWPS development started in 2006, just early enough, to be firsttime presented at first FOSS4G in Lausanne. It is implementation ofOGC WPS standard on the server side and it’s written in Pythonprogramming language. Curent version is distributed under theGNU/GPL license. New PyWPS (we call it 4) is developed under MITlicense.

Page 4: PyWPS Status report

2014

-07-

13PyWPS

I already metioned, PyWPS is written in Python. Among otherimplementations of the standard, PyWPS is known for it’s simplicity,regarding installation and setup. Instalation is matter of severalminutes. After that, user must write her own scripts, which are theninterpreted as processes.

Page 5: PyWPS Status report

2014

-07-

13PyWPS

Since beginning, PyWPS contained support for GRASS GIS modules.

Page 6: PyWPS Status report

2014

-07-

13PyWPS

GDAL/OGR or

Page 7: PyWPS Status report

2014

-07-

13PyWPS

R

Page 8: PyWPS Status report

PyWPS-4

PyWPS-4

2014

-07-

13PyWPS

So, why did we start to rewrite PyWPS from scratch?

Page 9: PyWPS Status report

2014

-07-

13PyWPS

In 2006, the world of GeoPython was different

Page 10: PyWPS Status report

2014

-07-

13PyWPS

• 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 OGCServices

• Most used format was ESRI Shapefile and we started to talkabout GML.

Page 11: PyWPS Status report

2014

-07-

13PyWPS

Today, we have

• Python 3

• Native GRASS Python API

• new projects, like lxml, owslib, werkzeug

• new formats - GeoJSON, TopoJSON (anybody heard aboutKML, recently? . . . )

Page 12: PyWPS Status report

https://github.com/jachym/pywps-4/issues/milestones

https://github.com/jachym/pywps-4/issues/milestones

2014

-07-

13PyWPS

On this URL, we started to creat roadmap. Currently, we aredistinguishing between PyWPS 4.0 and 4.1.

Page 13: PyWPS Status report

PyWPS 4.0: What do we haveI ValidatorsI Server implementation based on werkzeugI IOHandlerI File Storage

PyWPS 4.0: What do we haveI ValidatorsI Server implementation based on werkzeugI IOHandlerI File Storage

2014

-07-

13PyWPS

• Validators - gml, shp, 4 stupne

• Server implementation based on werkzeug - popular library forserver-side apps creation

• IOHandler is universal objekt for transparent transformation ofdata, beteween data stream, file object, in memory object nadother representations.

• File Storage – output files hanlder

Page 14: PyWPS Status report

Plans for PyWPS 4.1:

I Data outputs via GeoServer, MapServer and/or QGISMapServer

I Administrative REST API

Plans for PyWPS 4.1:

I Data outputs via GeoServer, MapServer and/or QGISMapServer

I Administrative REST API

2014

-07-

13PyWPS

PyWPS 4.1 should contain

• Outpu via GeoServer, MapServer, QGIS Server

• Administrative REST API

• Database storage, external service storage (FTP, Dropbox, ...)

Page 15: PyWPS Status report

2014

-07-

13PyWPS

what does break us

Page 16: PyWPS Status report

2014

-07-

13PyWPS

The team is curently of of time and there are no external resourcescurrently, to move faster forward.

We have to confess, that for open source project about this size, lackof resources is critical. We are able to maitain current version ofPyWPS fixing, but heavy works on PyWPS 4 are impossible.

Page 17: PyWPS Status report

2014

-07-

13PyWPS

This year, we had luck and we got 4 interesting proposals for GoogleSummer of code. As result, we have now one student working onprocess chaining on current version of PyWPS and we are lookingforward to port her work into PyWPS 4.

Page 18: PyWPS Status report

2014

-07-

13PyWPS

Yearlier this year, thanks to COST framework, PyWPS had change tomeet at code sprint at Henri Tudor research center in Luxembourg. Itwas join event with 52North WPS and we hope, next year the WPScomming together will be even bigger, and our collegues from Zoo orGeoserver or other projects will join us as well.

Page 19: PyWPS Status report

I Intevation GmbHI Help Service - Remote SensingI Deutsche Bundesstiftung UmweltI Netmar projectI COST Framework

I Intevation GmbHI Help Service - Remote SensingI Deutsche Bundesstiftung UmweltI Netmar projectI COST Framework

2014

-07-

13PyWPS

I would like to thank to existing and past sponsors of PyWPS andencourage new comming sponsors, to help with the development.The companies and projects supported the project with eitherhardware or man-power, so PyWPS could be at the spot, where it isnow.

Page 20: PyWPS Status report

Questions?

http://pywps.intevation.org

Questions?

http://pywps.intevation.org

2014

-07-

13PyWPS

Conclusion

Thank you