Changes between Version 3 and Version 4 of ExtendedRegions

Timestamp:

Oct 24, 2012, 7:41:20 AM (12 years ago)

Author:

jesseeichar

Comment:

--

ExtendedRegions

@@ -19 +19 @@
   * bbox
  * Add optional geometry for each region (in addition to bbox)
- * integrate into XmlSearch and Csw so that the region id can be used to look up the geometry of the region for a spatial filter
+ * integrate into !XmlSearch and Csw so that the region id can be used to look up the geometry of the region for a spatial filter
  * Add a configurable strategy object for that allows the region implementation to be easily pluggable.  For example it might be based on a table in the database or wfs 
 
@@ -93 +93 @@
 </regions>
 }}}
- * GetGeom
+ * !GetGeom - will return the geometry for the region. If the geometry does not have a geometry then the bbox will be used to construct a polygon.
   * Params
    * id - required (if multiple are provided then multiple geometries will be returned)
@@ -105 +105 @@
 }}}
 
+The XmlSearch API will be modified so the geom parameter can either be WKT or have the form: region:id, where id is the id of the region to use as a geometry.  If the region has a geometry then that geometry will be loaded otherwise the bbox will be used to create a polygon geometry.
+
+The CatalogSearcher (part of Csw GetRecords) will be modified to replace elements with the attribute gml:id which have the form: region:id
+
+The actual implementation will consist of the services and a strategy object that can be configured the geonetwork configuration files.  The intention is that for a particular application the strategy object can be implemented and configured for use.  The default implementation will be the same as
+
 === Backwards Compatibility Issues ===