Opened 15 years ago
Closed 14 years ago
#1421 closed enhancement (fixed)
WFS Extension doesn't request displayed extent using bbox
Reported by: | mlechner | Owned by: | mhugent |
---|---|---|---|
Priority: | major: does not work as expected | Milestone: | Version 1.5.0 |
Component: | WMS | Version: | Trunk |
Keywords: | WFS bbox bounding box | Cc: | |
Must Fix for Release: | No | Platform: | All |
Platform Version: | Awaiting user input: | no |
Description
Using the WFS-Extension to request vectordata from a WFS-Service doesn't request only the data of the displayed extend using bbox in requeststring. It request the whole layer! This could be pretty (too) much.
By the way "WFS" is missing in Component-list in this trac system.
Change History (5)
comment:1 by , 15 years ago
Component: | Vectors → Data Provider |
---|---|
Milestone: | Version 1.0.0 → Version 1.1.0 |
Must Fix for Release: | Yes → No |
Platform: | Debian → All |
Type: | bug → enhancement |
comment:2 by , 15 years ago
a side effect of that behaviour also is, that the provider only shows a snapshot of the content and there is no way to update it other than removing and re-adding the layer or reloading the project.
comment:3 by , 15 years ago
wouldn't it be better to preload some larger bbox than the viewed extend (easy to implement). I try to use a WFS serving a huge amount of data for whole europe (OpenStreetMap-WFS) - but I only need the features in a small part (surrounding of Freiburg, Germany) wich is already a lot of data. Loading the whole layer takes about five minutes (and I used a relatively small one for testing)
comment:4 by , 15 years ago
Component: | Data Provider → WMS+WFS |
---|---|
Owner: | changed from | to
comment:5 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
An option to fetch only the feature intersecting the current map extent is in the svn version.
Hi Marco
The WFS provider fetches the whole layer the first time and stores all in memory. Because it assumes that the user soon will do some panning and zooming and that will be a lot faster if everything is in memory. So the implemented solution requires more memory but is much faster for many zoom and pan actions.
And if a WFS layer is the first one, QGIS would need to fetch the whole layer anyway.
However, it could be a feature enhancement to give the user the possibility to only request the data in the current view extent (those features then would stay the same even if the user pans or zooms out afterwards). I'm therefore changing this ticket into enhancement (and category 'data provider')
Marco