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

Warning before running analyses on too large rasters #17058

Closed
qgib opened this issue Jul 10, 2013 · 7 comments
Closed

Warning before running analyses on too large rasters #17058

qgib opened this issue Jul 10, 2013 · 7 comments
Labels
Feature Request Feedback Waiting on the submitter for answers Processing Relating to QGIS Processing framework or individual Processing algorithms

Comments

@qgib
Copy link
Contributor

qgib commented Jul 10, 2013

Author Name: Paolo Cavallini (@pcav)
Original Redmine Issue: 8249

Redmine category:processing/core


If the user does not select an appropriate resolution for the resulting raster(s), it risks to get stuck with an excessive resolution, and too long processing time. I suggest to do a simple calculation of the resulting number of pixel before running analyses, and warn the user if this is too high.


Related issue(s): #16342 (relates)
Redmine related issue(s): 7369


@qgib
Copy link
Contributor Author

qgib commented Oct 4, 2014

Author Name: Giovanni Manghi (@gioman)


  • project_id was changed from 78 to 17
  • category_id removed 63

@qgib
Copy link
Contributor Author

qgib commented Oct 4, 2014

Author Name: Giovanni Manghi (@gioman)


  • category_id was configured as Processing/Core

@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 Feb 24, 2018

Author Name: Paolo Cavallini (@pcav)


  • assigned_to_id removed Victor Olaya

@qgib
Copy link
Contributor Author

qgib commented Feb 13, 2019

Author Name: Nyall Dawson (@nyalldawson)


I think this request could be satisfied by instead allowing cancellation of gdal algorithms. The native QGIS algorithms all have nice progress reports and support responsive cancellation already.


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Feb 13, 2019

Author Name: Paolo Cavallini (@pcav)


Agreed, thanks.

@qgib qgib added Feedback Waiting on the submitter for answers Feature Request Processing Relating to QGIS Processing framework or individual Processing algorithms labels May 24, 2019
@AlisterH
Copy link
Contributor

AlisterH commented Jun 8, 2021

#27882 is implemented, so this could probably be closed.

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

No branches or pull requests

3 participants