Jan and I need to serialize Plone collections to KML efficiently,
without waking up objects, and to help I have written new
zgeo.plone.geographer and zgeo.plone.kml packages.
zgeo.plone.geographer adds a "zgeo_geometry" metadata column to your
site catalog that is meant to hold geometry values like {'type':
'Point', 'coordinates': (-105, 40)}, and also registers an event
subscriber that reindexes objects whenever you georeference them using
the IWriteGeoreferenced adapter from zgeo.geographer. This keeps the
catalog metadata up to date. Note that zgeo.plone.geographer does not
add a spatial index to your site catalog.
zgeo.plone.kml provides a multi-adapter for the Collection content type
and registers a "kml-document" view. It also has a wrapper for catalog
brains that depends on the metadata installed by zgeo.plone.geographer.
Yes, there is a profusion of packages, but I'm finding it easy to manage
them with the help of a "policy product" as described in Martin Aspeli's
Plone 3 book.
Eric B: how does the zgeo_geometry metadata fit with your own catalog
work. Have I duplicated your work, and if so, what can we do to reconcile?
Sean
_______________________________________________
Community mailing list
[email protected]
http://lists.gispython.org/mailman/listinfo/community
