let's put it in SpatialIndex, I think it makes sense FYI: a colleague of mine and I are currently working on enabling WFS-T in zgeo.wfs, it is not finished but at the moment we are able to create Plone objects as points from OpenLayers.
Eric On Mon, Apr 21, 2008 at 5:40 PM, Sean Gillies <[EMAIL PROTECTED]> wrote: > Eric, > > I prefer that zgeo.spatialindex not contain Zope 2 catalog plugins. > > We could add it to the existing SpatialIndex product > > http://trac.gispython.org/projects/PrimaGIS/browser/SpatialIndex/trunk > > or start a new product for the index only and model it after other > existing index products like Extended Path Index: > > http://plone.org/products/extendedpathindex > > Sean > > > > Eric Bréhault wrote: > > Hello Sean, > > > > Sure, it certainely has to be a separate product. > > I can extract from zgeo.wfs the index I have built, it would be a good > > start for this product, and then you could implement and/or suggest > > any accurate evolution. > > What do you think ? > > > > PS: shall we name it zgeo.spatialindex ? > > > > Eric > > > > On Mon, Apr 21, 2008 at 4:39 PM, Sean Gillies <[EMAIL PROTECTED]> wrote: > >> Eric Bréhault wrote: > >> > Hello, > >> > > >> > I am currently working on zgeo.wfs in a Plone 3 context. > >> > As zgeo.wfs needs a catalog able to handle spatial operators, it would > >> > have been preferable to use zgeo.spatialindex. > >> > But it works in Zope 3, not Zope 2. > >> > So at the moment, I just keep using the GeoCatalog I have built in > >> > zgeo.wfs last year (which depends on zgeo.rtree). > >> > > >> > If anybody has a better suggestion (maybe backport zgeo.spatialindex > >> > to Zope 2, but would it be really useful ?), just tell me. > >> > > >> > Regards, > >> > > >> > Eric > >> > >> Hi Eric, > >> > >> Sorry I missed you on IRC this weekend. I need zgeo.spatialindex to work > >> on Zope 2.10 too, but I am using it as a very specialized container > >> index and not as a catalog plugin. > >> > >> I'd like to help with the Zope 2 catalog index. What would you think > >> about developing it as a separate product? > >> > >> 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 > > > > _______________________________________________ > Community mailing list > [email protected] > http://lists.gispython.org/mailman/listinfo/community > _______________________________________________ Community mailing list [email protected] http://lists.gispython.org/mailman/listinfo/community
