Custom Query (124 matches)

Section 2.5.1 of the convention defines the standard for the _FillValue attribute stating that it is "a scalar attribute and must have the same type as its variable." There are no specific exclusions, but I think that allowing the value NaN isn't a good idea.

The NetCDF standard doesn't prohibit the use of NaN as a _FillValue, but I did find several recommendations not to use NaN. The problem with allowing NaN is that any calculation or comparisons with NaN will return false.

I suggest a modification to the convention to recommend against the use of NaN as a _FillValue value.

Thoughts?

------------------
Checking variable: longitude
------------------
Traceback (most recent call last):
  File "/home/ros/bin/cfchecks_2-0-0.py", line 2194, in 
    inst.checker(file)
  File "/home/ros/bin/cfchecks_2-0-0.py", line 349, in checker
    if not self.chkAttribute(attribute,var,allCoordVars): rc=0
  File "/home/ros/bin/cfchecks_2-0-0.py", line 1019, in chkAttribute
    if var.dtype.char != var.attributes[attribute].dtype.char:
AttributeError: 'function' object has no attribute 'char'

Holding ticket to detail changes/fixes made to the CF Checker for version 2.0.1