-
Issue #513: Include DOI and License information in the conventions document
-
Issue #499: Formatting of local links in text
-
Issue #566: Fix invalid CRS WKT attribute in example 5.12.
-
Issue #527: Clarify the conventions for boundary variables, especially for auxiliary coordinate variables of more than one dimension, state that there is no default for boundaries, add more information about bounds in section 1.
-
Issue #550: Include a link to CF area-type table and make explicit the need to use standardized area-type strings in Section 7.3.3.
-
Issue #542: Clarify and rearrange text of section 4.4 about time coordinate units and calendars; introduce new text and a diagram explaining leap-seconds in existing calendars; define leap_second keyword of units_metadata attribute; define utc and tai calendars; define "datetime" in section 1.3.
-
Issue #166: Clarify that time coordinate variables must have
units
containingsince
and a reference time; distinguish between canonical units of time with and withoutsince
. -
Issue #141: Clarification that text may be stored in variables and attributes as either vlen strings or char arrays, and must be represented in Unicode Normalization Form C and encoded according to UTF-8.
-
Issue #367: Remove the AMIP and GRIB columns from the standard name table format defined by Appendix B.
-
Issue #403: Metadata to encode quantization properties
-
Issue #530: Define "the most rapidly varying dimension", and use this phrase consistently with the clarification "(the last dimension in CDL order)".
-
Issue #163: Provide a convention for boundary variables for grids whose cells do not all have the same number of sides.
-
Issue #174: A one-dimensional string-valued variable must not have the same name as its dimension, in order to avoid its being mistaken for a coordinate variable.
-
Issue #237: Clarify that the character set given in section 2.3 for variable, dimension, attribute and group names is a recommendation, not a requirement.
-
Issue #515: Clarify the recommendation to use the convention of 4.3.3 for parametric vertical coordinates, because the previous wording caused confusion.
-
Issue #511: Appendix B: New element in XML file header to record the "first published date"
-
Issue #509: In exceptional cases allow a standard name to be aliased into two alternatives
-
Issue #501: Clarify that data variables and variables containing coordinate data are highly recommended to have
long_name
orstandard_name
attributes, thatcf_role
is used only for discrete sampling geometries and UGRID mesh topologies, and that CF does not prohibit CF attributes from being used in ways that are not defined by CF but that in such cases their meaning is not defined by CF. -
Issue #500: Appendix B: Added a
conventions
string to the standard name xml file format definition
-
Issue #481: Introduce
units_metadata
attribute and clarify some other aspects ofunits
-
Issue #458: Clarify the use of compressed dimensions in related variables
-
Issue #486: Fix PDF formatting problems and invalid references
-
Issue #490: Simple correction to Example 6.1.2
-
Issue #457: Creation date of the draft Conventions document
-
Issue #445: Updates concerning the Polar Stereographic Grid Mapping
-
Issue #468: Update section 2.3 to clarify recommended character set
-
Issue #147: Clarify the use of compressed dimensions in related variables
-
Issue #483: Add a missing author
-
Issue #463: Convert URLs with HTTP protocol to HTTPS if available, fixed a few dead links
-
Issue #383: Link to the CF website and deleted the Preface section
-
Issue #472: Fix incorrect formating for some <= symbols
-
Issue #458: Fix broken link to Unidata documentation.
-
Issue #423: Always use "strictly monotonic" when describing coordinate variables
-
Issue #420: Add List of Figures
-
Issue #210: Correct errors in examples H9-H11
-
Issue #374: Clarify rules for packing and unpacking in Section 8.1
-
Issue #449: Typo in end-date in Example 7.12
-
Issue #266: Updates to some links in the bibliography
-
Issue #286: Some labels of examples contain "Example" so that their label in the list of examples contains "Example" (affects four examples); corrected captions of three tables and five examples
-
Issue #418: Add missing examples to TOE (table of examples); corrected captions of three tables and three examples
-
Issue #367: Delete obsolete references in section 3.3 for mappings of CF standard names to GRIB and PCMDI tables
-
Issue #405: Update ch. 4.4 text on reference time vs. UDUNIT
-
Issue #406: Remove duplicate section 8.2 in the conformance document
-
Issue #391: Correct link to Snyder and typo in the bibliography
-
Issue #437: Correct link to NUG in the bibliography
-
Issue #428: Recording deployment positions
-
Issue #430: Clarify the function of the
cf_role
attribute -
Pull request #408: Deleted a sentence on "rotated Mercator" under
Oblique Mercator
grid mapping in Appendix F -
Issue #265: Clarification of the requirements on bounds variable attributes
-
Issue #260: Clarify use of dimensionless units
-
Issue #410: Delete "on a spherical Earth" from the definition of the
latitude_longitude
grid mapping in Appendix F -
Issue #153: Reference UGRID conventions in CF
-
Pull request #378: Fixed missing semicolon in example 7.16
-
Issue #366: Clarify the intention of standard names
-
Issue #352: Correct errors in description of lossy compression by coordinate subsampling
-
Issue #345: Reformat the revision history
-
Issue #349: Delete unnecessary Conventions attribute in two examples
-
Issue #162: Delete incorrect missing_data attributes of time coordinate variables in two examples
-
Issue #129: timeSeries featureType with a forecast/reference time dimension?
-
Issue #327: Lossy compression by coordinate subsampling, including new Appendix J ("Coordinate Subsampling Methods")
-
Issue #323: Update data model figures for the Domain
-
Issue #319: Restrict "gregorian" label to only dates in the Gregorian calendar
-
Issue #298: Interpretation of negative years in the units attribute
-
Issue #314: Correction to the definition of "ocean sigma over z coordinate" in Appendix D
-
Issue #313: Clarification of the handling of leap seconds
-
Issue #304: Clarify formula terms definitions
-
Issue #301: Introduce the CF domain variable.
-
Issue #288: Remove unnecessary line from table in section 9.3.1
-
Issue #284: Fix the mention of example 6.1.2 in the example list
-
Issue #273: State the principles for design of the CF conventions
-
Issue #295: Correction of figures and their description
-
Issue #243: Rewording changes relating to the new integer types
-
Issue #222: Allow CRS WKT to represent the CRS without requiring reader to compare with grid mapping parameters
-
Issue #193: Figures to clarify the order of the vertices of cell bounds
-
Issue #271: Extend the CF data model for geometries
-
Issue #272: Remove unnecessary netCDF dimensions from some examples
-
Issue #258: Clarification of geostationary projection items
-
Issue #216: New text describing usage of ancillary variables as status/quality flags
-
Issue #159: Incorporate the CF data model into the conventions in new Appendix I
-
Issue #253: Update PROJ links in Appendix F
-
Pull request #236: Fixed the link in the COARDS reference
-
Issue #243: Add new integer types to CF
-
Issue #238: Clarifications to ancillary variables text and examples
-
Issue #230: Correct inconsistency in units of geostationary projection
-
Issue #223: Axis Order for CRS-WKT grid mappings
-
Issue #212: Inconsistent usage of false_easting and false_northing in grid mappings definitions and in examples
-
Issue #218: Taxon Names and Identifiers.
-
Issue #203: Clarifications to use of groups.
-
Issue #213: Missing `s`s in grid mapping description texts.
-
Pull request #202: Fix Section 7 examples numbering in the list of examples
-
Issue #198: Clarification of use of standard region names in "region" variables.
-
Issue #179: Don’t require longitude and Latitude for projected coordinates.
-
Issue #139: Added support for variables of type string.
-
Issue #186: Minor corrections to Example 5.10, Section 9.5 & Appendix F
-
Issue #136: Missing trajectory dimension in H.22
-
Issue #128: Add definition of 'name_strlen' dimension where missing in Appendix H CDL examples.
-
Pull request #142: Fix bad reference to an example in section 6.1 "Labels".
-
Issue #155, Issue #156: Allow alternate grid mappings for geometry containers. When node_count attribute is missing, require the dimension of the node coordinate variables to be one of the dimensions of the data variable.
-
Pull request #146: Typos (plural dimensions) in section H
-
Ticket #164: Add bounds attribute to first geometry CDL example.
-
Ticket #164: Replace axis with bounds for coordinate variables related to geometry node variables.
-
Ticket #164: Add Tim Whiteaker and Dave Blodgett as authors.
-
Ticket #164: Remove geometry attribute from lat/lon variables in examples.
-
Ticket #164: If coordinates attribute is carried by geometry container, require coordinate variables which correspond to node coordinate variables to have the corresponding axis attribute.
-
Ticket #164: Implement suggestions from trac ticket comments.
-
Ticket #164: New Geometries section 7.5.
-
Updated use of WKT-CRS syntax.
-
Trivial updates to links for COARDS and UDUNITS in the bibliography.
-
Updated the links and references to NUG (The NetCDF User Guide), to refer to the current version.
-
A few formatting tweaks.
-
Ticket #140: Added 3 paragraphs and an example to Chapter 7, Section 7.1.
-
Ticket #100: Clarifications to the preamble of sections 4 and 5.
-
Ticket #70: Connecting coordinates to Grid Mapping variables: revisions in Section 5.6 and Examples 5.10 and 5.12
-
Ticket #104: Clarify the interpretation of scalar coordinate variables, changes in sections 5.7 and 6.1
-
Ticket #102: additional cell_methods, changes in Appendix E and section 7.3
-
Ticket #80: added attributes to AppF Table F1, changes in section 5.6 and 5.6.1.
-
Ticket #86: Allow coordinate variables to be scaled integers, affects two table rows in Appendix A.
-
Ticket #138: Clarification of false_easting / false_northing (Table F.1)
-
Ticket #76: More than one name in Conventions attribute (section 2.6.1)
-
Ticket #109: resolve inconsistency of positive and standard_name attributes (section 4.3)
-
Ticket #75: fix documentation and definitions of 3 grid mapping definitions
-
Ticket #143: Supplement the definitions of dimensionless vertical coordinates
-
Ticket #85: Added sentence to bottom of first para in Section 9.1 "Features and feature types". Added Links column in Section 9.1. Replaced first para in Section 9.6. "Missing Data". Added verbiage to Section 2.5.1, "Missing data…". Added sentence to Appendix A "Description" "missing_value" and "Fill_Value".
-
Ticket #145: Add new sentence to bottom of Section 7.2, Add new Section 2.6.3, "External variables". Add "External variable" attribute to Appendix A.
-
Ticket #74: Removed "sea_water_speed" from flag values example and added Note at bottom of Example 3.3 in Chapter 3. Also added a sentence to Appendix C Standard Name Modifiers "number of observations" and and a sentence to "status_flag_modifiers"
-
Ticket #103: Corrections to Appendices A and H, finish the ticket with remaining changes to Appendix H.
-
Ticket #72: Adding the geostationary projection.
-
Ticket #92: Add oblique mercator projection
-
Ticket #87: Allow comments in coordinate variables
-
Ticket #77: Add sinusoidal projection
-
Ticket #149: correction of standard name in example 7.3
-
Ticket #148: Added maximum_absolute_value, minimum_absolute_value and mean_absolute_value to cell methods in Appendix E
-
Ticket #118: Add geoid_name and geopotential_datum_name to the list of Grid Mapping Attributes.
-
Ticket #123: revised section 3.3
-
Ticket #73: renamed Appendix G to Revision History
-
Ticket #31, add new attribute
actual_range
. -
Ticket #141, update affiliation organisations for Jonathan Gregory and Phil Bentley.
-
Ticket #103 updated Type and Use values for some attributes in [attribute-appendix] and added "special purpose" value. In [appendix-examples-discrete-geometries], updated coordinate values for the variables in some examples to correct omissions.
-
Ticket #71, correction of [vertical-perspective] projection.
-
Ticket #67, remove deprecation of "missing_value" from [attribute-appendix].
-
Ticket #93: Added two new dimensionless coordinates to Appendix D.
-
Ticket #69. Added Section 5.6.1, Use of the CRS Well-known Text Format and related changes.
-
Ticket #65: add range entry in Appendix E.
-
Ticket #64: section 7.3 editorial correction, replace "cell_bounds" with "bounds".
-
Ticket #61: two new cell methods in Appendix E.
-
Ticket #37: Added Chapter 9, Discrete Sampling Geometries, and a related Appendix H, and revised several other chapters.
-
In Appendix H (Annotated Examples of Discrete Geometries), updated standard names "station_description" and "station_wmo_id" to "platform_name" and "platform_id".
-
Ticket #47: error in example 7.4
-
Ticket #51: syntax consistency for dimensionless vertical coordinate definitions
-
Ticket #56: typo in CF conventions doc
-
Ticket #57: fix for broken URLs in CF Conventions document
-
Ticket #58: remove deprecation of "missing_value" attribute
-
Ticket #49: clarification of flag_meanings attribute
-
Ticket #33: cell_methods for statistical indices
-
Ticket #45: Fixed defect of outdated Conventions attribute.
-
Ticket #44: Fixed defect by clarifying that coordinates indicate gridpoint location in [coordinate-types].
-
Fixed defect in Mercator section of [appendix-grid-mappings] by updating to version 12 of Grid Map Names.
-
Ticket #34: Added grid mappings Lambert Cylindrical Equal Area, Mercator, and Orthographic to [appendix-grid-mappings].
-
Ticket #17: Changes related to removing ambiguity in [cell-methods].
-
Ticket #36: Fixed defect related to subsection headings in [parametric-v-coord].
-
Ticket #35: Fixed defect in wording of [coordinate-system].
-
Ticket #32: Fixed defect in [coordinate-system].
-
Ticket #30: Fixed defect in Example 4.3, “Atmosphere sigma coordinate”.
-
Ticket #26: [flags], [attribute-appendix], [standard-name-modifiers] : Enhanced the Flags definition to support bit field notation using a
flag_masks
attribute.
-
Ticket #25: Table 3.1, "Supported Units" : Corrected Prefix for Factor "1e-2" from "deci" to "centi".
-
Ticket #18: [grid-mappings-and-projections], [appendix-grid-mappings] : Additions and revisions to CF grid mapping attributes to support the specification of coordinate reference system properties
-
17 January 2008: [coordinate-types], [coordinate-system]: Made changes regarding use of the axis attribute to identify horizontal coordinate variables.
-
17 January 2008: Changed text to refer to rules of CF governance, and provisional status.
-
21 March 2006: Added the section called "Atmosphere natural log pressure coordinate".
-
21 March 2006: Added the section called "Azimuthal equidistant".
-
25 November 2005: the section called "Atmosphere hybrid height coordinate" : Fixed definition of atmosphere hybrid height coordinate.
-
22 October 2004: Added [lambert-conformal-projection].
-
20 September 2004: [cell-methods] : Changed several incorrect occurrences of the cell method
"standard deviation"
to"standard_deviation"
. -
1 July 2004: [multiple-forecasts-from-single-analysis] : Added
positive
attribute to the scalar coordinate p500 to make it unambiguous that the pressure is a vertical coordinate value. -
1 July 2004: [scalar-coordinate-variables] : Added note that use of scalar coordinate variables inhibits interoperability with COARDS conforming applications.
-
14 June 2004: the section called "Polar Stereographic" : Added
latitude_of_projection_origin
map parameter. -
14 June 2004: Added the section called “Lambert azimuthal equal area”.