There you go: a ticket and an example
http://trac.openlayers.org/ticket/1835
http://dev.openlayers.org/sandbox/igrcic/openlayers/examples/strategy-bbox.html
Cheers, Ivan
On Fri, Nov 14, 2008 at 5:40 PM, Tim Schaub [EMAIL PROTECTED] wrote:
Hey-
Ivan Grcic wrote:
Hi, ive tried Tims patch and i
Hi, ive tried Tims patch and i must say im pretty happy with it. Tnx Tim!
I dont need to filter data depending on number of features
(maxfeatures), but to show all the currently available data for area,
then the cluster strategy jumps in and takes care that there are not
too many features
Hey-
Ivan Grcic wrote:
Hi, ive tried Tims patch and i must say im pretty happy with it. Tnx Tim!
I dont need to filter data depending on number of features
(maxfeatures), but to show all the currently available data for area,
then the cluster strategy jumps in and takes care that there are
Thanks for putting this patch together Tim.
Initially Chris wanted that the bbox strategy behave aggressively on
zoom in, but, as an optimization, only if the number of features in
the layer is not lower than the maxfeatures value set in the protocol.
The change you're proposing wouldn't allow
Hey-
Eric Lemoine wrote:
Thanks for putting this patch together Tim.
Initially Chris wanted that the bbox strategy behave aggressively on
zoom in, but, as an optimization, only if the number of features in
the layer is not lower than the maxfeatures value set in the protocol.
Ok, I think
On Thu, Nov 13, 2008 at 01:52:02PM -0700, Tim Schaub wrote:
Hey-
Eric Lemoine wrote:
Thanks for putting this patch together Tim.
Initially Chris wanted that the bbox strategy behave aggressively on
zoom in, but, as an optimization, only if the number of features in
the layer is not
Hey-
Oh, and one more thing...
Eric Lemoine wrote:
Thanks for putting this patch together Tim.
Initially Chris wanted that the bbox strategy behave aggressively on
zoom in, but, as an optimization, only if the number of features in
the layer is not lower than the maxfeatures value set in
Hi all,
I also began using cluster strategy a lot recently, and im seeing lots
of places where it can be improved. Here im talking only about using
it with BBOX strategy, because Fixed strategy is of no use when we're
talking about large number of features (1000+) (just to be sure,
there is no
Hey-
This has gotten too scattered for me to follow, but I'll put in a few
thoughts.
The BBOX strategy is intentionally lazy. And I agree that we can add
properties to make it more aggressive (optionally). I think it is
short-sighted to tie this property to a maxfeatures or limit parameter
On Wed, Nov 12, 2008 at 09:25:20AM -0700, Tim Schaub wrote:
The BBOX strategy is intentionally lazy. And I agree that we can add
properties to make it more aggressive (optionally). I think it is
short-sighted to tie this property to a maxfeatures or limit parameter
in a request.
I don't
On Wed, Nov 12, 2008 at 01:56:11PM -0700, Tim Schaub wrote:
Hey-
Christopher Schmidt wrote:
On Wed, Nov 12, 2008 at 09:25:20AM -0700, Tim Schaub wrote:
The BBOX strategy is intentionally lazy. And I agree that we can add
properties to make it more aggressive (optionally). I think it
Hey-
Ivan Grcic wrote:
Hi all,
I also began using cluster strategy a lot recently, and im seeing lots
of places where it can be improved. Here im talking only about using
it with BBOX strategy, because Fixed strategy is of no use when we're
talking about large number of features (1000+)
Just for the record, I've bumped into this exact problem with a client
recently as well.
Is there anything analogous to maxfeatures in other formats besides
WFS? The only reason I can think of why it shouldn't be in BBOX is
that it might not be general enough.
On Tue, Nov 11, 2008 at 7:33 AM,
On Tue, Nov 11, 2008 at 07:36:22PM +0100, Eric Lemoine wrote:
Yeah, we could add a new option to the bbox strategy. If its value is
null the strategy behaves as currently. If it's non-null, the strategy
fetchs new data on zoom in if the current number of features in the
layer is equal or
Strategy People,
When I use the Layer.WFS, I often set a 'maxfeatures' parameter, to
limit the amount of data that is loaded at once. The result of this is
that when a user zooms in, I want the previous set of data to be
invalidated.
Ideally, of course, if the number of features returned was
On Tue, Nov 11, 2008 at 11:05:11AM -0500, Sebastian Benthall wrote:
Just for the record, I've bumped into this exact problem with a client
recently as well.
Is there anything analogous to maxfeatures in other formats besides
WFS? The only reason I can think of why it shouldn't be in BBOX is
Yeah, we could add a new option to the bbox strategy. If its value is
null the strategy behaves as currently. If it's non-null, the strategy
fetchs new data on zoom in if the current number of features in the
layer is equal or higher to the option value. Eric
2008/11/11, Christopher Schmidt
17 matches
Mail list logo
