Custom Query (124 matches)


Show under each result:

Results (76 - 78 of 124)

Ticket Resolution Summary Owner Reporter
#55 fixed specify that CF uses UDUNITS-2 cf-conventions@… jonathan

Unidata has released a new version of the udunits package, which fixes some problems in the original version. Although the units supported are very largely the same, CF should specify which version is the reference standard, since there are a few differences. Unidata deprecates the original version. Therefore version 2 should be the CF reference. This ticket proposes to clarify and update the CF standard by

  • Replacing all references to UDUNITS with UDUNITS-2.
  • Replacing all references to udunits.dat with references to the appropriate xml file of UDUNITS-2.

I'm submitting this as a defect, because I don't think it materially affects the CF standard.

Jonathan Gregory

#54 fixed CF Checker crash in chkAttribute ros ros
Checking variable: longitude
Traceback (most recent call last):
  File "/home/ros/bin/", line 2194, in 
  File "/home/ros/bin/", line 349, in checker
    if not self.chkAttribute(attribute,var,allCoordVars): rc=0
  File "/home/ros/bin/", line 1019, in chkAttribute
    if var.dtype.char != var.attributes[attribute].dtype.char:
AttributeError: 'function' object has no attribute 'char'
#52 fixed Clarification of _FillValue attribute cf-conventions@… ros

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.


Note: See TracQuery for help on using queries.