Global Argo Data Global Argo Data Repository Status Report Repository Status Report for 2009for 2009

Charles SunCharles Sun

US National Oceanographic Data CenterUS National Oceanographic Data Center

1010thth Argo Data Management Team Meeting Argo Data Management Team Meeting30 September – 2 October 2009, Toulouse, 30 September – 2 October 2009, Toulouse,

FranceFrance

22

Highlights of ActivitiesHighlights of Activities

Continued daily operations of the GADR.Continued daily operations of the GADR. Performed an automated procedure of Performed an automated procedure of

“mirroring” a local Argo data set in sync with the “mirroring” a local Argo data set in sync with the Argo GDAC server at Monterey, CA.Argo GDAC server at Monterey, CA.

Implemented an automated procedure for Implemented an automated procedure for acquiring the CLIVAR & Carbon Hydrographic acquiring the CLIVAR & Carbon Hydrographic Data Office (CCHDO) data from the Web for Data Office (CCHDO) data from the Web for archive accession.archive accession.

Produced monthly archives of the Argo data Produced monthly archives of the Argo data archived at the NODC and populated them at archived at the NODC and populated them at http://argo.nodc.noaa.gov/ http://argo.nodc.noaa.gov/

Identified the deficiency of the Argo NetCDF Identified the deficiency of the Argo NetCDF format convention and developed a strategy for format convention and developed a strategy for improving the Argo convention in compliance with improving the Argo convention in compliance with the Climate and Forecast (CF) metadata the Climate and Forecast (CF) metadata convention.convention.

33

GADR Web Server GADR Web Server StatisticsStatistics Monthly average of Monthly average of

requests (files):requests (files):– 595,908 in 2007595,908 in 2007– 1,021,903 in 20081,021,903 in 2008– 1,006,767 in 20091,006,767 in 2009**

Monthly average of Monthly average of data download:data download:– 23.55 GB in 200723.55 GB in 2007– 42.41 GB in 2008 42.41 GB in 2008 – 54.57 GB in 200954.57 GB in 2009**

*ending August 2009

Argo Web Server Statistics by Month

0.0

0.5

1.0

1.5

2.0

Sep-08

Oct-08

Nov-08

Dec-08

Jan-09

Feb-09

Mar-09

Apr-09

May-09

Jun-09

Jul-09

Aug-09

Mill

ion

sN

um

be

r o

f R

eq

ue

sts

Argo Data Downloaded by Month

0

20

40

60

80

100

120

Sep-08

Oct-08

Nov-08

Dec-08

Jan-09

Feb-09

Mar-09

Apr-09

May-09

Jun-09

Jul-09

Aug-09

Nu

mb

er o

f D

ata

Do

wn

load

ed (

GB

)

44

Argo User data and File Argo User data and File Type ReportType Report

20072007 20082008

extensaioextensaionn

# reqs# reqs % reqs% reqs % bytes% bytes # reqs# reqs % % reqsreqs

% bytes% bytes

.txt.txt 903,161903,161 12.5012.50 44.2344.23 1,133,2811,133,281 9.239.23 42.2642.26

.nc.nc 5,383,965,383,9666

74.5374.53 28.1928.19 9,402,2409,402,240 76.5776.57 27.9927.99

.tgz.tgz 111,439111,439 1.541.54 13.613.6 169,826169,826 1.381.38 11.3811.38

.kmz.kmz 904904 0.010.01 1.581.58 13,26213,262 0.110.11 8.428.42

.htm.htm 648,543648,543 8.988.98 5.655.65 1,032,6221,032,622 8.418.41 4.214.21

totaltotal 7,223,817,223,8155

285.03G285.03GBB

12,279,9512,279,9577

509.79G509.79GBB

55

Argo Monthly Archives Web Argo Monthly Archives Web SiteSite

http://argo.nodc.noaa.gov/

66

