-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Tolerance (snapping) during analyses #17933
Comments
Author Name: Paolo Cavallini (@pcav) See a discussion on: http://lists.osgeo.org/pipermail/qgis-developer/2014-January/030119.html |
Author Name: Paolo Cavallini (@pcav) Probably this could be solved with a new command, allowing the user to arbitrarily reduce the precision of coordinates (filling up the rest with 0s). |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Paolo Cavallini (@pcav) Still valid? With automatic reprojection now in Processing the issue can be even more serious.
I suggest to add a parameter in analyses, to either snap original data within a threshold before running the analysis, or to clean up the results afterwards to In case of layers with essentially the same shapes, with different precision, the diff between these layers produces a number of virtually 0 width polygons. I suggest to add a parameter in analyses, to either snap original data within a threshold before running the analysis, or to clean up the results afterwards |
Probably we can close this, as Processing now offers several tool for snapping which can be used before doing analysis. |
Agreed, thanks |
Author Name: Paolo Cavallini (@pcav)
Original Redmine Issue: 9326
Redmine category:processing/qgis
In case of layers with essentially the same shapes, with different precision, the diff between these layers produces a number of virtually 0 width polygons.
These microareas are tricky and time consuming to remove (if they are isolated, a possible solution is to select and remove those smaller than an arbitrary threshold, but if they are linked to some "real" polygons, this will not work).
I suggest to add a parameter in analyses, to either snap original data within a threshold before running the analysis, or to clean up the results afterwards
The text was updated successfully, but these errors were encountered: