Ticket #1830 (closed feature: fixed)
Give the bbox strategy an option to make it more agressive
| Reported by: | tschaub | Owned by: | crschmidt |
|---|---|---|---|
| Priority: | minor | Milestone: | 2.8 Release |
| Component: | Strategy | Version: | 2.7 |
| Keywords: | Cc: | ||
| State: | Complete |
Description
The bbox strategy currently only decides that the existing feature set is invalid if the existing bounds don't contain the new bounds. There are cases where it makes sense to be more aggressive with regard to requesting new data. Several of these cases are addressed by considering the change in resolution between requests in addition to the bounds. This still belongs in a bbox strategy because it is about managing successive requests for data within some bounding box. It is sort of like saying "request new data if the user navigates beyond the old bounds or is viewing an area much smaller/bigger than the previous request". One way to capture the smaller/bigger area than previous request is to add a resolution factor.
The resFactor option works in both ways (area getting bigger or smaller). If you set a resFactor of 2 and you zoom in to a point where your viewport is half as wide (on the ground), then new data will be requested. If you zoom back out so your viewport is twice as wide again (on the ground), data will again be requested. Setting a resFactor of 1 causes data to be requested with each change in resolution (this is equivalent to the behavior of the current WFS layer).
Attachments
-
resFactor.patch
(3.6 KB) - added by tschaub
22 months ago.
- add a resFactor option to make strategy more agressive
-
strat.patch
(3.8 KB) - added by crschmidt
18 months ago.
