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

[Processing] Mention layer name when algorithm fails due to invalid geometry #26664

Closed
qgib opened this issue Apr 20, 2018 · 0 comments · Fixed by #39378
Closed

[Processing] Mention layer name when algorithm fails due to invalid geometry #26664

qgib opened this issue Apr 20, 2018 · 0 comments · Fixed by #39378
Labels
Feature Request Processing Relating to QGIS Processing framework or individual Processing algorithms

Comments

@qgib
Copy link
Contributor

qgib commented Apr 20, 2018

Author Name: Harrissou Santanna (@DelazJ)
Original Redmine Issue: 18777

Redmine category:processing/gui


I'm doing some spatial join and it fails due to invalid geometry. In the Log panel, the message is

Feature (36802) has invalid geometry. Please fix the geometry or change the Processing setting to the "Ignore invalid input features" option.
Execution failed after 2.83 seconds

It could be nice to also indicate from which layer the broken feature comes.

@qgib qgib added Feature Request Processing Relating to QGIS Processing framework or individual Processing algorithms labels May 25, 2019
nyalldawson added a commit to nyalldawson/QGIS that referenced this issue Oct 15, 2020
the layer name so that it's clear which of the corresponding inputs
the warning/error relates to

Fixes qgis#26664
nyalldawson added a commit that referenced this issue Oct 15, 2020
the layer name so that it's clear which of the corresponding inputs
the warning/error relates to

Fixes #26664
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request Processing Relating to QGIS Processing framework or individual Processing algorithms
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant