Regressions in processing "Tile Index" tool #29114
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
Author Name: Alister Hood (@AlisterH)
Original Redmine Issue: 21296
Affected QGIS version: 3.4.4
Redmine category:processing/gdal
Assignee: Nyall Dawson
Issue 1:
The processing "Tile Index" tool in QGIS 3.x is equivalent to the one in 2.x. However, "Raster>Miscellaneous>Tile Index..." now uses the processing tool, whereas in 2.x series it was a separate implementation, which must have somehow run the gdaltindex command in a different way, because it could handle more files.
I have 151 rasters here with 88 character long paths.
In both 2.x and 3.x the processing tool produces the error "The command line is too long."
But the tool in the 2.x menu runs perfectly, even though the command it displays is significantly longer (for two reasons - it tries to use the .aux.xml files in the input directory, as well as the tif files, and it also uses \ in each path for all except the last directory separator, rather than /). So, whatever method that tool was using to run the command, it was superior (also note that the whole point of this tool is that you have a LOT of rasters - I don't think 151 is an unreasonably high number).
This could be considered a regression, because the old gdaltools tool which supported more input files has been superseded by the processing tool.
This testing is under Windows, and I doubt this issue would occur on a real operating system.
Issue 2:
If I only select a small number of rasters, the processing tool succeeds in 2.x, but not in 3.x. This is because the path to each raster includes a space, and 3.x is not separately quoting the path to each raster, it is putting one set of quotes around the entire list of input files.
These are the error messages (I have replaced the list of paths, obviously):
This problem is a regression by any definition, and I'm guessing it is not specific to Windows, but I haven't checked.
The text was updated successfully, but these errors were encountered: