Skip to main content
  • Home
  • Forums
  • FME Form
  • Data
  • FME - why is tif writer is setting 0's in any band to NODATA?[ e.g. (0,16,0)>>(NODATA, 16, NODATA) ]
Question

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

makt
Contributor
Forum|alt.badge.img+1
  • maktContributor
  • 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). 

 

 

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

takashi
Contributor
Forum|alt.badge.img+19
  • takashiContributor
  • Contributor
  • April 20, 2014
Hi, the RasterCellValueReplacer transformer might help you.

 

Takashi
gio
Contributor
Forum|alt.badge.img+15
  • gioContributor
  • Contributor
  • April 22, 2014
Hi,

 

 

 

Appearently 0 is nodata in your set.

 

RasterBandNodataSetter or replacer might be usefull.

 

 

makt
Contributor
Forum|alt.badge.img+1
  • maktContributor
  • Author
  • Contributor
  • April 25, 2014
After looking over all the options, the easiest options seems to be using RasterExpressionEvaluator.

Reply


Helpful Members This Week

Community Stats

30,921
Posts
117,189
Replies
38,725
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.