Skip to main content
  • EN

I'm doing a relatively simple task using a RasterCellValueReplacer, im filtering a few rasters by a defined filter parameter.

However, if the filter value is typed into the transformer it works fine, if i try and pass the filter value by either user parameter or attribute the result is completely different and incorrect.

What's a bit more of a concern, when i use an attribute or a parameter, the process seems to be making its own filter value out of thin air, the raster passes through as if filtered randomly

 

 

 

Hi ​@afod ,

In my quick test to check how RasterCellValueReplacer works with FME 2024.2.3 and FME 2025.1.1, the issue you have described didn't occur.

Can you share a workspace example and a sample data which reproduce the issue?

We are still on 2023.0 which may be part of the issue

Attached a sample area, with workspace and resulting Tiffs from each process type

Thank you for sharing the workspace example and the sample dataset. I was able to the issur with FME 2023.2, 2024.2, and 2025.1. It seems to be a bug in some condition, but I couldn’t specify the exact cause.

I would recommend you to submit a support request to Safe.

Interestingy, I found that the issue won’t appear if you assing the user parameter value to a feature attribute with ParameterFetcher - not with AttributeManager and set the attribute to the filter parameter in RasterCellValueReplacer. This might be a workaround in the interim.

Hope this helps.

Community Stats

31,835
Posts
120,911
Replies
39,470
Members

Latest FME

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.