Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add option for output type (uint8, unit16,..., float, double) #5

Open
alexbruy opened this issue May 3, 2017 · 0 comments
Open

Add option for output type (uint8, unit16,..., float, double) #5

alexbruy opened this issue May 3, 2017 · 0 comments

Comments

@alexbruy
Copy link

alexbruy commented May 3, 2017

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

-out <string> [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.

Moved from QGIS bugtracker https://issues.qgis.org/issues/11032

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant