[pycsw-devel] repository geometry storage

[Tom Kralidis]

Hi: FYI in trunk, we have the  requirement for storing geometries in the format 'minx,miny,maxx,maxy'.

This format is adhered to for:

- importing metadata into the repository
- searching metadata spatially (server.util.query_bbox() and server.util.bbox_not_query())
- presenting metadata

For spatial searching, we are using Shapely [1] to perform operations like intersects (ogc:BBOX) and disjoint (ogc:Not/ogc:BBOX).  We transform the geometry to wkt (server.util.bbox2wkt) before passing to Shapely.

Is there benefit to storing geometries as WKT in the repository?  Or WKB (maybe for better performance)?  Or something else?

The change would be easy to implement, the question is would this be of value, in the context of the life cycle of catalog metadata (import/search/present).

Comments?

..Tom

[1] http://trac.gispython.org/lab/wiki/Shapely
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/pycsw-devel/attachments/20110406/ab43d36a/attachment.html