<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2873" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Palatino Linotype; COLOR: #000000">
<DIV>Steve - thanks a lot. That helps a tonne. Even just having this as part of the list archives will be useful.</DIV>
<DIV> </DIV>
<DIV>Thanks again for the dbox interface. That is *incredibly* useful.</DIV>
<DIV> </DIV>
<DIV>Chip<BR><BR>>>> Steve Lime <Steve.Lime@DNR.STATE.MN.US> 6/2/2006 12:26 PM >>><BR></DIV>
<DIV style="COLOR: #000000">At this point the documentation is pretty sparce, but the demo shows all the options<BR>at the moment. We developed that capability for a specific project so there will likely<BR>need to be extensions.<BR><BR>The metadata serves 3 primary functions:<BR><BR>1) it allows the creation of what we call metagroups to collect similarly themed layers or<BR>groups<BR><BR>In the demo the following metadata does that:<BR><BR> dlegend_metagroups "foreground,background"<BR> dlegend_foreground_layers_and_groups "pls,lakes,dlgstln2,cities,roads"<BR> dlegend_background_layers_and_groups "drgs,lulc_90cenim3"<BR><BR>The first line tells the parser what groups there are (and what order to render themin the<BR>legend) and the next two lines define membership.<BR><BR>2) is allows the naming of elements that can't be named with normal MapServer map<BR>elements. Obviously metagroups since they are not MapServer constructs cannot be<BR>named. Nor can MapServer groups or layers with more than one named class. In those<BR>cases we name those elements with metadata:<BR><BR> dlegend_foreground_name "Foreground Layers:"<BR> dlegend_background_name "Background Layers:"<BR> dlegend_lulc_90cenim3_name "Landuse/Landcover"<BR> dlegend_pls_name "Public Land Survey"<BR> dlegend_roads_name "Roads"<BR><BR>3) we can alter the legend control element type used for a metagroup, either a checkbox<BR>or a radio button. Yahoo actually mimics that behavior with DHTML and css but the effect<BR>is the same as using a form.<BR><BR> dlegend_background_element "radio"<BR><BR>That's really all there is to it. All other information such as class names, icons and scale limits<BR>are picked up from the regular mapfile structures.<BR><BR>We have immediate needs to make a couple of extensions such as allowing nested <BR>metagroups and setting the default status (open/closed) of a metagroup.<BR><BR>Let me know if this helps and/or if you need more detail. We can post this then as documentation<BR>for the MapScript piece of dlegend...<BR><BR>Steve</DIV>
<P>Outgoing messages, along with any attachments, are scanned for viruses
prior to sending.
<HR>
NOTICE-- This email may contain confidential and privileged information for the
sole use of the intended recipient. Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately and delete all copies.
<P></P>
</BODY></HTML>