[OWSLib-devel] Fwd: Call for OWS Common Server Python base

[Tom Kralidis]

Thanks Stephan.  FYI Dom Lowe (thanks Dom!) sent along
http://proj.badc.rl.ac.uk/cows/browser/cows/trunk/cows/model as
something we could leverage as well.

Looks like we have a fair bit of implementations we can leverage for a
unified lib.

On Mon, Oct 21, 2013 at 1:20 PM, Stephan Meißl <stephan at meissl.name> wrote:
> Jachym, Tom, Angelos, All,
>
> this sounds like a great initiative. In EOxServer [1] we've already
> invested quite some effort to provide the server side for WMS and WCS
> (e.g. [2]). Don't know yet how this could fit into a common
> owslib-server but maybe something to explore to save some efforts.
>
> I'm looking forward to welcome you in Vienna next March!
>
> cu
> Stephan
>
> [1] eoxserver.org/
> [2]
> https://github.com/EOxServer/eoxserver/tree/master/eoxserver/services/ows
>
>
>> Hi all Geo-Pythonists,
>>
>> [please spread between communities, sorry for crossposting]
>>
>> today, we (me, Tom Kralidis and Angelos Tzotsos) had IRC discussion (on
>> #geopython channel), and we all came to conslusion, that it it would be
>> nice, to share some code base and start to work on common OWS-server
>> implementation, which could cover needs of various projects (currently
>> PyWPS and pycsw), for their server-side implementation.
>>
>> As you might know, PyWPS started to be rewritten from scratch and some
>> currently used approaches seems to be interesting for others as well.
>> Pycsw is on the other hand widely used, they are both OGC OWS
>> implementations and so, they have some common needs (for example
>> Exception handelings, the whole server-side infrastructure,  etc.).
>>
>> So we would like to invite all members of the (open source) geo-python
>> community to join us on OWSLib-dev mailing list [1] (because the library
>> could be part of it, as owslib/server) within a week from now.
>>
>> The discussion will start there beginning with *monday 24.10.2013*.
>> Please, drop short information about you and project, you are interested
>> most to this list, once you are connected, so that we know, each other.
>>
>> We would also like to join the Vienna Code sprint [2] in next year, and
>> push the work further forward, if the discussion will lead to common work.
>>
>> See you at owslib-devel
>>
>> Jachym (on behalf of Tom and Angelos)
>>
>>
>> [1] http://lists.osgeo.org/cgi-bin/mailman/listinfo/owslib-devel
>> [2] http://wiki.osgeo.org/wiki/Vienna_Code_Sprint_2014
>
> _______________________________________________
> OWSLib-devel mailing list
> OWSLib-devel at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/owslib-devel