On Mon, Oct 27, 2008 at 4:59 PM, Sean Gillies <[EMAIL PROTECTED]> wrote: > Eric Bréhault wrote: >> Hello, >> >> We are happy to announce you we have just released zgeo.wfs. >> >> zgeo.wfs provides an adapter to turn any Plone 3 folder into a WFS service. >> It allows to publish Plone geo-refrenced objects to any WFS compliant >> client like for instance OpenLayers which can be easily integrated in >> Plone. >> It allows to combine spatial and attributes criterias for filtering. >> >> It also supports WFS-T, so Plone objects geometry can be created or >> modified directly from the client. >> >> Using zgeo.wfs and OpenLayers, you can build a 100% Plone-based GIS >> application easily (no need of Mapserver, PostGIS, etc...). >> >> Here is a demo site containing 2 simple applications using zgeo.wfs: >> http://plone.demo.makina-corpus.net/plonegis >> Those 2 GIS applications have been built entirely through-the-web, we >> have just installed Plomino, zgeo.wfs and epwithgis (which is not >> released at the moment but will be soon) on Plone site, and we have >> designed everything from the Plone web interface. >> The flexibility of this architecture makes possible to build a >> complete GIS application (geometry storage, rendering, attributes >> management, spatial + attributes filtering, etc.) in a very small >> amount of time with almost no development. >> >> Any comments/questions/feedbacks are welcome. >> >> Best regards, >> >> Eric BREHAULT >> Makina Corpus >> www.makina-corpus.com > > Hi Eric, Hi Sean,
> > The demo looks good. I have a few comments about the zgeo.wfs code: > > If you could factor the plone dependencies into a zgeo.plone.wfs > package, a zgeo.wfs package depending only on Zope (3) could be > potentially useful to an organization like OpenGeo, which uses Zope and > Grok but not Plone. Yes indeed, and it is probably not that much work (my dependencies with Plone/Zope2 are currently the AT events, plus I need to use the Z3 catalog instead of Zcatalog). > > Eventually IGeoCollection will be eliminated from > zgeo.geographer.interfaces, and the sooner you prepare for this the > better. I recommend that you add the features iterator into your own > IWebFeatureService interface and not subclass IGeoCollection. > ok > Recently I met with Dominic Lowe and Stephan Pascoe at the British > Atmospheric Data Center and was introduced to a project called COWS. > It's a Pylons-based OWS implementation with code that may be useful to > you: http://proj.badc.rl.ac.uk/ndg/browser/cows. > Interesting. I will have a look. Cheers, Eric > Cheers, > Sean > > _______________________________________________ > Community mailing list > [email protected] > http://lists.gispython.org/mailman/listinfo/community > _______________________________________________ Community mailing list [email protected] http://lists.gispython.org/mailman/listinfo/community
