Processing: add option for output type (uint8, unit16,..., float, double) in OTB tools

[qgib]

Author Name: Giovanni Manghi (@gioman)
Original Redmine Issue: 11032

Redmine category:processing/core
Assignee: Victor Olaya

---

in OTB tools is possible in (all?) tools to define the bit depth of output, example

-out [pixel] Output Image [pixel=uint8/uint16/int16/uint32/int32/float/double] (default value is float) (mandatory)

by default is "float" that many times is not the best option. As in Processing is not possible to change this default then further manipulation of outputs is often needed.

The problem is that this [pixel] definition is not added to the OTB command as any other parameter: it must be added just after the "-out" parameter without any "-" in front of it, exemple:

otbcli_KMeansClassification -in input.tif -out output.tif uint8

this means that this parameter cannot be added in OTB tools definitions files because they will be added to the command line with the "-" causing an error for unrecognized parameter.

I guess that this means that OTBAlgorithm.py must be patched to cope with the "non" parameter.

[qgib]

Author Name: Alexander Bruy (@alexbruy)

---

• category_id was changed from 94 to 120

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

• easy_fix was configured as 0

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

A few providers are being removed from QGIS3 (they will be available as plugins), so the respective categories are also being removed from the bug tracker. Where necessary the tickets will be reassigned to "processing/core" to not leave them orphaned of category.

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

Some providers are being removed from QGIS/Processing (will be available as plugin) and so are their categories in the bug tracker. To not leave them orphaned of a category they are being reassigned to processing/core.

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

• category_id was changed from 120 to Processing/Core

[qgib]

Author Name: Alexander Bruy (@alexbruy)

---

Moved to plugin bugtracker orfeotoolbox/qgis-otb-plugin#5

---

• resolution was changed from to up/downstream
• description was changed from in OTB tools is possible in (all?) tools to define the bit depth of output, example

-out [pixel] Output Image [pixel=uint8/uint16/int16/uint32/int32/float/double] (default value is float) (mandatory)

by default is "float" that many times is not the best option. As in Processing is not possible to change this default then further manipulation of outputs is often needed.

The problem is that this [pixel] definition is not added to the OTB command as any other parameter: it must be added just after the "-out" parameter without any "-" in front of it, exemple:

otbcli_KMeansClassification -in input.tif -out output.tif uint8

this means that this parameter cannot be added in OTB tools definitions files because they will be added to the command line with the "-" causing an error for unrecognized parameter.

I guess that this means that OTBAlgorithm.py must be patched to cope with the "non" parameter. to in OTB tools is possible in (all?) tools to define the bit depth of output, example

-out [pixel] Output Image [pixel=uint8/uint16/int16/uint32/int32/float/double] (default value is float) (mandatory)

by default is "float" that many times is not the best option. As in Processing is not possible to change this default then further manipulation of outputs is often needed.

The problem is that this [pixel] definition is not added to the OTB command as any other parameter: it must be added just after the "-out" parameter without any "-" in front of it, exemple:

otbcli_KMeansClassification -in input.tif -out output.tif uint8

this means that this parameter cannot be added in OTB tools definitions files because they will be added to the command line with the "-" causing an error for unrecognized parameter.

I guess that this means that OTBAlgorithm.py must be patched to cope with the "non" parameter.

• status_id was changed from Open to Rejected