Changes between Version 4 and Version 5 of BluePrintRegionsAndIncidents

Timestamp:

02/16/11 14:38:31 (14 years ago)

Author:

Pat Tressel

Comment:

--

BluePrintRegionsAndIncidents

@@ -33 +33 @@
 In order to support configuring and selecting regions:
  * Move any region-specific configuration into gis_config.  This currently means:
-  * A location representing a region (see following).
+  * A location representing a region (see below).
   * The hierarchy labels, depth, and settings appropriate for that area.
     (Language translation is not sufficient here. E.g we don't have "provinces" and "districts"
     in the US but those are perfectly legal US English words. Different areas also have
     different depths of hierarchy, and different choices about a "strict" hierarchy.)
+    Hierarchy settings are:
+   * "Strict" -- specific locations can only be attached to the hierarchy at its maximum level.
+   * "Parent required" -- specific locations need a parent location selected from the hierarchy.
+     (This is used to assist forming regions in the absence of boundary data -- see below.)
   * A flag for whether this gis_config represents a region.
   * A label to use on a menu of regions.
@@ -52 +56 @@
    * The generic gis_config.
 
-
 The "region location" associates specific locations to the region.
 There are four main ways a region location can specify this association:
- * Specific locations can have the region location as an ancestor.
-   E.g. the region might be a city.  Specific locations can be assigned a parent in the hierarchy.
+ * The region location can be in the hierarchy, and specific locations can have
+   the region location as an ancestor. (E.g. the region might be a city.)
+   Turning on the "parent required" flag means selecting a parent is mandatory,
+   which would be appropriate in this case.
+ * The region location can contain a boundary polygon. Specific locations with
+   point or polygon data can be tested for overlapping the region polygon.
+ * The region can specify a point and a radius. Specific locations with point or
+   polygon data can be tested for overlapping this circle.
+ * The region location can be a "location group" (a list of locations that are
+   each appropriate as region locations). (For instance, the region might consist
+   of several counties in a state.) A specific location is tested against each
+   of the locations in the group. (This would allow recursion, if we permit a
+   location group to be a member of a location group. That's not required, though.)
 
 === Incident discussion ===