[Chameleon-dev] [Bug 31] New: [Chameleon]Class Status ON/OFF & Class Grouping Definisions
Wed, 30 Jul 2003 16:24:42 -0400

           Summary: [Chameleon]Class Status ON/OFF & Class Grouping
           Product: Chameleon
           Version: 1.1
          Platform: PC
        OS/Version: Windows 2000
            Status: NEW
          Severity: enhancement
          Priority: P4
         Component: Core

!!GIS Team's Data Optimization Procedures, Utilities and New Direction


This document was started July 30th, 2003 to deal with the complex issue of data
optimization. It has been brought to the GIS Teams attention that their need to
be a great understanding of the steps and tools used during a large or small
data optimization projects. Also, it is important to make the efforts of the GIS
Team more efficient, more practical and re usable towards other data/none data
projects. This document will help everyone on the GIS Team understand the
general steps involved during data optimization. Hopefully allowing the GIS Team
to define a better direction for the efforts made by all of us.

The purpose of this Wiki document is to:
# Outline the data optimization procedures currently being done.
# Identify and evaluate the GIS software/utilities and scripting language(s)
currently being used to clean, optimize the data for the web.
# Define the direction the GIS Teams future efforts with respect to building
automated data optimization scripts.
# Identify specific utilities that could be build and allow the optimization to
be less depended on licensed GIS software (eg. FME, ArcGIS).

This enhancement request will be better defined during SLD development. This bug
was entered to have this issue visibly documented.

In an effort to have more complete Legend Templates automatically generated from
map files, either by using the LegendTemplate Widget, ContextSelect Widget or
future developed Widgets; a serious limitation has been noted.  

As most people know ;) the HTML Legend Template allows the user to display
within a legend either: groups, layers or classes. Since, the parameter STATUS
"ON/OFF/DEFAULT" is only used at the Layer level. The applications can only
allowing the user to turn on/off groups of layers at once, or single layers
within the map file. While in the ContextSelect Widget only Layers or groups of
layers can be displayed in a legend.

Since the enhancement of mapscript to have min/max zoom levels defined in the
class, there has been a shift in how we define our layers. Meaning that the
Class Objects can be considered more as the Layer definition, while Layer Object
is used to define the different Data sets.   

So logically, the enhancement request would be to have Classes to be just as
flexible as Layers. 
1)	CLASSSTATUS -> Turn ON/OFF parameter
2)	GROUPCLASS -> To group class when building a legend and to have the ability
to turn ON and OFF the layer(s) in the legend. 

There may be other enhancements required related to this Legend/Class issues.

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

This archive was generated by Pipermail.