Hello, yes, zgeo.wfs must in eggs and zcml
now to use it, you need actual content types (zgeo.wfs does not provide any Plone CT, it just provides adapters) and mark them with appropriate interfaces: - the container which will provides the WFS service needs to implement zgeo.wfs.interfaces.IWebFeatureServiceable - the geo item (stored into the container) need to implement zgeo.geographer.interfaces.IGeoreferenceable have a look to the doctests, you will see how it works Eric On Fri, Jun 11, 2010 at 12:03 PM, Christian Ledermann <[email protected]> wrote: > On Fri, 2010-06-11 at 11:09 +0200, Eric Bréhault wrote: >> I see >> unfortunately, AdvancedQuery is intensively used to manage the WFS >> GetFeature requests >> it cannot be achieved with regular ZCatalog search > > OK, I contacted Dieter, the maintainer of Advanced Query, and this > problem is solved :) > > Actually it was all my fault, I added Advanced query to the wrong > section of the buildout. > > > BTW, I have to add zgeo.wfs to my eggs and zcml section? > > If i add it only to my eggs and not to the zcml section plone starts up > OK, but the pages @@wfs, @@wfsconfig, @@getFeatureInfo ( like > localhost:8080/plone-site/news/wfs) give me a 404. > > > > > > > -- > Best regards, > > Christian Ledermann > > Nairobi - Kenya > Mobile : +254 729495789 > > <*)))>{ > > If you save the living environment, the biodiversity that we have left, > you will also automatically save the physical environment, too. But If > you only save the physical environment, you will ultimately lose both. > > }<(((*> > > _______________________________________________ > Community mailing list > [email protected] > http://lists.gispython.org/mailman/listinfo/community > _______________________________________________ Community mailing list [email protected] http://lists.gispython.org/mailman/listinfo/community
