+1
I am not certain what transformer can change my NaN values to NoData values (or any other values)?
I read through this article: http://blog.safe.com/2013/11/fmeevangelist119/
and thought the NullAttributeMapper would be the answer, but it does not seem so.
+19Hi,
Have you tried setting a preferable Nodata value to the "Output DEM Raster Nodata Value" parameter of the SurfaceModeller?
Takashi
+17+1
Itay - I think you are getting at the NoData value? My understanding of NaN is that is is not a number so it would not be 9999 or 0.
To simply my question: given that you have a 32 bit raster that has normal double values, has a NoData value set as -32767.0, and also has NaN values, what is the simplest way to make the NaN values into NoData values?
I have managed to do this but I'm not sure how efficient the process would be with larger datasets:
I first convert the raster to points, then do a AttributeClassifier (passing only points that are "double") and then using NumericRasterizer to arrive back at a raster. This does the trick but is there a more efficient method?
+1+19It seems that "nan" is treated internally as a numeric value smaller than any valid value when comparing values.
Try the RasterCellValueReplacer with this setting:
Replace Values <=: -32767
New Value: -32767
+19It seems that "nan" is treated internally as a numeric value smaller than any valid value when comparing values.
Try the RasterCellValueReplacer with this setting:
Replace Values <=: -32767
New Value: -32767
An application. This workflow removes every "nan" point from the source point cloud feature.
+4By me works well with raster with NaN nan or -nan Nodata value:
PointCloudCombiner with options: Extract NoData = No
NumericRasterizer, set Cell Spacing and extent with the value extracted with RasterPropertyExtractor. Set your nodata value, example -9999
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
