Custom Query (124 matches)
Results (10 - 12 of 124)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#13 | fixed | Procedure for correcting errors in the CF documents | cf-conventions@… | jonathan |
Description |
Rich Signell has pointed out an error in the CF standard document by raising a trac ticket. I think we need rules for deciding to make corrections, or there's a danger they might not be implemented. I propose the following:
It feels a bit bureaucratic to have rules, but I think it may be necessary because experience shows that without rules we find it hard to reach conclusions. Please post your comments to this ticket. Jonathan |
|||
#14 | wontfix | Allow time coordinates to be stored as a W3C / ISO 8601formatted String | cf-conventions@… | caron |
Description |
Currently time coordinates must be stored as a number with units that are parsable by the udunits library (cf section 4.4). I propose that we also allow time coordinates to be expressed as W3C/ISO 8601 formatted Strings. (Example: 2007-03-29T12:00:00Z) This format is widely used internationally, it is a profile by the W3C of the ISO standard. This page has a summary of the format and more links: http://www.unidata.ucar.edu/projects/THREDDS/tech/interfaceSpec/NetcdfSubsetService.html#Reference Reasons:
Proposed change:
Note: I find it clearer to use "date" to refer to "calendar date", and "time" to mean a "unit of time duration" (eg 1500 secs). It might be worth looking through our usage to see where this meaning may be unclear. |
|||
#15 | fixed | Correct Appendix A for flag_values attribute | cf-conventions@… | jonathan |
Description |
This is a proposed correction for an error in the documents, not a change to the standard. According to the rules, it will be accepted if no-one objects to it in the next three weeks. The table in Appendix A incorrectly states that flag_values is a string attribute. This is inconsistent with CF 3.5, which says, "The flag_values attribute is the same type as the variable to which it is attached." This error was pointed out by John Stark in April 2007 http://www.cgd.ucar.edu/pipermail/cf-metadata/2007/001614.html and this month by Philippe Poilbarbe on the netCDF email list. The correction required is as follows:
Jonathan |