QGIS » QGIS Application

I'd be inclined to close this as a "won't-fix". The command line is shown only as a shortcut for people developing batch files and for execution outside of QGIS. There's no real way to fit an editable command into the processing world.

Alternative options would be:

1. A separate plugin allowing execution of gdal command line tools via a toolbar button. Users could then copy commands from processing windows and paste and edit using that plugin.

Or

2. A new gdal algorithm with a single "command" parameter, allowing for pasting of a gdal command to execute.

I understand well your point. Same thing applies to other backends (grass, saga).
However, good old GDALTools made this straightforward, and power users took advantage of this function extensively. I think that missing it is a regression, not a very good thing.
Perhaps a more general solution should be designed, i.e. the capability of re-running analyses editing the command string by hand.

Nyall Dawson wrote:

I'd be inclined to close this as a "won't-fix". The command line is shown only as a shortcut for people developing batch files and for execution outside of QGIS. There's no real way to fit an editable command into the processing world.

Alternative options would be:

1. A separate plugin allowing execution of gdal command line tools via a toolbar button. Users could then copy commands from processing windows and paste and edit using that plugin.

Or

2. A new gdal algorithm with a single "command" parameter, allowing for pasting of a gdal command to execute.

Hi,

I can't figure out how to add a comment without modifying the comment. Perhaps the "cite" button is the only way... anyways, I agree with Paolo that this is a major setback as the old tool really permitted users to learn the gdal command lines. It also gave flexibility. I agree that a "other command" parameter would be one way to go. Still, it would be important to see the list of files being used (in the case of gdalbuiltvrt). Currently all we see is that the file list will be created in (buildvrtInputFiles.txt). This is important as the order of the files is important in this module. Sorry if I messed up your comment. I will only see if I did this correctly after I press the "send" button!

Nicolas

I'd like to support this feature request turning the output command text field of the dialog into an editable text field (referring to #21978).

My test case and goal is to call e.g. "gdal_grid" as follows:

gdal_grid -a nearest:radius1=1:radius2=1:nodata=-99 \
-txe 50 350 -tye 650 450 -outsize 3 2 -zfield z \
"grid in.gpkg" "grid out.tif" 

The parameters "-txe 50 350 -tye 650 450 -outsize 3 2" are currently unreachable through the processing dialog (i.e. they are not layer output creation options). Think also about the -sql option.