NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
I was wondering what the NaNf meant :-) But yeah, that's probably it -- now to track down whoever wrote this file -- But I do wonder what software allowed this? -CHB On Wed, Oct 2, 2024 at 12:53 PM Benjamin Root <ben.v.root@xxxxxxxxx> wrote: > I think the issue is that the _FillValue of "NaN" is probably a float64 > while the variable's dtype is float32, which is probably what it means by a > type mismatch. When I have a NaN FillValue for a float32 variable, it > prints "NaNf" > > ``` > float sum_tp_mm(time, latitude, longitude) ; > sum_tp_mm:_FillValue = NaNf ; > ``` > -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker@xxxxxxxx
netcdfgroup
archives: