-
-
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
Dissolved: Could not add feature with geometry type GeometryCollection to layer of type MultiPolygon #53360
Comments
@see7e it seems to me the issue also occur using the Dissolve processing algorithm GUI. |
@agiudiceandrea in the zip I've posted there's a log file with the processing run, comproving that is possible to run the same output by the toolbox, but you can see bellow a print. In this image you can see that
PS; I've mentioned the same report ( #47348 ) in the previous post |
@see7e probably there is a misunderstanding. From your issue report:
I understood that the issue occurs only using the Python script while it doesn't occur using the processing algorithm GUI. Form the provided log and screenshots I don't see any proof that the issue doesn't occur using the processing algorithm GUI. dissolve.mp4The same issue ( |
@agiudiceandrea okay, but some points seems odd to me.
The log shows what processings I've done in sequence
And the print shows the three temporary layers. The other point is:
All three layers have elements and geometries. Although these errors occurred in
|
@see7e the 004_FAS_1 layer contains 3 features with empty geometry (fids 47, 48, 49): you can spot them using the Field Calculator with the expression |
Oh, okay then, I'll add a validation to filter this null geom. in the next time! Thank you very much 😃 |
What is the bug or the crash?
We have this diferent shapefiles and need to Dissolve them altoghether so I'll post the snippet of the code (the comments are in pt)
Whats confuses me is when I run the same processing tools in the GUI toolbox I get the output with no errors (you can see in the
log
file)This problem seems to be related with #47348
Steps to reproduce the issue
Versions
Supported QGIS version
New profile
Additional context
I've done a good amount of tests in many different inputs, all of them presenting good outputs, but stumbled on this one..
Tried to look in #46396, but don't seems to be the same issue.
The text was updated successfully, but these errors were encountered: