Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance during digitizing in a shape-layer if other big layers in project are snap-able #16005

Closed
qgib opened this issue Dec 14, 2012 · 4 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Digitizing Related to feature digitizing map tools or functionality

Comments

@qgib
Copy link
Contributor

qgib commented Dec 14, 2012

Author Name: Joachim Deutmann (Joachim Deutmann)
Original Redmine Issue: 6876
Affected QGIS version: 1.8.0
Redmine category:digitising


Layer with many elements reduce performance during digitizing in the project significantly if the layers snap is on. This applies to all of the tested file formats or databases (Shape, XML, KML, SpatiaLite, PostgreSQL ...) If these layers, however, saved as MapInfo Tab layer, the performance increases drastically. For example, i generate a vector grid with 170,000 polygons and stored it as well as ESRI-shape and as MapInfo-tab. Both layers are in the actual project. After that i create a new polygon-shape layer in the same project. Then i turn "snap on" on the big TAB-Layer and create an object in new shape layer (It doesn't matter, if it is created "normal" or with the plugin "new memory layer" or if it is an existing Shapelayer). The performance difference between snap on the TAB-layer (high speed) and snap on the SHP-layer (very, very slow) during digitizing is extreme.

@qgib
Copy link
Contributor Author

qgib commented Dec 30, 2012

Author Name: Giovanni Manghi (@gioman)


  • priority_id was changed from High to Normal

@qgib
Copy link
Contributor Author

qgib commented Apr 30, 2017

Author Name: Giovanni Manghi (@gioman)


  • easy_fix was configured as 0
  • regression was configured as 0

@qgib
Copy link
Contributor Author

qgib commented Mar 1, 2018

Author Name: Giovanni Manghi (@gioman)


Please test with a recent QGIS release (2.18 or 3), if the issue/request is still valid change the affected version accordingly, if is fixed/implemented then close the ticket. Thanks!


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Feb 23, 2019

Author Name: Jürgen Fischer (@jef-n)


  • resolution was changed from to no timely feedback
  • status_id was changed from Feedback to Closed

@qgib qgib closed this as completed Feb 23, 2019
@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Digitizing Related to feature digitizing map tools or functionality labels May 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Digitizing Related to feature digitizing map tools or functionality
Projects
None yet
Development

No branches or pull requests

1 participant