Using the RasterBandNoDataRemover does fix the problem, but also changes the NODATA cells that I want to be NODATA into balck (0,0,0).
How can I fix this? Seems to me that this should not be a default behavior...
Question
FME - why is tif writer is setting 0's in any band to NODATA?[ e.g. (0,16,0)>>(NODATA, 16, NODATA) ]
+1- Contributor
I'm reading a geotiff and am unsure why when I'm writing to a new geotif, all my dark dark green cells, such as RGB (0,16,0), get rewritten to (NODATA, 16, NODATA).
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.
+15- Contributor
Hi,
Appearently 0 is nodata in your set.
RasterBandNodataSetter or replacer might be usefull.
+1- Contributor
After looking over all the options, the easiest options seems to be using RasterExpressionEvaluator.