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

SAGA "slope, aspect, curvature" return wrong output #24394

Closed
qgib opened this issue Apr 29, 2017 · 5 comments
Closed

SAGA "slope, aspect, curvature" return wrong output #24394

qgib opened this issue Apr 29, 2017 · 5 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! High Priority Processing Relating to QGIS Processing framework or individual Processing algorithms Regression Something which used to work, but doesn't anymore
Milestone

Comments

@qgib
Copy link
Contributor

qgib commented Apr 29, 2017

Author Name: Giovanni Manghi (@gioman)
Original Redmine Issue: 16486
Affected QGIS version: 2.18.7
Redmine category:processing/saga
Assignee: Victor Olaya


Tagging this as a regression because I don't remember being an issue in the past, but not sure 100% now.

Tested on macOS, Windows and Linux, on 2.14.8, 2.14.14/2.18.7 and 2.18.7 with different SAGA versions.

Take the attached dataset and use as input for the "slope, aspect, curvature" alg. Leave output fields empty. Run the the tool, point layers are returned instead of raster layers. If an output is manually defined then after running the right results is returned (but with the attached dataset it seems that the output is not given the right CRS, the one of the input).

This does not happen with other sample inputs of the same type (but other CRSs).


@qgib
Copy link
Contributor Author

qgib commented Apr 30, 2017

Author Name: Giovanni Manghi (@gioman)


  • regression was configured as 1

@qgib
Copy link
Contributor Author

qgib commented Apr 30, 2017

Author Name: Giovanni Manghi (@gioman)


  • priority_id was changed from Severe/Regression to High

@qgib
Copy link
Contributor Author

qgib commented Apr 30, 2017

Author Name: Giovanni Manghi (@gioman)


  • easy_fix was configured as 0

@qgib
Copy link
Contributor Author

qgib commented May 12, 2017

Author Name: Alexander Bruy (@alexbruy)


Applied in changeset 3d3b6ec.


  • status_id was changed from Open to Closed
  • done_ratio was changed from 0 to 100

@qgib qgib closed this as completed May 12, 2017
@qgib
Copy link
Contributor Author

qgib commented May 12, 2017

Author Name: Giovanni Manghi (@gioman)


  • resolution was changed from to fixed/implemented
  • description was changed from Tagging this as a regression because I don't remember being an issue in the past, but not sure 100% now.

Tested on macOS, Windows and Linux, on 2.14.8, 2.14.14/2.18.7 and 2.18.7 with different SAGA versions.

Take the attached dataset and use as input for the "slope, aspect, curvature" alg. Leave output fields empty. Run the the tool, point layers are returned instead of raster layers. If an output is manually defined then after running the right results is returned (but with the attached dataset it seems that the output is not given the right CRS, the one of the input).

This does not happen with other sample inputs of the same type (but other CRSs). to Tagging this as a regression because I don't remember being an issue in the past, but not sure 100% now.

Tested on macOS, Windows and Linux, on 2.14.8, 2.14.14/2.18.7 and 2.18.7 with different SAGA versions.

Take the attached dataset and use as input for the "slope, aspect, curvature" alg. Leave output fields empty. Run the the tool, point layers are returned instead of raster layers. If an output is manually defined then after running the right results is returned (but with the attached dataset it seems that the output is not given the right CRS, the one of the input).

This does not happen with other sample inputs of the same type (but other CRSs).

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! High Priority Processing Relating to QGIS Processing framework or individual Processing algorithms Regression Something which used to work, but doesn't anymore labels May 25, 2019
@qgib qgib added this to the Version 2.18 milestone May 25, 2019
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! High Priority Processing Relating to QGIS Processing framework or individual Processing algorithms Regression Something which used to work, but doesn't anymore
Projects
None yet
Development

No branches or pull requests

1 participant