nan()function in Band Math expressions, but since NetCDF4-CF is used by current OCSSW processing tools it is worth mentioning NetCDF best practices for handling "missing data values".
(nan)function, but the NaN values weren't replaced and the values different of NaN became 0....so the NaN didn't become a number...
Any ideia why does this happens? I'm really stuck at this...
At Math Band I'm using .L3m images and the following expression: "
if turb==NaN then 9999 else turb".
Any ideia from that, sir George?
And about this unsigned integers, how could I translate to this format-specific "missing data" value? And I don't really know if my image is stored as unsigned integers; how can I verify that?
Thank you very much for your time and help sir!
A good way to get an overview of the contents of a geoTIFF or NetCDF4-CF file is with GDAL's
gdalinfo. Note that NetCDF4-CF files often contain multiple bands, so you use "
gdalinfo <filename>" once to find the band you want, then "
SeaDAS provides the
nanfunction because NaN is defined in way that tests of the form you tried: "
if turb==NaN then 9999 else turb" don't work and have to written as "
if nan(turb) then 9999 else turb", or using a Ternary Conditional Operator "
nan(turb) ? 9999 : turb". Rather than trying set a special value in Band Math, use the
Property Editor to set a "Valid Pixel Expression".
About using the ArcGIS, I'm really more used to work with geoTIFF files on that, but considering those advantages on NetCDF4-CF I'll check it out.
Thank you for your help sir. Have a very nice day!