Okay, I've created a branch now: http://trac.gispython.org/lab/browser/OWSLib/branches/soswfsbranch
This contains wfs2, sos, filter, owscommon, util I mainly used my owscommon module but borrowed bits from yours - the interface should be the same, but you might want to check your SOS code works as expected. Cheers, Dom On Thursday 02 April 2009 13:52:12 Kralidis,Tom [Ontario] wrote: > > -----Original Message----- > > From: Dominic Lowe [mailto:[email protected]] > > Sent: Thursday, 02 April 2009 06:58 > > To: Sean Gillies; Kralidis,Tom [Ontario] > > Cc: [email protected] > > Subject: OWSLib WFS 2.0/SOS/OWSCommon branch? > > > > Hi Sean, Tom, > > > > I've recently extended OWSLib to read WFS "2.0.0" - which is > > the current draft WFS spec (also known as ISO 19142). > > This is great! > > > All the code is currently on our internal svn but I'd like to > > roll it into OWSlib if possible. Do you have any objections? > > > > Tom, are you still interested in SOS development? > > In a refactoring frenzy I also split off an owscommon module > > which I now realise more or less duplicates what you did here: > > http://trac.gispython.org/lab/ticket/172 > > > > I can attempt to harmonize the two bits of owscommon code and > > check it all in together (SOS, WFS2.0.0, OWSCommon) to give a > > base to work from - we should probably just create a new > > branch for now. Any thoughts on this? > > Agreed. If we could merge the OWS Common stuff into one, that would be > great. Let's start a branch. > > > Cheers, > > Dom > > > > p.s. One issue is that there are no WFS 2.0.0 servers yet to > > test against except our development machine (which isn't > > public). So we have the egg before the chicken. _______________________________________________ Community mailing list [email protected] http://lists.gispython.org/mailman/listinfo/community
