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, Christopher Schmidt <[EMAIL PROTECTED]> wrote: > 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 fewer than > $max_features, there would be no need to invalidate the previous dataset > when zooming in (only when zooming out). > > The current BBOX strategy does not allow for this as an option of any > kind. > > Is adding this type of support something that belongs in the BBOX > strategy, or somewhere else? > > Regards, > -- > Christopher Schmidt > MetaCarta > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev > _______________________________________________ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev
