Changes between Version 29 and Version 30 of BluePrintRegionsAndIncidents

Timestamp:

04/11/11 00:09:35 (14 years ago)

Author:

Pat Tressel

Comment:

--

BluePrintRegionsAndIncidents

@@ -60 +60 @@
   * Already present in gis_config, and needed for region selection:
    * Map center and zoom (so map can be positioned appropriately for the region).
-  * Allow the set of selected layers to differ per region.
-    Options for implementation:
+  * Allow the set of available base layers and the initial selected base layer to differ per region.
+    (Implementation detail: Take enabled flag out of gis_layer_* and instead have a list multiple field in gis_config that enumerates the enabled layers for that config. Add a field for the selected base layer.)
+  * Allow the set of available (resource) overlays (a.k.a. "internal" overlays or "internal features") and the initial selected overlays to differ per region.
+    Options for implementation:  (Pat: In the following, I believe we were referring to different aspects -- which overlays were selected, i.e. "visible" versus which were made available to select, i.e. "enabled". In any case, both suggested implementations now seem incorrect.)
    * Pat: Inserting a reference to a region in layer_feature *deselects* the layer for that on the map for that region. This is consistent with an empty region set meaning all regions have that layer, and is easier to maintain if new regions are added -- don't need to do anything.)
    * Fran: Inserting a reference to a region in layer_feature *restricts* the layer to just that region since this is the most usual use-case where a layer only applies to a particular region.
-   * Pat: Take the enabled flag out of gis_layer_* and instead have a list multiple field in gis_config that enumerates the enabled layers for that config. The decision whether all layers or none are enabled if this gis_config field is empty can be made in the map display function. Only place that choice affects gis_config is in the tooltip for this field, and other user help info.
+   * Pat: (After getting that confusion cleared up...):
+    * Take the "enabled" flag out of gis_layer_feature and instead have a list multiple field in gis_config that enumerates the enabled internal overlays for that config.
+    * Take the "visible" field out of gis_layer_feature and add another list multiple field in gis_config for which are initially selected.
+  * Allow selection of "external" overlays to be specified in gis_config (both "enabled" and "visible" as for internal overlays). (The set of possible external overlays might be hard coded -- changed when support is added for each.) (Note Fran says adding another "folder" in the map viewer is "not so easy".)
 
  * Generate a regions menu from the gis_config table. Include site and personal configs in the menu. Add deployment setting to enable the regions menu and specify a label for the menu head.