<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>In general, I would advise against having 11 seperate layers on a map.<br>It's possible that this really is neccesary, but in general, 11 layers
<br>is more likely to confuse the user: You're the map maker, make some<br>decisions about how the map should look, and combine some of the layers.</blockquote><div><br>Well, I think there are many situations where one would want to give a user, which might not be the general public, a _lot_ of layers and I would argue that OL should should support this.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I could be wrong, especially in the case of analysis, but in general,<br>I've found that as you add more layers, users feel less comfortable,
<br>rather than more, despite the addtional level of control it offers.<br><br>> When I zoom in the performances are very very poor and when I go to the<br>> max zoom level I can see that the requests send to the web server are
<br>> about 1000.</blockquote><div><br>I have found that with mapserver vector layers it is often better to just have a single tile as the effort creating the tile lies in the DB or shapefile access and because Mapserver will, depending on setting, either discard elements at the edges of tiles (which would be in the middle of an OL tiled window), or the symbols do not line up well or a duplicated on more than one tile.
<br><br>I have still an experimental version of my OL at <a href="http://www.yunnanexplorer.com/yunnanmap.html">www.yunnanexplorer.com/yunnanmap.html</a>. Move the red sliders to make a layer visible, sort stacking order by dragging and dropping, or flicker a layer with the check-box.
<br><br>The earthquake layers towards the bottom are single tile mapserver tiles against PostGIS.<br><br>Ludwig<br> </div><br></div><br>