Something else to experiment with is if the filter itself is taking a long time. Take the fixed strategy out and also the filter and zoom in and around and see what the performance is.. if it is still problematic you can look into the following options: -- only show the data at higher zoom levels (i.e. closer to the ground) - that way the bbox is smaller. -- think about using a clustering strategy. For this to work it should really be done on the server, but you can experiment with it on the client. (search the OL examples for cluster). Toby
On 7 December 2011 08:09, Toby R <[email protected]> wrote: > Yes, it means your requesting your features twice, one the whole > dataset, and once for the bbox. Remove the fixed strategy. > Toby > > > > On 7 Dec 2011, at 07:56, Shadin <[email protected]> wrote: > >> still don't know what to do. >> the points take 1 min to appear over the map. >> >> /*Then you probably need to index the data and use a tile cache in front >> of the WMS. */ >> would that help with this problem ? >> >> >> I'm using 2 strategies with the vector layer >> [new OpenLayers.Strategy.Fixed(), >> new OpenLayers.Strategy.BBOX()] >> >> would that make any problem ? >> >> >> >> >> /*If you are using geoserver, make sure that distance is in the units of >> native projection.*/ >> how i can do that ? >> >> >> >> -- >> View this message in context: >> http://osgeo-org.1803224.n2.nabble.com/DWITHIN-Spatial-Filter-tp7062101p7069663.html >> Sent from the OpenLayers Users mailing list archive at Nabble.com. >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.osgeo.org/mailman/listinfo/openlayers-users _______________________________________________ Users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/openlayers-users
