OWSLib SOS enhancements

[Kralidis,Tom [Ontario]]

Hi,

First off, let me congratulate the team here on a useful package for WxS
in OWSLib.  I have contacted Sean G. offline, who suggested I get
acquianted in this space.

I'd like to add SOS (1.0.0) support in OWSLib.  I think this will add
value to OWSLib in terms of additional OWS support w.r.t. monitoring and
observation data.  As well, I think it will add value in terms of
working with OWS Common, OGC's approach to a unified content model for
things like Capabilities XML, etc.

I have some more detailed questions w.r.t. OWSLib and this addition,
which are better discussed in another thread, but I just wanted to get
folks' thoughts first.

I also believe I need a trac userid to http://trac.gispython.org/lab.

Thanks

..Tom

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

[Sean Gillies]

>
> Hi,
>
> First off, let me congratulate the team here on a useful package for WxS
> in OWSLib.  I have contacted Sean G. offline, who suggested I get
> acquianted in this space.
>
> I'd like to add SOS (1.0.0) support in OWSLib.  I think this will add
> value to OWSLib in terms of additional OWS support w.r.t. monitoring and
> observation data.  As well, I think it will add value in terms of
> working with OWS Common, OGC's approach to a unified content model for
> things like Capabilities XML, etc.
>
> I have some more detailed questions w.r.t. OWSLib and this addition,
> which are better discussed in another thread, but I just wanted to get
> folks' thoughts first.
>
> I also believe I need a trac userid to http://trac.gispython.org/lab.
>
> Thanks
>
> ..Tom
>

Hi Tom. The project's take on OWS Common is laid out in

http://trac.gispython.org/lab/browser/OWSLib/trunk/owslib/interfaces.py

These interfaces are not formal contracts, but are more of a blueprint for
developers (although they could become formalized if this is ever ported
to Python 3). A new SOS service proxy class should provide
ISensorObservationService, which should derive from IService. See
IWebMapService for example:

http://trac.gispython.org/lab/browser/OWSLib/trunk/owslib/interfaces.py#L64

Currently the different services provide IService in different ways, but
Dominic and I are both interested in refactoring for consolidation.

Cheers,
Sean


_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

[Dominic Lowe]

Hi Tom,

Adding SOS support to OWSLib would be great. Please ask if you have any
questions.

> Currently the different services provide IService in different ways, but
> Dominic and I are both interested in refactoring for consolidation.
>
btw: I actually attempted to harmonize the Service metadata for WFS/WMS and
WCS in this changeset:
http://trac.gispython.org/lab/changeset/1095

So any of the W*S code modules can be used as a 'template' for SOS.

btw #2: At the moment the service metadata is handled on a per service level  
it might make sense to refactor and subclass services from a (OWS) common
base service (but it's not essential right now..).

Cheers,
Dominic


On Thursday 28 August 2008 18:25:43 sgillies@... wrote:

> > Hi,
> >
> > First off, let me congratulate the team here on a useful package for WxS
> > in OWSLib.  I have contacted Sean G. offline, who suggested I get
> > acquianted in this space.
> >
> > I'd like to add SOS (1.0.0) support in OWSLib.  I think this will add
> > value to OWSLib in terms of additional OWS support w.r.t. monitoring and
> > observation data.  As well, I think it will add value in terms of
> > working with OWS Common, OGC's approach to a unified content model for
> > things like Capabilities XML, etc.
> >
> > I have some more detailed questions w.r.t. OWSLib and this addition,
> > which are better discussed in another thread, but I just wanted to get
> > folks' thoughts first.
> >
> > I also believe I need a trac userid to http://trac.gispython.org/lab.
> >
> > Thanks
> >
> > ..Tom
>
> Hi Tom. The project's take on OWS Common is laid out in
>
> http://trac.gispython.org/lab/browser/OWSLib/trunk/owslib/interfaces.py
>
> These interfaces are not formal contracts, but are more of a blueprint for
> developers (although they could become formalized if this is ever ported
> to Python 3). A new SOS service proxy class should provide
> ISensorObservationService, which should derive from IService. See
> IWebMapService for example:
>
> http://trac.gispython.org/lab/browser/OWSLib/trunk/owslib/interfaces.py#L64
>
> Currently the different services provide IService in different ways, but
> Dominic and I are both interested in refactoring for consolidation.
>
> Cheers,
> Sean
>
>
> _______________________________________________
> Community mailing list
> Community@...
> http://lists.gispython.org/mailman/listinfo/community

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

[Kralidis,Tom [Ontario]]

Dominic: thanks for the info.  The existing harmonization is pretty bang on.  There are a few extensions I may add in there.

..Tom



-----Original Message-----
From: community-bounces@... on behalf of Dominic Lowe
Sent: Fri 29-Aug-08 10:35
To: community@...
Subject: Re: [Community] OWSLib SOS enhancements
 
Hi Tom,

Adding SOS support to OWSLib would be great. Please ask if you have any
questions.

> Currently the different services provide IService in different ways, but
> Dominic and I are both interested in refactoring for consolidation.
>
btw: I actually attempted to harmonize the Service metadata for WFS/WMS and
WCS in this changeset:
http://trac.gispython.org/lab/changeset/1095

So any of the W*S code modules can be used as a 'template' for SOS.

btw #2: At the moment the service metadata is handled on a per service level  
it might make sense to refactor and subclass services from a (OWS) common
base service (but it's not essential right now..).

Cheers,
Dominic


On Thursday 28 August 2008 18:25:43 sgillies@... wrote:

> > Hi,
> >
> > First off, let me congratulate the team here on a useful package for WxS
> > in OWSLib.  I have contacted Sean G. offline, who suggested I get
> > acquianted in this space.
> >
> > I'd like to add SOS (1.0.0) support in OWSLib.  I think this will add
> > value to OWSLib in terms of additional OWS support w.r.t. monitoring and
> > observation data.  As well, I think it will add value in terms of
> > working with OWS Common, OGC's approach to a unified content model for
> > things like Capabilities XML, etc.
> >
> > I have some more detailed questions w.r.t. OWSLib and this addition,
> > which are better discussed in another thread, but I just wanted to get
> > folks' thoughts first.
> >
> > I also believe I need a trac userid to http://trac.gispython.org/lab.
> >
> > Thanks
> >
> > ..Tom
>
> Hi Tom. The project's take on OWS Common is laid out in
>
> http://trac.gispython.org/lab/browser/OWSLib/trunk/owslib/interfaces.py
>
> These interfaces are not formal contracts, but are more of a blueprint for
> developers (although they could become formalized if this is ever ported
> to Python 3). A new SOS service proxy class should provide
> ISensorObservationService, which should derive from IService. See
> IWebMapService for example:
>
> http://trac.gispython.org/lab/browser/OWSLib/trunk/owslib/interfaces.py#L64
>
> Currently the different services provide IService in different ways, but
> Dominic and I are both interested in refactoring for consolidation.
>
> Cheers,
> Sean
>
>
> _______________________________________________
> Community mailing list
> Community@...
> http://lists.gispython.org/mailman/listinfo/community

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community

_______________________________________________
Community mailing list
Community@...
http://lists.gispython.org/mailman/listinfo/community