<html>
<head>
<style type="text/css">
<!--
body { margin-right: 4px; margin-top: 4px; font-variant: normal; margin-left: 4px; margin-bottom: 1px; line-height: normal }
p { margin-top: 0; margin-bottom: 0 }
-->
</style>
</head>
<body style="margin-right: 4px; margin-top: 4px; margin-bottom: 1px; margin-left: 4px">
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">Bill,</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">This is a shameless plug for GeoMoose functionality, it was prompted by your comments below however, so I don't feel too bad :c)</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">* GeoMoose can handle almost an unlimited number of layers (Browser memory being the limit for the most part), we have just over 170 layers in our internal installation (and growing)</font> </p>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">* It has had a expand/collapse feature since day one.</font> </p>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">* It has had grouping available via MapFiles from day one, and the last couple of versions have had grouping with control in the client, while still maintaining individual layer control at the user end. You can group layers in a single mapfile for a single image return, and still be able to control the separate layer on/off visibility in the client.</font> </p>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">* Most (if not all) of the layer specific controls are icon based. (you can also add layer specific user extensions as well, that's another post though)</font> </p>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">* Each layer (or group of layers) is controlled via it's own mapfile, while this might seem cumbersome to manage, it does allow for separate and integrated management of data layers by many data custodians, which is what GeoMoose was originally designed for, many data custodians doing their own thing. It's also very good for automation purposes in general.</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">Check it out, the new GeoMoose site ( </font><a href="http://www.geomoose.org)"><i><font color="#0000ff" face="Comic Sans MS" size="3"><u>www.geomoose.org)</u></font></i></a><font size="3" face="Comic Sans MS"> has some live demos of the interface running, which demonstrate many of it's capabilities in online working versions.</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">bobb</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<br>
<br>
>>> Bill Thoen <bthoen@gisnet.com> wrote:<br> </p>
<div style="background-color: #f3f3f3; margin-right: 0; margin-top: 0; margin-left: 15px; margin-bottom: 0; border-left: solid 1px #050505; padding-left: 7px">
<p style="margin-top: 0; margin-bottom: 0">
<br>
<br>
In my case I was happily building a pretty good tool in Open Layers, and<br>the first thing a new client wanted was support for up to 100 layers,<br>which is not do-able in OL because the layer switcher doesn't have a<br>scrollbar and it maxes out when the list of layer reaches the bottom of<br>the map window. It also has no grouping ability to treat a group of<br>layers as a single layer, nor does it provide a expand/collapse feature,<br>or show layer icons. Other than the grouping issue (which I think is not<br>going to be as useful as the client thinks, even if I get it to work the<br>way they want) HTML Legends cover a lot of ground with not a lot of code<br>needed. Still, I think I should look at this GeoMoose some time. It<br>sounds pretty good.<br><br><br><br><br><br><br><br><br><br>
</p>
</div>
</body>
</html>