Global Argo Data Repository Status Report for 2009 Charles Sun US National Oceanographic Data Center 10 th Argo Data Management Team Meeting 30 September – 2 October 2009, Toulouse, France
Highlights of Activities n n n Continued daily operations of the GADR. Performed an automated procedure of “mirroring” a local Argo data set in sync with the Argo GDAC server at Monterey, CA. Implemented an automated procedure for acquiring the CLIVAR & Carbon Hydrographic Data Office (CCHDO) data from the Web for archive accession. Produced monthly archives of the Argo data archived at the NODC and populated them at http: //argo. nodc. noaa. gov/ Identified the deficiency of the Argo Net. CDF format convention and developed a strategy for improving the Argo convention in compliance with the Climate and Forecast (CF) metadata convention. 2
GADR Web Server Statistics n Monthly average of requests (files): – 595, 908 in 2007 – 1, 021, 903 in 2008 – 1, 006, 767 in 2009* n Monthly average of data download: – – – 23. 55 GB in 2007 42. 41 GB in 2008 54. 57 GB in 2009* *ending August 2009 3
Argo User data and File Type Report 2007 extensaion # reqs % reqs 2008 % bytes # reqs % bytes . txt 903, 161 12. 50 44. 23 1, 133, 281 9. 23 42. 26 . nc 5, 383, 966 74. 53 28. 19 9, 402, 240 76. 57 27. 99 . tgz 111, 439 1. 54 13. 6 169, 826 1. 38 11. 38 . kmz 904 0. 01 1. 58 13, 262 0. 11 8. 42 . htm 648, 543 8. 98 5. 65 1, 032, 622 8. 41 4. 21 285. 03 GB 12, 279, 957 total 7, 223, 815 509. 79 GB 4
Argo Monthly Archives Web Site http: //argo. nodc. noaa. gov/ 5
Argo Net. CDF Format Issue • The Geographic Coordinate System is not well-defined in the Argo individual profile Net. CDF format file. • The Argo Net. CDF convention is not in compliance with the CF (Climate and Forecast) metadata convention. • The CF (and COARS) Net. CDF convention suggests: • Any 4 -dimensional data should have four coordinates (axes), "date or time" (a. k. a. "T"), "height or depth" (a. k. a. "Z"), "latitude" (a. k. a. "Y"), or "longitude" (a. k. a. "X"). • Order of dimensions: If any or all of the dimensions of a variable have the interpretations of "date or time“, "height or depth" "latitude”, or "longitude" then those dimensions should appear in the relative order T, then Z, then Y, then X in the CDL definition corresponding to the file. • The dimension name of each coordinate variable should be the same as its variable name, i. e. , time(time), depth(depth), latitude(latitude), and longitude(longitude). 6
What do we have in the Argo Net. CDF format files? netcdf R 7900061_058 { dimensions: DATE_TIME = 14 ; …; N_PROF = 1 ; N_PARAM = 3 ; N_LEVELS = 454 ; N_CALIB = 1 ; N_HISTORY = UNLIMITED ; // (2 currently) variables: double JULD (N_PROF) ; JULD: long_name = “…" ; float PRES(N_PROF, N_LEVELS) ; PRES: long_name = “…" ; float TEMP(N_PROF, N_LEVELS) ; TEMP: long_name = “…”; float PSAL(N_PROF, N_LEVELS) ; PSAL: long_name = “…. " ; … data: JULD = 21788. 3671064973 ; LATITUDE = -53. 5970001220703 ; LONGITUDE = 6. 85099983215332 ; PRES = 2. 0, 4. 0, 6. 0, … TEMP = -1. 244, … PSAL = 33. 919, 33. 920, 33. 919, . . . 7
What’s the Issue? Annoying and Inconvenient! Use a generic Net. CDF browser, “nc. Browse”, to illustrate the Argo Net. CDF format issue. 8
9
Profile Plot Comparison Original Format Profile Plot Modified Format Profile Plot 10
Suggestions of Format Changes (shown in red) variables: netcdf R 7900061_058_mod { double JULD (N_PROF) ; dimensions: double TIME(TIME) ; DATE_TIME = 14 ; …; float PRES(N_PROF, N_LEVELS) ; N_PROF = 1 ; float PRES(PRES) ; N_PARAM = 3 ; N_LEVELS = 454 ; float TEMP(N_PROF, N_LEVELS) ; N_CALIB = 1 ; float TEMP(TIME, PRES, LATITUDE, LONGITUDE) ; N_HISTORY = UNLIMITED ; // (2 currently) float PSAL(N_PROF, N_LEVELS) ; TIME = 1 ; float PSAL(TIME, PRES, LATITUDE, LONGITUDE) ; PRES = 454 ; … LONGITUDE = 1 ; LATITUDE = 1 ; 11
Other Suggestions for Improvements Spell out whole variable names, such as “pressure” instead of “PRES”, “temperature” or “sea_temperature” instead of “TEMP” etc. n Use lower case for all variable names. n 12
Future Plan Continue GADR operations. n Continue to acquire the CCHDO data via the Internet on a quarterly basis. n Continue to populate the Argo data archives on a monthly basis. n 13
Comments & Questions 14
Background 15
Скачать презентацию Global Argo Data Repository Status Report for 2009
7071dbd24e928f5f79d7fa7acd0f0ea2.ppt