[GRASS-user] Keeping GRASS/OTB/... algorithm in qgis processing

Moritz Lennert mlennert at club.worldonline.be
Mon Feb 5 05:49:37 PST 2018

On 05/02/18 13:51, Helmut Kudrnovsky wrote:
> Von: "Moritz Lennert"
>> I don't know how difficult it would be to create such algorithm
>> descriptions automagically.
>   https://github.com/qgis/QGIS/search?p=1&q=processing+grass&type=&utf8=%E2%9C%93
> AFAIU there are some general python scripts to provide it in processing:
> e.g.
> python/plugins/processing/algs/grass7/Grass7AlgorithmProvider.py

No, this is the provider itself, not a tool to create the descriptions.

> and there are a lot of txt files providing the module interface
> e.g
> python/plugins/processing/algs/grass7/description/r.out.png.txt
> r.out.png
> Export a GRASS raster map as a non-georeferenced PNG image
> Raster (r.*)
> QgsProcessingParameterRasterLayer|input|Input raster|None|False
> QgsProcessingParameterNumber|compression|Compression level of PNG file (0 = none, 1 = fastest, 9 = best)|QgsProcessingParameterNumber.Integer|6|True|0|9
> and other files

My question was whether it would be possible to create these description 
files more or less automagically.

I think the python scripts for more complex operations have to be 
created manually.

IIUC (from rapid reading of the threads on the qgis-developer list), 
Rashad's suggestion was to keep the *AlgorithmProvider code in the QGIS 
code base, but to possibly move the creation of the description and 
script files to a plugin managed outside QGIS core, possibly by the 
respective external software teams.


More information about the grass-user mailing list