Question

FME - why is tif writer is setting 0's in any band to NODATA?[ e.g. (0,16,0)>>(NODATA, 16, NODATA) ]

  • 20 April 2014
  • 3 replies
  • 1 view

Badge
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). 

 

 

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...

 

 

 


3 replies

Userlevel 2
Badge +17
Hi, the RasterCellValueReplacer transformer might help you.

 

Takashi
Badge +3
Hi,

 

 

 

Appearently 0 is nodata in your set.

 

RasterBandNodataSetter or replacer might be usefull.

 

 

Badge
After looking over all the options, the easiest options seems to be using RasterExpressionEvaluator.

Reply