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

Split features tool behaves unpredictably when split line is snapped on a segment #29270

Closed
qgib opened this issue Mar 3, 2019 · 3 comments · Fixed by #56811
Closed

Split features tool behaves unpredictably when split line is snapped on a segment #29270

qgib opened this issue Mar 3, 2019 · 3 comments · Fixed by #56811
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 Mar 3, 2019

Author Name: Antoine Lafranchis (@alafr)
Original Redmine Issue: 21453
Affected QGIS version: 3.7(master)
Redmine category:digitising


The split features tool sometimes splits and sometimes doesn't split the feature, when the split line's last vertex is snapped exactly on a segment it. I attach a screencast to illustrate the issue because it's not totally reproductible. The issue is the same whether the feature is selected or not. It happens both with polygons and linestring geometries. It's probably due to small floating-point calculation inaccuracies.
In the examples shown in the screencasts, the CRS of the project and the layers (temporary memory layers) was the same (EPSG:3945).


@qgib
Copy link
Contributor Author

qgib commented Mar 3, 2019

Author Name: Giovanni Manghi (@gioman)


  • category_id was changed from Map Tools to Digitising

@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 25, 2019
@Pedro-Murteira
Copy link

I can still replicate this issue on QGIS 3.16.14 and 3.22.1.

@MTrim
Copy link

MTrim commented Feb 6, 2024

In a project, I encountered this bug. It seems it hasn't been resolved yet. Is there a workaround or an approach to this? I also have resources to sponsor a fix.

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

Successfully merging a pull request may close this issue.

3 participants