Feature request #14856

Processing: Use r.external.out for GRASS raster algorithms

Added by Stefan Blumentrath 10 months ago. Updated 9 months ago.

Status:Open Start Date:05/22/2016
Priority:Normal Due date:
Assigned to:Victor Olaya % Done:

0%

Category:Processing/GRASS
Target version:Version 2.16
Platform: Resolution:
Platform version: Pull Request or Patch supplied:No
Status info: Tag:

Description

In processing, GRASS raster algorithms should use r.external.out instead of r.out.gdal.
With r.external.out, results are stored directly as non-GRASS, GDAL-supported formats. This will save a significant amount of processing time as the export step is saved.
Files will be stored in a sub-folder of the current (temporary) mapset. Thus, after completition, results have to be moved to the user-defined location. Therefore, speed improvements are less big, when the user-defined output and the temporary GRASS location are not on the same volume.
Necessary changes would be along the lines of the attached Grass7Algorithm.py.
The attached Grass7Algorithm.py works at least for r.aspect, except for the "mv", which has trouble with the path delimiters / drive letter on windows.
Please note, that GeoTiff is hard-coded as output format, while r.external.out supports all gdal writable formats.

Grass7Algorithm.py (25.1 kB) Stefan Blumentrath, 05/22/2016 02:49 am

History

Also available in: Atom