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

Edit vertex tool very slow #14365

Closed
qgib opened this issue Oct 24, 2011 · 7 comments
Closed

Edit vertex tool very slow #14365

qgib opened this issue Oct 24, 2011 · 7 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 High Priority
Milestone

Comments

@qgib
Copy link
Contributor

qgib commented Oct 24, 2011

Author Name: Marica Landini bulma (Marica Landini bulma)
Original Redmine Issue: 4433
Affected QGIS version: master
Redmine category:digitising


Dear developers,
we noticed that the tool for the vertex edit since the version 1.5 is very slow.
When we try to edit features (polygons in our case) having a big number of vertices, during an editing session, just clicking with the node tool on a vertex (node) of a selected polygon we have to wait a lot of seconds (proportionally to the number of vertices) before to see the vertices selected in red square.
In the 1.4 version this operation was immediate.
After these selection of vertices the use of the tool (moving a vertex) it is also very slow.
We loaded on http://geo.regione.emilia-romagna.it/gstatico/documenti/qgis/test_node_edit_qgis.zip an example shapefile that we used for these tests.
You can try with the Ferrara Province polygon, although we tried also with others shapefiles and differents polygons.
OS: Win XP, Ubuntu 10.10
qGis versions: since 1.5, till 1.7.1 (with the 1.4 there is no problem)


Related issue(s): #14441 (duplicates)
Redmine related issue(s): 4523


@qgib
Copy link
Contributor Author

qgib commented Oct 24, 2011

Author Name: Paolo Cavallini (@pcav)


Also on Debian, and Windows 7 and Vista, apparently

@qgib
Copy link
Contributor Author

qgib commented Oct 26, 2011

Author Name: Giovanni Manghi (@gioman)


This is easily confirmed and the reason seems to be something related to the (pseudo)topological editing features. Interesting enough QGIS still very slow (basically unusable) when editing large/complex geometries even if the topological editing parameters are not enabled.


  • category_id was configured as Digitising
  • priority_id was changed from Normal to High
  • fixed_version_id was configured as Version 1.8.0

@qgib
Copy link
Contributor Author

qgib commented Dec 20, 2011

Author Name: Ben Madin (Ben Madin)


Paolo Cavallini wrote:

Also on Debian, and Windows 7 and Vista, apparently

Also on Mac OS X 10.6 using QGIS 1.7.3 (from William Kyngesbury)

@qgib
Copy link
Contributor Author

qgib commented Dec 20, 2011

Author Name: Ben Madin (Ben Madin)


Sorry, I hit submit instead of preview, but I wanted to add that "(basically unusable)" is most definitely an understatement - but to put some sense of perspective on it, it seems that at about 27000 points in the geometry you can just manage, but a bigger multipolygon (I seem to be dealing with places like the Philippines and Chile a lot at the moment!) often have hundreds of thousands of points, and the whole programme ends up using 1 GB of RAM, 100% of CPU and 10 minutes later hasn't progressed.

I can remember editing these for a project some years ago, so I was just wondering if there is any way to roll back the pseudo-topological editing features for now (they are good, but I need to get rid of some errors).

cheers

Ben

@qgib
Copy link
Contributor Author

qgib commented Jan 26, 2012

Author Name: Paolo Cavallini (@pcav)


Seems fixed now - please test on master.


  • version was configured as master
  • crashes_corrupts_data was configured as 0

@qgib
Copy link
Contributor Author

qgib commented Jan 26, 2012

Author Name: Giovanni Manghi (@gioman)


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Jan 28, 2012

Author Name: Giovanni Manghi (@gioman)


This is issue is (thanks to Jurgen work) gone, and actually the performances when editing geometries with a lot of nodes (tens of thousands nodes) is now even more efficient of any other GIS software I had testes, both OS and proprietary.


  • resolution was changed from to fixed
  • status_id was changed from Feedback to Closed

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! High Priority Digitizing Related to feature digitizing map tools or functionality labels May 24, 2019
@qgib qgib added this to the Version 1.8.0 milestone May 24, 2019
@qgib qgib closed this as completed 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 High Priority
Projects
None yet
Development

No branches or pull requests

1 participant