Product reader/writer parameters
Description
Environment
None
GitHub Work
blocks
relates to
Activity
Show:
Marco Peters 23 October 2019 at 07:32
Depending on one parameter other parameters can change.
E.g. changing the binary output format for the new std. IO-Format leads to different parameters. For example, one can be compressed another not. See https://senbox.atlassian.net/browse/SNAP-1212
Norman Fomferra 26 August 2015 at 16:00
Must move @Parameter annotation from snap-gpf into snap-core
Norman Fomferra 30 January 2015 at 14:50
Set writer compression
Set writer target types (e.g. force uint16)
Set force big-tiff
The product reader/writer API in SNAP core should support parameterisation similar to what has been done for GPF operators.
In the ideal case, the @Parameter annotations from GPF would be reused. Parameters of readers and writers should be propagated to the corresponding GPF ReaderOp and WriterOp, so that these can be configured in the same way.
For readers or writers that have parameters, a configuration dialog is automatically displayed when invoked from SNAP Desktop. Users shall then have the option to supress the configuration dialog the next time and use the last entered values as default reader/writer parameter values. The preference dialog should have a dedicated page where this setting can be reverted (to show config again).