Argo NetCDF Format Argo NetCDF Format IssueIssue• The Geographic Coordinate System is not well-defined The Geographic Coordinate System is not well-defined

in the Argo individual profile NetCDF format file.in the Argo individual profile NetCDF format file.• The Argo NetCDF convention is not in compliance with The Argo NetCDF convention is not in compliance with

the CF (Climate and Forecast) metadata convention.the CF (Climate and Forecast) metadata convention.• The CF (and COARS) NetCDF convention suggests:The CF (and COARS) NetCDF convention suggests:

• Any 4-dimensional data should have four coordinates Any 4-dimensional data should have four coordinates (axes), "date or time" (a.k.a. "T"), "height or depth" (a.k.a. (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"). "Z"), "latitude" (a.k.a. "Y"), or "longitude" (a.k.a. "X").

• Order of dimensions: If any or all of the dimensions of a Order of dimensions: If any or all of the dimensions of a variable have the interpretations of "date or time“, "height variable have the interpretations of "date or time“, "height or depth" "latitude”, or "longitude" then those dimensions or depth" "latitude”, or "longitude" then those dimensions should appear in the relative order T, then Z, then Y, then should appear in the relative order T, then Z, then Y, then X in the CDL definition corresponding to the file.X in the CDL definition corresponding to the file.

• The dimension name of each coordinate variable should The dimension name of each coordinate variable should be the same as its variable name, i.e., time(time), be the same as its variable name, i.e., time(time), depth(depth), latitude(latitude), and longitude(longitude).depth(depth), latitude(latitude), and longitude(longitude).

77

What do we have in the What do we have in the Argo NetCDF format Argo NetCDF format files?files?

netcdf R7900061_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, -1.244, -1.244, … PSAL = 33.919, 33.920, 33.919, ...

88

What’s the Issue?What’s the Issue?

Annoying and Inconvenient!Annoying and Inconvenient!

Use a generic NetCDF browser, Use a generic NetCDF browser, “ncBrowse”, to illustrate the Argo NetCDF “ncBrowse”, to illustrate the Argo NetCDF format issue.format issue.

99

1010

Profile Plot ComparisonProfile Plot Comparison

Original Format Profile Plot Modified Format Profile Plot

1111

Suggestions of Format Suggestions of Format Changes (shown in red)Changes (shown in red)

netcdf R7900061_058_mod {dimensions: DATE_TIME = 14 ; … ; N_PROF = 1 ; N_PARAM = 3 ; N_LEVELS = 454 ; N_CALIB = 1 ; N_HISTORY = UNLIMITED ; // (2 currently) TIME = 1 ; PRES = 454 ; LONGITUDE = 1 ; LATITUDE = 1 ;

variables:double JULD (N_PROF) ;double TIME(TIME) ;

float PRES(N_PROF, N_LEVELS) ;float PRES(PRES) ;

float TEMP(N_PROF, N_LEVELS) ;float TEMP(TIME,PRES,LATITUDE,LONGITUDE) ;

float PSAL(N_PROF, N_LEVELS) ;float PSAL(TIME,PRES,LATITUDE,LONGITUDE) ;…

1212

Other Suggestions for Other Suggestions for ImprovementsImprovements

Spell out whole variable names, Spell out whole variable names, such as “pressure” instead of such as “pressure” instead of “PRES”, “temperature” or “PRES”, “temperature” or “sea_temperature” instead of “sea_temperature” instead of “TEMP” etc.“TEMP” etc.

Use lower case for all variable Use lower case for all variable names.names.

1313

Future PlanFuture Plan

Continue GADR operations.Continue GADR operations. Continue to acquire the CCHDO Continue to acquire the CCHDO

data via the Internet on a data via the Internet on a quarterly basis.quarterly basis.

Continue to populate the Argo Continue to populate the Argo data archives on a monthly basis .data archives on a monthly basis .

1414

Comments & Questions

1515

BackgroundBackground