[OWSLib-devel] OWS Python server

[Ricardo Filipe Soares Garcia da]

I can share my own experience with you:


I've been working on a OGC OSEO[1] (ordering services) server in Python. It
is not full featured (yet), but it is good enough for my requirements
already.

I've studied some bits of owslib, pyCSW and pyWPS code and came up with my
own implementation.

This was due to the following reasons:

* I had to work fast, due to project constraints, so there was no time to
try and get some sort of core server done first and then build OSEO
functionality on top of this.

* it seemed owslib was more fit to be used as a client than in server code
as I needed access to the raw XML requests in order to process SOAP headers
and stuff.
I've decided to use the requests library for handling HTTP requests and
responses and pyxb as a way to generate python objects from the underlying
XML schemas from OGC.

* I also wanted to incorporate django into my server, so as to have the
admin backend autogenerated and use django to manage my database of ordered
products. This involved structuring things in a different way.

Studying owslib, pycsw and pywps was very insightful and definitely helped
me a lot with this project. Furthermore, since then I have contributed some
patches to pywps and am currently evaluating using pycsw in a new project,
so it was a multiple win.

I'd recommend that you study the code for pycsw, pywps (and my own pyoseo,
if I may be even more shameless) and then, depending on your time
constraints:

* go for your own WCS implementation, taking bits from the other projects.
This will be faster to develop and more likely to succeed in a timely
fashion

or

* start a round up for creating a OGC Common base server, work on that and
simultaneously create a WCS server on top of it as a proof of concept. This
one is a lot more work, but it could prove to be more fun too.
Personally, I think that it would be great if there was a common base for
implementing OGC web services in Python. Maybe something that follows the
Web Service Common standard [2]. I'd like to be a part of such an effort.

best regards

[1] - https://github.com/ricardogsilva/pyoseo
[2] - http://www.opengeospatial.org/standards/common

On Fri, Oct 10, 2014 at 1:34 PM, Jachym Cepicky <jachym.cepicky at gmail.com>
wrote:

> Hi,
>
> I would suggest to create proxy server, rather that try to implement
> everything.
>
> Just opinion,
>
> Jachym
>
> 2014-10-10 14:27 GMT+02:00 Ian Edwards <ian.edwards at metoffice.gov.uk>:
> > Hi All,
> >
> > OWSLib is excellent for client requests.
> >
> > Has anyone given any thought to creating a generic core package for a
> python
> > OGC server?  Such a package could learn from the development of packages
> > like pycsw and PyWPS, and could be used for creating reference
> > implementations for other OGC services (including emerging standards).
> >
> > If a generic server is not in the pipeline (or is not practical), would
> it
> > be easier to strip down and retask pycsw to create a server, or to extend
> > OWSLib?
> >
> > I'm interested in attempting a reference implementation for emerging WCS
> 2.0
> > extensions.
> >
> > Many thanks
> >
> > Ian
>
>
>
> --
> Jachym Cepicky
> e-mail: jachym.cepicky gmail com
> URL: http://les-ejk.cz
> GPG: http://les-ejk.cz/pgp/JachymCepicky.pgp
>
> Give your code freedom with PyWPS - http://pywps.wald.intevation.org
> _______________________________________________
> OWSLib-devel mailing list
> OWSLib-devel at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/owslib-devel
>



-- 
___________________________ ___ __
Ricardo Garcia Silva
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/owslib-devel/attachments/20141010/c6ee84f8/attachment.html>