Hi,<br><br>In my sandbox you can find an example of how to use WFS transactional trying to minimize the ammount of data transmitted between client and server. It's quite based in the mentioned Andreas' example, it's just another resource oriented slightly different. <br>
What it does, as explained there, is to load first only a WMS layer, and feature data will only be retrieved when clicking on them. It can be easily adapted to your needs if you want to load more than one feature at a time (the example is WFS-T-oriented). You can find it here:<br>
<br><a href="http://dev.openlayers.org/sandbox/sonxurxo/wfs-t/examples/wfs-transaction-optimized.html">http://dev.openlayers.org/sandbox/sonxurxo/wfs-t/examples/wfs-transaction-optimized.html</a><br><br><br clear="all">Best regards,<br>
<br>Xurxo Méndez Pérez<br><br><a href="http://www.sonxurxo.com/" target="_blank">http://www.sonxurxo.com</a><br>
<br><br><div class="gmail_quote">2010/10/3 Andreas Hocevar <span dir="ltr"><<a href="mailto:ahocevar@opengeo.org">ahocevar@opengeo.org</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi,<br>
<br>
from what you describe, your use case screams for rendering features on the server and maintaining only a layer of selected features (using the GetFeature control) on the client. For this, however, you would need a WMS or something similar that can render your features on the server.<br>
<br>
You may want to have a look at <a href="http://ol-performance.appspot.com/" target="_blank">http://ol-performance.appspot.com/</a>, especially the "Combine OGC Services Wisely" section which shows alternative ways of feature selection.<br>
<br>
Also, don't expect too much performance improvements from the Cluster strategy. It will speed up rendering and panning for sure, but the real bottleneck is parsing the features as they arrive from the server. The cluster strategy is a great way to improve the perception of otherwise overcrowded maps, but it is not an all-purpose cure for performance issues.<br>
<br>
Regards,<br>
<font color="#888888">Andreas.<br>
</font><div><div></div><div class="h5"><br>
On Oct 3, 2010, at 15:57 , crb wrote:<br>
<br>
><br>
> Hi Andreas. Thanks for the reply (and for the reply to my other post of the<br>
> same day).<br>
><br>
> The reason for the extra layer for the selected features is because we want<br>
> to show selected features at all scales, but the vector layer for our<br>
> "locations" layer has too many features to display at all scales: it drags<br>
> IE to a crawl, rendering it unusable. So for our "main", location features<br>
> layer, we display only at the 10th zoom level and we display only the<br>
> features within the maps current extent (requiring a callback to the server<br>
> every time the extent changes) and we use a cluster strategy for it. This<br>
> helps with the locations layer (sort of -- I'll be posting again shortly in<br>
> another thread regarding problems we're having with the cluster strategy)<br>
> but so that the user can always see all the features that they've selected,<br>
> we need a 2nd vector layer (or equivalent) to display only selected features<br>
> at all scales.<br>
><br>
> Even given that, we've decided to hold off adding a 2nd selected features<br>
> layer for to make sure we can get the cluster strategy working the way we<br>
> need it first. We'll likely revisit this, but we have to resolve our other<br>
> issue first...<br>
> --<br>
> View this message in context: <a href="http://osgeo-org.1803224.n2.nabble.com/vector-layer-with-highest-zIndex-not-overlaying-other-vector-layers-tp5592538p5596175.html" target="_blank">http://osgeo-org.1803224.n2.nabble.com/vector-layer-with-highest-zIndex-not-overlaying-other-vector-layers-tp5592538p5596175.html</a><br>
> Sent from the OpenLayers Dev mailing list archive at Nabble.com.<br>
> _______________________________________________<br>
> Dev mailing list<br>
> <a href="mailto:Dev@lists.osgeo.org">Dev@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/openlayers-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/openlayers-dev</a><br>
<br>
<br>
<br>
</div></div><div class="im">--<br>
Andreas Hocevar<br>
OpenGeo - <a href="http://opengeo.org/" target="_blank">http://opengeo.org/</a><br>
Expert service straight from the developers.<br>
<br>
_______________________________________________<br>
</div><div><div></div><div class="h5">Dev mailing list<br>
<a href="mailto:Dev@lists.osgeo.org">Dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/openlayers-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/openlayers-dev</a><br>
</div></div></blockquote></div><br>