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] fix intersection and union tools #5099

Closed
wants to merge 2 commits into from
Closed

[processing] fix intersection and union tools #5099

wants to merge 2 commits into from

Conversation

alexbruy
Copy link
Contributor

@alexbruy alexbruy commented Aug 31, 2017

Description

This is backport of master fixes to 2.18 branch

Checklist

Reviewing is a process done by project maintainers, mostly on a volunteer basis. We try to keep the overhead as small as possible and appreciate if you help us to do so by completing the following items. Feel free to ask in a comment if you have troubles with any of them.

  • Commit messages are descriptive and explain the rationale for changes
  • Commits which fix bugs include fixes #11111 in the commit message next to the description
  • Commits which add new features are tagged with [FEATURE] in the commit message
  • Commits which change the UI or existing user workflows are tagged with [needs-docs] in the commit message and containt sufficient information in the commit message to be documented
  • I have read the QGIS Coding Standards and this PR complies with them
  • This PR passes all existing unit tests (test results will be reported by travis-ci after opening this PR)
  • New unit tests have been added for core changes
  • I have run the scripts/prepare-commit.sh script before each commit

@alexbruy
Copy link
Contributor Author

@gioman can you test these fixes?

@alexbruy
Copy link
Contributor Author

Travis failure on master expected and not related, as this PR targeted to 2.18 branch

@nyalldawson
Copy link
Collaborator

Travis failure on master expected and not related, as this PR targeted to 2.18 branch

It's not failing on master, it's failing on the 2.18 build under qt5. So it must be something related to these changes.

@nyalldawson
Copy link
Collaborator

It's not failing on master, it's failing on the 2.18 build under qt5. So it must be something related to these changes.

Actually it IS an unrelated test failure ;)

@gioman
Copy link
Contributor

gioman commented Sep 5, 2017

@gioman can you test these fixes?

will do asap!

@gioman
Copy link
Contributor

gioman commented Sep 13, 2017

@Gustry
Copy link
Contributor

Gustry commented Sep 13, 2017

See https://issues.qgis.org/issues/14846 too
@wonder-sk was fixing this ticket in the 2.18 branch too (AFAIK)

@gioman
Copy link
Contributor

gioman commented Sep 14, 2017

@Gustry I added a new comment https://issues.qgis.org/issues/17131#note-2 that is about the dataset provided by the issuer of https://issues.qgis.org/issues/14846 and upatched processing in 2.18.12

Master and the patched processing for 2.18.12 that included backports from master gives results that are worst than the unpatched processing in 2.18.12. In this case with very simple datasets the results are sometimes correct, in other cases are still wrong but "look" better than on master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants