Bug report #14145: Snapping to WFS - QGIS Application - QGIS Issue Tracking

Bug report #14145

Snapping to WFS

Added by Heikki Vesanto almost 9 years ago. Updated over 5 years ago.

Status:	Closed
Priority:	Normal
Assignee:	-
Category:	Unknown
Affected QGIS version:	master	Regression?:	No
Operating System:		Easy fix?:	No
Pull Request or Patch supplied:	No	Resolution:	end of life
Crashes QGIS or corrupts data:	No	Copied to github as #:	22147

Description

Issue I believe with indexing of snapping.

If you add in a WFS layer non-cached, so that it only loads in the extents of your screen. Turn snapping on for that layer. Create a new feature in a different layer (at which point the WFS layer is indexed in order to be snapped to quickly). Then pan the map to bring in new features from the WFS, you can not snap to the new features. The features in your initial view extent can be snapped to, but the new ones cannot be. Turning editing off and on does not resolve the issue.

I have attached an image which may clarify the issue.

I have tested this on 2 different WFS servers.

It can be tested on the Vienna city WFS from:
http://data.wien.gv.at/daten/geo?version=1.1.0&service=WFS&request=GetCapabilities

Tested in QGIS 2.8.6 and 2.13 (2bacece) in Windows. Cannot test in 2.12 as the WFS does not fully support non-cached WFS.

History

#1 Updated by Heikki Vesanto over 8 years ago

Tested in 2.14 as well. Still and issue. It would be good if indexing for snapping could be turned on/off either completely or on a layer by layer basis.

#2 Updated by Zlata Popelnuh over 8 years ago

Heikki Vesanto wrote:

Tested in 2.14 as well. Still and issue. It would be good if indexing for snapping could be turned on/off either completely or on a layer by layer basis.

I am experiencing the same issue in 2.14. Snapping stops working. Auto-trace does toggle snapping but temporarily.