-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
qgis doesn't show any message/warning when splitting a polygon with an invalid geometry #12889
Comments
Author Name: Paolo Cavallini (@pcav) Confirmed. In my case, it crashes with: Error:
Segmentation fault |
Author Name: Giovanni Manghi (@gioman) see attached image. The geometry does not seems correct. Fix it and the tool will work fine. |
Author Name: Jürgen Fischer (@jef-n) Replying to [comment:2 pcav]:
No crash here.
GDAL? Strange. There should be a GEOS exception, if any. Although the rest of the message looks like one. Doesn't this only crash with some plugins involved? |
Author Name: Paolo Cavallini (@pcav) So we got another problem now: I suspected the layer was invalid, so I checked with fTools, which it couldn't find the error.
|
Author Name: Paolo Cavallini (@pcav) Right: uninstalling SDA4PP plugin removes the crash. A meaningful erro message would be good to have anyway. |
Author Name: xr6ute - (xr6ute -) Sorry about the bad geometry file I hadn't noticed that, and I can confirm Lutra is correct, once I fixed the geometry the tool worked as expected. |
Author Name: Giovanni Manghi (@gioman) New description: See attached polygon shapefile. It has an invalid geometry and if you try to split it qgis does nothing. It should throw a message/warning. |
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: xr6ute - (xr6ute -)
Original Redmine Issue: 2829
Redmine category:digitising
Assignee: nobody -
While editing a shape file, trying to split the feature has no affect. Trying to split the same shape file with v1.2.0 used to cause a crash.
Creating a new ring and splitting that does work as expected.
The text was updated successfully, but these errors were encountered: