<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
<br>Hi: FYI in trunk, we have the requirement for storing geometries in the format 'minx,miny,maxx,maxy'.<br><br>This format is adhered to for:<br><br>- importing metadata into the repository<br>- searching metadata spatially (server.util.query_bbox() and server.util.bbox_not_query())<br>- presenting metadata<br><br>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.<br><br>Is there benefit to storing geometries as WKT in the repository? Or WKB (maybe for better performance)? Or something else?<br><br>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).<br><br>Comments?<br><br>..Tom<br><br>[1] http://trac.gispython.org/lab/wiki/Shapely<br> </body>
</html>