The RasterBandInterpretationCoercer allows only for hardcoded choice or user parameter for all of its parameters like Destination Interpretation Type, and Conversion Options.
It would be nice if these value could be set by an attribute on the Raster. The Conversion options could also be simplified to Convert from Color, Convert from Numeric, Convert from Float to Integer, as the "to" interpretation is redundant when supplying the Destination Interpretation Type.
Any features with invalid combinations (like palettes restricted to UINT) could be output the Rejected port.
Archived
RasterBandInterpretationCoercer should support attributes for parameters
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.

