Skip to main content
  • EN

Hello,

I have a lot of rasters to clip with a single polygon shapefile. As always, I use the 'clipper' function in FME in a simple workspace. But I am unable to clip the data, FME gives me the following error message:

MaskCombiner(RasterEvaluationFactory): Failed to parse the EXPRESSION_LIST clause. The provided value was 'if(B[0]==255,A[0],nan);if(B[0]==255,A[1],nan);if(B[0]==255,A[2],nan);if(B[0]==255,A[3],nan)'. Please ensure that your syntax is correct

I am guessing that something is wrong with the nodata value in my tiff files? How do I fix this issue in FME?

Thanks!

Interesting, did you try to use RasterBandNoDataSetter before clipping

Are there some transformers that manipulate raster features, other than the Clipper? If you posted the workspace or its screenshot, it could help us to find the issue.

 

 

Are there some transformers that manipulate raster features, other than the Clipper? If you posted the workspace or its screenshot, it could help us to find the issue.

 

 

@takashi: No, the workspace is as easy as it gets: read in the multiband geotiff, clip using an ESRI shapefile (with one polygon), and write as a multiband geotiff in a different folder. There are no other operations. Both datasets have the same projection, too, and can be opened in QGIS with no problems.

 

 

@takashi: No, the workspace is as easy as it gets: read in the multiband geotiff, clip using an ESRI shapefile (with one polygon), and write as a multiband geotiff in a different folder. There are no other operations. Both datasets have the same projection, too, and can be opened in QGIS with no problems.

 

 

can you maybe provide data sample?

As @zzupljanin, mentioned, you can try adding a transformer before clipping. Another option would be the RasterBandNoDataRemover or the RasterInterpretationCoercer. If you can attach your workspace and sample data, I can try this out.

Looks like this is a known issue (PR#77325). Where the nodata is set to NaN (Not a Number) then there is a problem. As others have suggested, using a RasterBandNoDataSetter to change the Nodata value to an actual number is a good workaround.

If you need to follow up on this, contact our support team and let them know it is related to PR#77325

As @zzupljanin, mentioned, you can try adding a transformer before clipping. Another option would be the RasterBandNoDataRemover or the RasterInterpretationCoercer. If you can attach your workspace and sample data, I can try this out.

Using RasterBandNoDataRemover solved my problem, thanks @courtney_m!

 

Looks like this is a known issue (PR#77325). Where the nodata is set to NaN (Not a Number) then there is a problem. As others have suggested, using a RasterBandNoDataSetter to change the Nodata value to an actual number is a good workaround.

If you need to follow up on this, contact our support team and let them know it is related to PR#77325

fyi It's been fixed in FME2018 (beta build 18170 or greater)

 

The issue with the Clipper that was causing this problem has been fixed in FME 2018, which can be downloaded from www.safe.com/download.

Reply


Community Stats

30,190
Posts
114,589
Replies
37,854
Members
Terms & ConditionsCookie 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.