Changes between Version 10 and Version 11 of ExtendedRegions

Timestamp:

Jan 3, 2013, 6:39:21 AM (12 years ago)

Author:

jesseeichar

Comment:

--

ExtendedRegions

@@ -125 +125 @@
 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
+For example:
+
+ * Search for metadata intersecting with france:
+  * http://localhost:8080/geonetwork/srv/eng/q?fast=index&from=1&to=20&geometry=region: http%3A%2F%2Fgeonetwork-opensource.org%2Fregions%2368
+ * Search within the union of France and Switzerland
+  * http://localhost:8080/geonetwork/srv/eng/q?fast=index&from=1&to=20&geometry=region:kantone:22,kantone:10
+
+The !CatalogSearcher (part of Csw !GetRecords) will be modified to replace elements with the attribute gml:id which have the form: region:id.
+
+For example:
+
+
+'''Implementation Notes'''
 
 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 current implementation factored out into the strategy object.
+
+The main strategy object is called:
+
+RegionsDAO which is the entry point into searching and querying regions.  See the javadocs of this class for information on how to use the class and implement new custom regions strategies.
 
 '''Example URLS'''