<br><br>On Thursday, May 3, 2012, Ruben Schoenefeld wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi -<br>
<br>
I have been using OpenLayers 2.10 / GeoExt 1.0 / ExtJS 3.2.1 for a while now and decided it's time to upgrade to OpenLayers 2.11. Ever since I did, I have a problem with my two (mutually exclusive) overlays. Here's how I created them:<br>
<br>
l_layer_route = new OpenLayers.Layer.Vector<br>
( "Utah State Routes"<br>
, { "strategies":<br>
[ new OpenLayers.Strategy.BBOX()<br>
]<br>
, "protocol": new OpenLayers.Protocol.WFS(<br>
{ "version": '&G_WFSVERSION.'<br>
, "srsName": 'EPSG:26912'<br>
, "url": '&G_WFSMAP.'<br>
, "featureType": '&G_WFS_ROUTE.'<br>
, "featureNS": '&G_GEOSERV_NAMESPACE.'<br>
, "geometryName": 'GEOM'<br>
})<br>
, "visibility": true<br>
, "styleMap": l_style_route<br>
, "minResolution": 0.298582153289307<br>
, "maxResolution": 20<br>
, "units": 'm'<br>
, "alwaysInRange": false<br>
}<br>
);<br>
<br>
l_layer_centerline = new OpenLayers.Layer.Vector<br>
( "Local Street Centerlines"<br>
, { "strategies":<br>
[ new OpenLayers.Strategy.BBOX()<br>
]<br>
, "protocol": new OpenLayers.Protocol.WFS(<br>
{ "version": '&G_WFSVERSION.'<br>
, "srsName": 'EPSG:26912'<br>
, "url": '&G_WFSMAP.'<br>
, "featureType": '&G_WFS_CENTERLINE.'<br>
, "featureNS": '&G_GEOSERV_NAMESPACE.'<br>
, "geometryName": 'GEOM'<br>
})<br>
, "visibility": false<br>
, "styleMap": l_style_centerline<br>
, "minResolution": 0.298582153289307<br>
, "maxResolution": 4<br>
, "units": 'm'<br>
, "alwaysInRange": false<br>
}<br>
);<br>
<br>
The locations in the WFS protocol entries are populated when the page is run. The routes layer contains fewer records "per area" than the street centerline layer, so it should be okay to display it at 20 m / pixel. The centerline layer should be displayed at 4 m / pixel. I've got the following resolutions on the map, which come from the first base map that I add:<br>
[4891.96999883583, 2445.98499994708, 1222.99250010583, 611.496250052917, 305.748124894166, 152.8740625, 76.4370312632292, 38.2185156316146, 19.1092578131615, 9.55462890525781, 4.77731445262891, 2.38865722657904, 1.19432861315723, 0.597164306578613, 0.298582153289307]<br>
<br>
When I initially load the map, the resolution is 1222.99250010583 m / pixel, to display the whole state of Utah. The extent of the map on my screen is -296596.91381471, 3855627.9299551, 1199122.9138147, 4892725.5700449.<br>
<br>
All the layers (base maps and overlays) use the EPSG:26912 projection.<br>
<br>
So from that, as expected, neither the routes or centerline layers are loaded, which is great and as I expect it. As you can see in the layer definition for the routes layer (the first of the two), its visibility is "true" when the layer is created. Yesterday, more or less on accident, I used the layer switcher to switch from the routes layer to the centerline layer, which happens by executing this:<br>
l_layer_route.setVisibility(false);<br>
l_layer_centerline.setVisiblity(true);<br>
<br>
This worked fine in OpenLayers 2.10, but since I switched to 2.11, what happens now (while displaying the whole state) is that it first loads all the data for the routes layer of that huge extent, which takes forever and is multiple MB of data and then it loads all the data for the centerline layer, which is too much for Firefox and I get it to crash.</blockquote>
<div><br></div><div><br></div><div>Woo. That's indeed unexpected and abnormal.</div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
So my questions:<br>
1) Why would OpenLayers want to load the data when maxResolution on the layers clearly tells it that it shouldn't?</blockquote><div><br></div><div><br></div><div>It should not.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2) Why would OpenLayers want to load the data for the routes layer when I am setting its visibility to false but it didn't care to do that when I initially loaded the page (and shouldn't have)?</blockquote><div><br>
</div><div><br></div><div>It should not.</div><div><br></div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
3) What am I doing wrong?<br>
<br>
Because I first experienced this problem with OpenLayers 2.11, I switched back to 2.10 just to see if it happens there, and it didn't. I also upgraded GeoExt to 1.1 now and that doesn't make a difference. Also, initially, I didn't have the minResolution set, but only maxResolution. But I added it now, but that doesn't make a difference.<br>
<br>
Please let me know if further information is needed.</blockquote><div><br></div><div><br></div><div>I'd be curious to know if the same issues exist with 2.12-rc2. And it'd be great to come up with a minimal example demonstrating the problem.</div>
<div><br></div><div>Cheers,<span></span></div><br><br>-- <br>Eric Lemoine<br><br>Camptocamp France SAS<br>Savoie Technolac, BP 352<br>73377 Le Bourget du Lac, Cedex<br><br>Tel : 00 33 4 79 44 44 96<br>Mail : <a href="mailto:eric.lemoine@camptocamp.com">eric.lemoine@camptocamp.com</a><br>
<a href="http://www.camptocamp.com">http://www.camptocamp.com</a><br><br>