Knowledge

Climate and Forecast Metadata Conventions

Source 📝

298:
A central element of the CF Conventions is the CF Standard Name Table. The CF Standard Name Table uniquely associates a standard name with each geophysical parameter in a data set, where each name provides a precise description of physical quantities being represented. Note that this is the string
53:
The CF conventions were introduced in 2003, after several years of development by a collaboration that included staff from U.S. and European climate and weather laboratories. The conventions contained generalizations and extensions to the earlier Cooperative Ocean/Atmosphere Research Data Service
32:
variable represent, and of the spatial and temporal properties of the data, including information about grids, such as grid cell bounds and cell averaging methods. This enables users of files from different sources to decide which variables are comparable, and is a basis for building software
28:. The metadata defined by the CF conventions are generally included in the same file as the data, thus making the file "self-describing". The conventions provide a definitive description of what the data values found in each 94:. They are also used as a technical foundation for a number of software packages and data systems, including the Climate Model Output Rewriter (CMOR), which is post processing software for climate model data, and the 743:. 25th Conference on International Interactive Information and Processing Systems (IIPS) for Meteorology, Oceanography, and Hydrology, 89th American Meteorological Society Meeting. 818: 489: 78:
The CF conventions have been adopted by a wide variety of national and international programs and activities in the Earth sciences. For example, they were required for the
533: 700: 359: 98:, which distributes climate and other data. The CF conventions have also been used to describe the physical fields transferred between individual Earth system model 54:(COARDS) conventions and the Gregory/Drach/Tett (GDT) conventions. As the scope of the CF conventions grew along with its user base, the CF community adopted an 303:
attribute, not the name of the parameter. The CF standard name table identifies over 1,000 physical quantities, each with a precise description and associated
838: 642: 470: 843: 87: 66:
as a recommended standard (number 08-012) for the representation and transport of gridded data. The CF conventions are being considered by the
83: 808: 368:
version 2021b supports netCDF CF Convention. Averaging can be performed during import to allow handling of large datasets in a GUI software.
352:) of the CF conventions. The authors of the CFDM and CF-Python currently assert a desire to fully support all aspects of the CF conventions. 715: 621: 418: 803: 813: 496: 146:, but its structure is general and it has been adapted for use with other data formats. For example, using the CF conventions with 443: 91: 365: 530: 118:
data, in the atmosphere, ocean, and other physical domains. It was designed primarily to address gridded data types such as
119: 310:
As an example of the information provided by CF standard names, the entry for sea-level atmospheric pressure includes:
667:
Dunlap, R. L. Mark, S. Rugaber, V. Balaji, J. Chastang, L. Cinquini, C. DeLuca, D. Middleton, and S. Murphy (2008).
646: 848: 603: 147: 775: 585: 474: 130:
is used to impose a regular structure. However, the CF conventions are also applicable to many classes of
90:
assessment reports. They are promoted as an important element of scientific community coordination by the
754: 694: 382:
Python library "draws heavily from the NetCDF CF Metadata Conventions as a source for its data model".
514: 99: 740: 567: 401: 131: 42: 722: 307:. Guidelines for construction of CF standard names are documented on the conventions web site. 625: 355: 833: 95: 422: 680: 379: 111: 549: 537: 304: 182: 55: 34: 814:
Standard for the CF Metadata Conventions (Marine Metadata Interoperability Project page)
741:"Investigation of using HDF5 archival information packages (AIP) to store NASA ECS data" 550:"Report of the 12th Session of the JSC/CLIVAR Working Group on Coupled Modelling (WGCM)" 165:
Conventions should be developed only as needed, rather than anticipating possible needs.
21: 447: 827: 79: 38: 471:"Maintaining and Advancing the CF Standard for Earth System Science Community Data" 329: 127: 162:
Data should be self-describing, without external tables needed for interpretation.
168:
Conventions should not be onerous to use for either data-writers or data-readers.
123: 115: 70:
Standards Process Group (SPG) and others as more broadly applicable standards.
685: 668: 531:
Projects and Groups Adopting or Encouraging the CF-Conventions as a Standard
321: 25: 171:
Metadata should be readable by humans as well as interpretable by programs.
375:
Python library parses and decodes data stored according to CF Conventions.
174:
Redundancy should be avoided to prevent inconsistencies when writing data.
17: 345: 178:
Specific CF metadata descriptors use values of attributes to represent
59: 716:"Metadata Standards for Gridded Climate Data in the Earth System Grid" 622:"Metadata Standards for Gridded Climate Data in the Earth System Grid" 515:"Web Coverage Service (WCS) 1.1 extension for CF-netCDF 3.0 encoding" 143: 29: 669:"Earth system curator: metadata infrastructure for climate modeling" 798: 349: 134:
and have been adopted by a number of groups for such applications.
325: 67: 63: 348:
is a data analysis package built on a complete implementation (
332:
at sea level is the quantity often abbreviated as MSLP or PMSL.
102:, such as atmosphere and ocean components, as the model runs . 586:"Issues Related to the Dissemination of Climate Model Output" 372: 158:
Several principles guide the development of CF conventions:
58:
model. In December 2008 the trio of standards, netCDF+CF+
24:
data, intended to promote the processing and sharing of
444:"GDT netCDF conventions for climate data, version 1.3" 419:"Conventions for the Standardization of NetCDF files" 568:"Data Issues for WCRP Weather and Climate Modeling" 20:conventions are conventions for the description of 142:CF originated as a standard for data written in 637: 635: 8: 699:: CS1 maint: multiple names: authors list ( 684: 88:Intergovernmental Panel on Climate Change 392: 804:The CF Metadata Convention (BADC page) 692: 84:Coupled model intercomparison projects 7: 215:Description of associated activity: 839:Earth sciences metadata conventions 739:Yang, M.; R. Duerr; C. Lee (2009). 358:parses CF Conventions and creates 320:description: sea_level means mean 14: 755:"NetCDF Importing and Processing" 844:Meteorological data and networks 819:Ocean Data Standards on Metadata 446:. March 14, 1999. Archived from 294:, and climatological statistics. 92:World Climate Research Programme 86:, which are widely used for the 776:"Metadata - Iris Documentation" 604:"Climate Model Output Rewriter" 16:The Climate and Forecast (CF) 1: 566:Kinter, James L. III (2005). 205:(audit trail of operations), 809:NASA Standards Process Group 259:Description of coordinates: 120:numerical weather prediction 110:CF is intended for use with 602:Doutriaux, Charles (2010). 33:applications with powerful 865: 421:. May 1995. Archived from 402:"The CF metadata standard" 400:Gregory, Jonathan (2003). 82:output data collected for 74:Applications and user base 686:10.1007/s12145-008-0016-1 673:Earth Science Informatics 490:"CF Metadata Conventions" 316:air_pressure_at_sea_level 536:August 23, 2010, at the 324:, which is close to the 150:data has been explored. 148:Hierarchical Data Format 469:Lawrence, B.N. (2003). 286:Meaning of grid cells: 275:); time specified with 645:. 2006. Archived from 643:"NetCDF in ArcGIS 9.2" 513:Domenico, Ben (2009). 279:("time since T0") and 138:Supported data formats 799:CF Metadata Home Page 584:Taylor, Karl (2005). 225:Description of data: 49:History and evolution 106:Supported data types 620:Drach, Bob (2002). 356:NetCDF-Java Library 335:canonical units: Pa 239:auxiliary_variables 100:software components 714:V. Balaji (2008). 488:Rew, Russ (2010). 132:observational data 122:model outputs and 43:data visualization 37:, grid remapping, 362:objects from them 360:Coordinate System 154:Design principles 96:Earth System Grid 62:, was adopted by 856: 849:Science software 786: 785: 783: 782: 772: 766: 765: 763: 762: 751: 745: 744: 736: 730: 729: 727: 721:. Archived from 720: 711: 705: 704: 698: 690: 688: 679:(3–4): 131–149. 664: 658: 657: 655: 654: 639: 630: 629: 624:. Archived from 617: 611: 610: 608: 599: 593: 592: 590: 581: 575: 574: 572: 563: 557: 556: 554: 546: 540: 528: 522: 521: 519: 510: 504: 503: 501: 495:. Archived from 494: 485: 479: 478: 473:. Archived from 466: 460: 459: 457: 455: 450:on June 10, 2010 440: 434: 433: 431: 430: 415: 409: 408: 406: 397: 317: 302: 293: 289: 282: 278: 274: 270: 266: 262: 256: 252: 248: 244: 240: 236: 232: 228: 222: 218: 212: 208: 204: 200: 196: 192: 188: 112:state estimation 864: 863: 859: 858: 857: 855: 854: 853: 824: 823: 795: 790: 789: 780: 778: 774: 773: 769: 760: 758: 757:. originlab.com 753: 752: 748: 738: 737: 733: 725: 718: 713: 712: 708: 691: 666: 665: 661: 652: 650: 641: 640: 633: 619: 618: 614: 606: 601: 600: 596: 588: 583: 582: 578: 570: 565: 564: 560: 552: 548: 547: 543: 538:Wayback Machine 529: 525: 517: 512: 511: 507: 499: 492: 487: 486: 482: 468: 467: 463: 453: 451: 442: 441: 437: 428: 426: 417: 416: 412: 404: 399: 398: 394: 389: 342: 315: 314:standard name: 305:canonical units 300: 291: 287: 280: 276: 272: 268: 264: 260: 254: 250: 246: 242: 238: 234: 230: 226: 220: 216: 210: 206: 202: 198: 194: 190: 186: 183:Data provenance 156: 140: 108: 76: 56:open governance 51: 35:data extraction 12: 11: 5: 862: 860: 852: 851: 846: 841: 836: 826: 825: 822: 821: 816: 811: 806: 801: 794: 793:External links 791: 788: 787: 767: 746: 731: 728:on 2010-05-28. 706: 659: 631: 628:on 2004-09-12. 612: 594: 576: 558: 541: 523: 505: 502:on 2014-04-04. 480: 477:on 2010-05-27. 461: 435: 410: 391: 390: 388: 385: 384: 383: 376: 369: 363: 353: 341: 338: 337: 336: 333: 328:in sea areas. 318: 296: 295: 284: 277:reference_time 257: 223: 213: 201:(e.g. model), 176: 175: 172: 169: 166: 163: 155: 152: 139: 136: 126:data in which 107: 104: 75: 72: 50: 47: 45:capabilities. 22:Earth sciences 13: 10: 9: 6: 4: 3: 2: 861: 850: 847: 845: 842: 840: 837: 835: 832: 831: 829: 820: 817: 815: 812: 810: 807: 805: 802: 800: 797: 796: 792: 777: 771: 768: 756: 750: 747: 742: 735: 732: 724: 717: 710: 707: 702: 696: 687: 682: 678: 674: 670: 663: 660: 649:on 2010-06-14 648: 644: 638: 636: 632: 627: 623: 616: 613: 605: 598: 595: 587: 580: 577: 569: 562: 559: 551: 545: 542: 539: 535: 532: 527: 524: 516: 509: 506: 498: 491: 484: 481: 476: 472: 465: 462: 449: 445: 439: 436: 425:on 2010-05-27 424: 420: 414: 411: 403: 396: 393: 386: 381: 377: 374: 370: 367: 364: 361: 357: 354: 351: 347: 344: 343: 339: 334: 331: 327: 323: 319: 313: 312: 311: 308: 306: 301:standard_name 299:value of the 292:cell_measures 285: 273:formula_terms 258: 255:flag_meanings 243:missing_value 231:standard_name 224: 214: 184: 181: 180: 179: 173: 170: 167: 164: 161: 160: 159: 153: 151: 149: 145: 137: 135: 133: 129: 125: 121: 117: 113: 105: 103: 101: 97: 93: 89: 85: 81: 80:climate model 73: 71: 69: 65: 61: 57: 48: 46: 44: 40: 39:data analysis 36: 31: 27: 23: 19: 779:. Retrieved 770: 759:. Retrieved 749: 734: 723:the original 709: 695:cite journal 676: 672: 662: 651:. Retrieved 647:the original 626:the original 615: 597: 579: 561: 544: 526: 508: 497:the original 483: 475:the original 464: 452:. Retrieved 448:the original 438: 427:. Retrieved 423:the original 413: 395: 330:Air pressure 309: 297: 288:cell_methods 269:grid_mapping 177: 157: 141: 128:data binning 109: 77: 52: 15: 283:attributes. 261:coordinates 251:flag_values 247:valid_range 191:institution 124:climatology 116:forecasting 828:Categories 781:2023-02-10 761:2021-05-11 653:2010-06-23 429:2010-06-23 387:References 221:experiment 207:references 26:data files 366:OriginPro 346:CF-Python 322:sea level 235:long_name 834:Metadata 534:Archived 454:June 23, 340:Software 281:calendar 18:metadata 555:. 2009. 217:project 211:comment 203:history 195:contact 60:OPeNDAP 373:xarray 271:(with 265:bounds 199:source 144:netCDF 41:, and 30:netCDF 726:(PDF) 719:(PDF) 607:(PDF) 589:(PDF) 571:(PDF) 553:(PDF) 518:(PDF) 500:(PDF) 493:(PDF) 405:(PDF) 326:geoid 227:units 187:title 701:link 456:2010 380:Iris 378:The 371:The 350:CFDM 114:and 68:NASA 64:IOOS 681:doi 830:: 697:}} 693:{{ 675:. 671:. 634:^ 290:, 267:, 263:, 253:, 249:, 245:, 241:, 237:, 233:, 229:, 219:, 209:, 197:, 193:, 189:, 185:: 784:. 764:. 703:) 689:. 683:: 677:1 656:. 609:. 591:. 573:. 520:. 458:. 432:. 407:.

Index

metadata
Earth sciences
data files
netCDF
data extraction
data analysis
data visualization
open governance
OPeNDAP
IOOS
NASA
climate model
Coupled model intercomparison projects
Intergovernmental Panel on Climate Change
World Climate Research Programme
Earth System Grid
software components
state estimation
forecasting
numerical weather prediction
climatology
data binning
observational data
netCDF
Hierarchical Data Format
Data provenance
canonical units
sea level
geoid
Air pressure

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.