Home

Argo user's manual - Archimer

1. hits or buoyancy issues DAST Deep Ascent JULD DEEP ASCENT START Time when float begins its rise to drift pressure Start Time JULD DEEP ASCENT START Typical for profile on descent floats STATUS AST Ascent Start JULD ASCENT START Time when float begins to return to the surface Time JULD ASCENT START STATUS AET Ascent End JULD ASCENT END Time when float reaches the surface Time JULD ASCENT END STATUS TST Transmission JULD TRANSMISSION START Time when float begins transmitting Start Time JULD TRANSMISSION START STATUS FMT First Message JULD FIRST MESSAGE Earliest time of all received float messages Time JULD FIRST MESSAGE _ STATUS FLT First Location JULD FIRST LOCATION Earliest location of all float locations Time JULD FIRST LOCATION STATUS LLT Last Location JULD LAST LOCATION Latest location of all float locations Time JULD LAST LOCATION STATUS LMT Last Message JULD LAST MESSAGE Latest time of all received float messages Time JULD LAST MESSAGE STATUS TET Transmission JULD TRANSMISSION END Time when floats stops transmitting End Time JULD TRANSMISSION END STATUS General Measurement Code Table Key Measurement code type Definition Argo data management User s manual Any code evenly divisible by 50 but not evenly divisible by 100 e g 150 250 450 etc Any code that falls in between any Primary or Secondary Measurement Code span of 50 values These codes describe data that are important cycle timi
2. Field Sample Explanation HISTORY INSTITUTION Cl Selected from the list in reference table 4 HISTORY_STEP ARGQ Selected from the list in reference table 12 HISTORY_SOFTWARE FillValue This field does not apply HISTORY SOFTWARE RELEASE FillValue This field does not apply HISTORY REFERENCE FillValue This field does not apply HISTORY DATE 2003080500000 The year month day hour minute second that the process 0 ran HISTORY ACTION CF Selected from the list in reference table 7 HISTORY PARAMETER TEMP Selected from the list in reference table 3 HISTORY START PRES 75 Shallowest pressure of action HISTORY STOP PRES 105 Deepest pressure of action HISTORY PREVIOUS VALUE 1 This is the value of the quality flag on temperature readings before the change was made HISTORY QCTEST FillValue This field does not apply Notes 1 The new QC flag of 4 to indicate wrong values would appear in the param QC field Argo data management User s manual sr 6 DAC GDAC data management This chapter describes the data management organization between Argo DACs and GDACS Each DAC submits regularly all its new files to both USGODAE and Coriolis GDACs On both GDACs each DAC has an ftp account with e a submit directory to submit files e areject directory that contains the submitted file that were rejected by GDACS files format checker Seven types of files are accepted on GDAC A float metadata file A float trajecto
3. HISTORY DATE long name Date the history record was created HISTORY DATE conventions YYYYMMDDHHMISS HISTORY DATE FillValue Date of the action Example 20011217160057 HISTORY ACTION char HISTORY ACTION N HISTORY N PROF STRING4 HISTORY ACTION long name Action performed on data HISTORY ACTION conventions Argo reference table 7 HISTORY ACTION FillValue Name of the action The action codes are described in reference table 7 Example QCF for QC failed HISTORY PARAMETER char HISTORY PARAMETER N HISTORY N PROF STRING16 HISTORY PARAMETER long name Station parameter action is performed on HISTORY PARAMETER conventions Name of the parameter on which the action is performed Example PSAL Argo data management User s manual 4 Argo reference table 3 HISTORY PARAMETER FillValue HISTORY START PRES float HISTORY START PRES N HISTORY N PROF HISTORY START PRES long name Start pressure action applied on HISTORY START PRES FillValue 99999 f HISTORY START PRES units decibar Start pressure the action is applied to Example 1500 0 HISTORY STOP PRES float HISTORY STOP PRES N HISTORY N PROF HISTORY STOP PRES long name Stop pressure action applied on HISTORY STOP PRES FillValue 99999 f HISTORY STOP PRES units decibar Stop pressure the action is applied to This
4. JULD QC long name Quality on Date and The flag scale is described in the reference table Argo data management User s manual Time JULD QC conventions Argo reference table 2 FillValue 2 Example 1 the date and time seems correct JULD_LOCATION double J ULD_LOCATION N_PROF JULD_LOCATION long_name Julian day UTC of the location relative to REFERENCE_DATE_TIME JULD_LOCATION units days since 1950 01 01 00 00 00 UTC JULD_LOCATION conventions Relative julian days with decimal part as parts of day LOCATION FillValue 999999 Julian day of the location of the profile 1 The integer part represents the day the decimal part represents the time of the profile Date and time are in universal time coordinates The julian day is relative to REFERENCE_DATE_TIME Example 18833 8013889885 July 25 2001 19 14 00 POSITION_QC long_name Quality on position latitude and longitude POSITION_QC conventions Argo reference table 2 POSITION FillValue LATITUDE double LATITUDE N_PROF Latitude of the profile LATITUDE long_name Latitude of the Unit degree north station best estimate This field contains the best estimated latitude LATITUDE standard name latitude The latitude value may be improved in delayed LATITUDE units degree north mode LATITUDE FillValue 99999 The measure
5. n Meaning Real time comment Delayed mode comment 0 No QC was No QC was performed No QC was performed performed 1 Good data All Argo real time QC tests passed The adjusted value is statistically consistent and a statistical error estimate is supplied 2 Probably good Not used in real time Probably good data data 3 Bad data that Test 15 or Test 16 or Test 17 failed and all other An adjustment has been applied but the are potentially real time QC tests passed These data are not to be value may still be bad correctable used without scientific correction A flag 3 may be assigned by an operator during additional visual QC for bad data that may be corrected in delayed mode 4 Bad data Data have failed one or more of the real time QC Bad data Not adjustable tests excluding Test 16 A flag 4 may be assigned by an operator during additional visual QC for bad data that are not correctable 5 Value changed Value changed Value changed 6 Not used Not used Not used 7 Not used Not used Not used 8 Interpolated Interpolated value Interpolated value value 9 Missing value Missing value Missing value A list of real time QC tests can be found in Table 11 Argo data management User s manual e 3 2 2 Reference table 2a profile quality flag N is defined as the percentage of levels with good data where e QC flag values of 1 2 5 or 8 are GOOD data e QC flag values
6. 2 01 11 11 2005 Thierry Carval 2 2 4 82 3 4 accept adjusted parameters in real time files 2 01 11 11 2005 Thierry Carval 2 2 6 history section for multi profile files is empty 2 01 11 11 2005 Thierry Carval 1 3 52 2 3 82 3 4 real time adjusted data 2 01 11 11 2005 Thierry Carval 2 4 8 highly desirable meta data description 2 1 30 11 2005 Annie Wong 83 2 1 update on flag 4 real time comment 21 20 12 2005 Thierry Carval remove erroneous blanks ex Argo reference table 3 2 1 01 03 2006 Mark gnaszewski 82 3 6 Change HISTORY INDEX to int Change HISTORY REFERENCE to STRING64 Change to dependent in all sections Remove PLATFORM SERIAL NO from desirable parameter table Add No QC performed to Table 2a Change FORMAT VERSION to 2 2 in all sections 21 26 09 2006 Thierry Carval 82 4 3 TRANS SYSTEM ID use N A when not applicable eg Iridium or Orbcomm 21 27 11 2006 Thierry Carval 82 4 8 highly desirable metadata PARKING PRESSURE may be empty for floats drifting Argo data management User s manual along a selected density level 2 1 09 06 2008 Claudia Schmid 3 3 use DOXY2 for floats equipped with 2 oxygen sensors 2 2 12 02 2009 Claudia Schmid 84 1 file naming convention multi profiles cycle 2 2 03 03 2009 Thierry Carval 6 1 greylist file collection 82 2 2 move date creation and date update to general information on profile file section
7. DATA_TYPE FORMAT_VERSION HANDBOOK_VERSION DATE_CREATION DATE_UPDATE Definition char DATA_TYPE STRING16 DATA_TYPE long_name Data type DATA_TYPE _FillValue char FORMAT_VERSION STRING4 FORMAT_VERSION long_name File format version FORMAT VERSION FillValue char HANDBOOK_VERSION STRING4 HANDBOOK_VERSION long_name Data handbook version HANDBOOK VERSION FillValue char DATE CREATION DATE TIME DATE CREATION long name Date of file creation DATE CREATIOON conventions YYYYMMDDHHMISS DATE CREATION FillValue char DATE UPDATE DATE TIME DATE UPDATE long name Date of update of this file DATE UPDATE conventions YYYYMMDDHHMISS DATE UPDATE FillValue 2 4 4 Float characteristics This section contains the main characteristics of the float PLATFORM NUMBER Definition char PLATFORM NUMBER STRINGB8 PLATFORM NUMBER long name Float unique identifier PLATFORM NUMBER conventions WMO float identifier ASIII PLATFORM NUMBER FillValue char PTT STRING256 PTT long name Transmission identifier ARGOS ORBCOMM etc PTT FillValue Comment MANDATORY This field contains the type of data contained in the file The list of acceptable data types is in the reference table 1 Example Argo meta data File format version Example 3 0 Version number of the data handbook This field indicates tha
8. ee ee esee eese en sese etta sese teta sese seen e sete ea sese 69 3 13 REFERENCE TABLE 13 OCEAN CODBES 7 t eee eo Da Fe aane a eo pe aeo EISSES 69 3 14 REFERENCE TABLE 14 TECHNICAL PARAMETER NAMES eee ee esee en seen eo seo tosta sese aseo susto 70 3 15 REFERENCE TABLE 15 CODES OF TRAJECTORY MEASUREMENTS PERFORMED WITHIN A r o 71 3 16 REFERENCE TABLE 16 VERTICAL SAMPLING SCHEMES eee eee ense ee een sees en sese ee ease seen au 77 3 17 REFERENCE TABLE 17 BBBEER 78 3 18 REFERENCE TABLE 18 METADATA CONFIGURATION PARAMETER NAMES eee ecce eese 78 4 DATA ACCESS LADEE EEEE reae o sve s sep vene vUa vod eV eo ae e UU U spa oven Cap E PUE 81 4 1 FILE NAMING CONVENTION ON GDACS eere esee sense tasses sons tn sees snus 81 4 2 OTHER DATA SOURCES RR 82 5 USING THE HISTORY SECTION OF THE ARGO NETCDF STRUCTURE 83 5 1 RECORDING INFORMATION ABOUT THE DELAYED MODE QC PROCESS eere eene eeenue 83 Argo data management User s manual O 5 2 RECORDING PROCESSING STAGES sseesesssesosssesocssesoossessesoossesoossessossocsoesoosoesoesoesoesoossessossessossosses 83 5 3 RECOR
9. that contains the pre deployment or launch information So for a float with one basic mission it will have missions 0 and 1 When there are multiple configurations the configuration from the first cycle has CONFIG MISSION NUMBER set to 1 Each subsequent configuration change will be recorded as additional entries in CONFIG MISSION NUMBER with the value increased sequentially by the integer one variables from mission 1 must be repeated in subsequent missions Floats with multiple configurations still record pre deployment or launch information in CONFIG MISSION NUMBER 0 Argo data management User s manual If the configuration parameters change but mirror a previous mission then that mission number should be re used In extremely complex cases where mission changes are unclear then a new mission number can be used for each cycle Users should be aware that the metafile will need to be rewritten each time a new mission number is added 2 4 6 2 Determining which mission applies to a particular float cycle Users are able to determine which mission applies to each cycle by looking at the CONFIG MISSION NUMBER N CYCLE variable located in the trajectory file see section 2 3 5 cycle information from the float in the Trajectory format version 3 0 section of this User s manual Mission 0 pre deployment or launch information CONFIG MISSION NUMBER In the above example there are 3 different floa
10. 2 2 21 08 2009 81 2 new graphic for float cycles description 82 2 3 add a firmware version to general information for profile 82 3 4 add a CYCLE STAGE in trajectory file 82 3 5 add CYCLE PHASE and cycle in trajectory file 82 4 3 general review of float characteristics 82 4 5 configuration parameters 82 4 8 metadata file version 2 3 82 6 technical data format 2 3 82 8 2 profile directory file format version 2 1 83 3 add BPHASE DOXY 3 3 remark on unit conversion of oxygen 56 2 GDAC files removal add a RAFOS positioning system add a note on qc flag and qc manual add a description of greylist use for users trajectory format move date creation and date update in the file information section 2 2 27 11 2009 51 1 Notice on file format change chapter added 1 2 User Obligations chapter added 81 3 Disclaimer chapter added 51 4 Further information sources and contact information chapter added 82 3 1 and 52 3 6 remove HISTORY2 dimension from trajectory format 82 3 2 move DATE CREATION and DATE UPDATE to General information on the trajectory file chapter 82 3 4 revisit PARAM and PARAM QC policy in real time delayed mode 82 5 4 CONFIGURATION PHASE REPETITION is removed from the configuration parameter chapter 52 5 4 new example with a graphic 52 8 2 Profile directory file format statement transition added 53 2 1 add a reference to quality control manual 3 11 add a
11. first complete cycle CYCLE NUMBER ADJUSTED FillValue 99999 int MEASUREMENT CODE N MEASUREMENT MEASUREMENT CODE long name Flag referring to a measurement event in the cycle MEASUREMENT CODE conventions Argo reference table 15 MEASUREMENT CODE FillValue 99999 float PARAM N MEASUREMENT PARAM long name lt gt PARAM standard name lt X gt PARAM FillValue X lt PARAM gt units lt X gt lt PARAM gt valid_min X lt PARAM gt valid_max X lt PARAM gt C_format lt X gt lt PARAM gt FORTRAN_ format lt X gt char lt PARAM gt _QC N_MEASUREMENT lt PARAM gt _QC long_name quality flag lt PARAM gt _QC conventions Argo reference table 2 lt PARAM gt _QC FillValue float lt gt USTED N_MEASUREMENT lt gt ADJUSTED long name lt X gt lt gt ADJUSTED standard name lt gt lt gt USTED _ FillValue X lt gt USTED units lt gt lt gt USTED valid_min X lt gt ADJUSTED valid max X lt gt ADJUSTED comment lt gt lt gt ADJUSTED C format lt X gt lt gt ADJUSTED FORTRAN format Position accuracy received from the positioning system The location classes from ARGOS are described in the reference table 5 A G indicates t
12. 00 00 00 UTC JULD conventions Relative julian days with decimal part as parts of the day JULD FillValue 999999 ULD axis JULD_STATUS char JULD STATUS N MEASUREMENT JULD_STATUS long_name Status of the date and time JULD STATUS conventions Argo reference table 19 JULD STATUS FillValue JULD QC char J ULD_QC N_ MEASUREMENT JULD_QC long_name Quality on date and time JULD QC conventions Argo reference table 2 ULD_QC FillValue JULD_ADJ USTED double JULD ADJUSTED N MEASUREMENT JULD ADJUSTED long name Adjusted julian day UTC of each measurement relative to REFERENCE DATE TIME JULD ADJUSTED standard name time JULD ADJUSTED units days since 1950 01 01 00 00 00 JULD_ADJ USTED conventions Relative julian days with decimal part as parts of the day JULD_ADJ USTED _ FillValue 999999 ULD axis char JULD ADJUSTED STATUS N MEASUREMENT JULD ADJUSTED ST ATUS JULD ADJUSTED STATUS long name Statu s of the JULD ADJUSTED date JULD ADJUSTED STATUS conventions Argo reference table 19 ULD ADJUSTED STATUS FillValue JULD ADJUSTED Q char C JULD ADJUSTED QC N MEASUREMENT JULD ADJUSTED QC long name Quality on adjusted date and time JULD ADJUSTED QC conventions Argo reference table 2 JULD ADJUSTED QC FillValue double LATITUDE N MEASUREMENT LATITUDE long name Latitude of each location LATITUDE s
13. 13 2 1 OVERVIEW OF THE FORMATS eene ense sense ta sts toss sns sees ses sens sesso isoo 13 22 PROFILE FORMAT VERSION 30 14 22 dative ta ae ne a US 14 222 DIMENSTONS 15 2 2 3 GENERAL INFORMATION ON THE PROFILE nenne 15 2 2 4 GENERAL INFORMATION FOR EACH PROFILE esent 16 2 2 5 MEASUREMENTS FOR EACH PROFILE scssssscssesiesssssssccsssavansavestessesstuaccenascncsscssaansnssucasessesecsacesense 19 2 2 6 CALIBRATION INFORMATION FOR EACH PROFILE eese eene nnne nennen 21 22 7 HISTORY INFORMATION FOR BACH PROFILE 1 tekst eth ere 21 24 2 3 1 25 2 3 2 DIMENSIONS AND DEFINITIONS 25 2 3 3 GENERAL INFORMATION ON THE TRAJECTORY PILE 26 2 3 4 GENERAL INFORMATION ON THE BLOAT tb Ln Lee aHa E Dk ERE RUIN Eb nta 27 2 3 5 N MEASUREMENT DIMENSION VARIABLE GROUP eerte erret enne 28 2 3 6 N CYCLE DIMENSION VARIABLE GROUP iia pits ba RO RUE 32 Argo data management User s manual ee 2 3 1 HISTORY INFORMATION iiid erede nai e Oa eai id nas 3
14. An Argo single cycle profile file contains a set of profiles from a single cycle The minimum number is one profile per cycle There is no defined maximum number of profiles per cycle A profile contains all parameters that are measured with the same vertical sampling scheme and at the For example all Argo floats collect at least one profile per cycle that contains the CTD measurements Some speciality floats collect additional profiles per cycle These speciality profiles contain parameters measured at pressure levels that are different from the CTD levels Some examples of speciality profiles with different vertical sampling schemes are e Bouncing profiles a series of shallow profiles performed during one cycle e High resolution near surface observations higher resolution vertical sampling near the surface from unpumped CTD e Oxygen profiles dissolved oxygen measured on vertical levels that are not the CTD levels Optical profiles a series of optical profiles performed during one cycle For single cycle profile file naming conventions see 4 1 2 2 1 Global attributes The global attributes section is used for data discovery The following 9 global attributes should appear in the global section The NetCDF Climate and Forecast CF Metadata Conventions version 1 6 5 December 2011 are available from e http cf pcmdi lInl gov documents cf conventions 1 6 cf conventions pdf global attributes title
15. Argo float vertical profile institution CSIRO source Argo float history 2011 04 22T06 00 00Z creation references http www argodatamgt org Documentation comment free text user manual version 3 03 Conventions Argo 3 0 CF 1 6 featureType trajectoryProfile Global attribute Definition Title A succinct description of what is in the dataset Institution Specifies where the original data was produced Source The method of production of the original data If it was model generated source should name the model and its version as specifically as could be useful If it is observational source should characterize it e g surface observation or radiosonde Argo data management User s manual as History Provides an audit trail for modifications to the original data Well behaved generic netCDF filters will automatically append their name and the parameters with which they were invoked to the global history attribute of an input netCDF file We recommend that each line begin with a timestamp indicating the date and time of day that the program was executed references Published or web based references that describe the data or methods used to produce it Comment Miscellaneous information about the data or methods used to produce it 2 2 2 Dimensions Name Value Definition DATE_TIME DATE_TIME 14 This
16. HISTORY STEP ARSQ Selected from the list in reference table 12 HISTORY SOFTWARE WJO This is a locally defined name for the delayed mode QC rocess employed HISTORY SOFTWARE RELEASE 1 This is a locally defined indicator that identifies what version of the QC software is being used HISTORY REFERENCE WOD2001 This is a locally defined name for the reference database used for the delayed mode QC process HISTORY DATE 2003080500000 The year month day hour minute second that the process 0 ran HISTORY ACTION IP Selected from the list in reference table 7 HISTORY PARAMETER FillValue This field does not apply 1 HISTORY START PRES FillValue This field does not apply HISTORY STOP PRES FillValue This field does not apply HISTORY PREVIOUS VALUE FillValue This field does not apply HISTORY QCTEST FillValue This field does not apply Note 1 The present version of delayed mode QC only tests salinity and as such it is tempting to place PSAL in the PARAMETER field In future delayed mode QC tests may include tests for temperature pressure and perhaps other parameters For this reason simply addressing the software and version number will tell users what parameters have been tested 5 2 Recording processing stages Each entry to record the processing stages has a similar form An example is provided to show how this is done Note that reference table 12 contains the present list of processing stages and there should be at least on
17. Julian day UTC when float transitions to its Park or Drift mission This variable is based on float logic based on a descent timer i e SOLO or be based on measurements of pressure i e Provor Example 18833 8013889885 July 25 2001 19 14 00 Status flag on JULD date and time The flag scale is described in reference table 19 Example 2 Value is transmitted by the float Julian day UTC when float exits from its Park or Drift mission It may next rise to the surface AST or sink to profile depth DDET Example 18833 8013889885 July 25 2001 19 14 00 Status flag on JULD date and time The flag scale is described in reference table 19 Example 2 Value is transmitted by the float Argo data management User s manual JULD_DEEP_DESCENT_ END JULD_DEEP_DESCENT_ END STATUS JULD DEEP PARK STA RT DEEP PARK START STATUS JULD ASCENT START ASCENT START STATUS JULD DEEP ASCENT S TART double JULD DEEP DESCENT END N CYCLE JULD DEEP DESCENT END long name Deep Descent end date of the cycle JULD DEEP DESCENT END standard n ame time JULD DEEP DESCENT END units days since 1950 01 01 00 00 00 UTC JULD DEEP DESCENT END convention S Relative julian days with decimal part as part of day JULD DEEP DESCENT END FillValue 999999 char JULD DEEP DESCENT END STATUS N CYCLE JULD DEEP DESCENT END STATUS c onventions Argo reference table 1
18. QC FillValue Global quality flag on the PARAM profile PARAM is among the STATION PARAMETERS The overall flag is set to indicate the percentage of good data in the profile as described in reference table 2a Example PROFILE TEMP the temperature profile contains only good values PROFILE PSAL QC the salinity profile contains 5096 to 7596 good values VERTICAL SAMPLING SC HEME prse char VERTICAL SAMPLING SCHEME N PROF STRING256 VERTICAL SAMPLING SCHEME long name Vertical sampling scheme VERTICAL SAMPLING SCHEME conventions Argo reference table 16 VERTICAL SAMPLING SCHEME FillValue This variable is mandatory Use vertical sampling scheme to differentiate and identify profiles from a single cycle with different vertical sampling schemes leben i Argo data management User s manual 2 2 5 Measurements for each profile This section contains information on each level of each profile Each variable in this section has a N_PROF number of profiles N LEVELS number of pressure levels dimension lt gt contains the raw values telemetered from the floats The values in lt gt should never be altered lt PARAM_QC gt contains qc flags that pertain to the values in lt gt Values in lt QC are set initially in R and modes by the automatic real time tests They are later
19. These constitute the delayed mode data The adjustments applied to delayed data may also be applied to real time data to correct sensor drifts for real time users However these real time adjustments will be recalculated by the delayed mode quality control Argo data management User s manual 1 2 Formats description 2 1 Overview of the formats Argo data formats are based on NetCDF from UNIDATA NetCDF network Common Data Form is an interface for array oriented data access and a library that provides an implementation of the interface The NetCDF library also defines a machine independent format for representing scientific data Together the interface library and format support the creation access and sharing of scientific data The NetCDF software was developed at the Unidata Program Centre in Boulder Colorado The freely available source can be obtained as a compressed tar file or a zip file from Unidata or from other mirror sites e Ucar web site address http www ucar edu ucar NetCDF documentation http www unidata ucar edu packages netcdf index html Argo formats are divided in 4 sections Dimensions and definitions General information Data section History section The Argo NetCDF formats do not contain any global attribute Argo date and time all date and time have to be given in Universal Time coordinates Argo data management User s manual 2 2 Profile format version 3 0
20. UTC of creation of this DATE CREATION long name Date of file creation file DATE CREATION conventions YYYYMMDDHHMISS Format YYYYMMDDHHMISS DATE CREATION FillValue Example 20011229161700 December 29 2001 16 17 00 DATE_UPDATE char DATE UPDATE DATE TIME Date and time UTC of update of this DATE UPDATE long name Date of update of this file file Format YYYYMMDDHHMISS DATE UPDATE conventions YYYYMMDDHHMISS Example DATE UPDATE FillValue 20011230090500 December 30 2001 09 05 00 2 2 4 General information for each profile This section contains general information on each profile Each item of this section has a N PROF number of profiles dimension Name PLATFORM_NUMBER Definition char PLATFORM_NUMBER N_PROF STRING8 PLATFORM NUMBER long name Float unique identifier PLATFORM NUMBER conventions WMO float identifier PLATFORM NUMBER FillValue Comment WMO float identifier WMO is the World Meteorological Organization This platform number is unique Example 6900045 PROJECT NAME char PROJECT NAME N PROF STRING64 PROJECT NAME long name Name of the project PROJECT NAME FillValue Name of the project which operates the profiling float that performed the profile Example GYROSCOPE EU project for ARGO program NAME char PI NAME PROF STRING64 PI NAME long name Name
21. from the surface or from a deep profile This Note Float may approach drift pressure variable is based on pressure only and can be from above or below measured or estimated by fall rate In the case of a float that overshoots the drift pressure on descent DET is the time of the overshoot PST Park Start JULD PARK START Time when float transitions to its Park or Drift Time JULD PARK START STATUS mission This variable is based on float logic based on a descent timer i e SOLO or be based on measurements of pressure i e Provor Note on DET and PST DET and PST might be near in time or hours apart depending on float model and cycle to cycle variability Pl has judgment call whether DET PST PET Park End Time JULD PARK END Time when float exits from its Park or Drift JULD PARK END STATUS mission It may next rise to the surface AST or sink to profile depth DDET Deep Descent JULD DEEP DESCENT END Time when float first approaches within 396 of the End Time JULD DEEP DESCENT END eventual deep drift profile pressure This variable STATUS is based on pressure only and can be measured or estimated by fall rate DPST Deep Park JULD DEEP PARK START Time when float transitions to a deep park drift Start Time JULD DEEP PARK START mission This variable is only defined if the float STATUS enters a deep drift phase i e DPST not defined in cases of constant deep pressure due to bottom
22. in the code column of reference table 3 X these fields are specified in the columns of the reference table 3 Quality flag applied on each lt PARAM gt values The flag scale is specified in table 2 lt PARAM gt _ADJ USTED contains the adjusted values derived from the original values of the parameter X these fields are specified in the columns of the reference table 3 lt PARAM gt _ADJUSTED is mandatory When no adjustment is performed the FillValue is inserted Argo data management User s manual lt gt lt gt X lt PARAM gt _ADJUSTE char lt PARAM gt _ADJ USTED_QC N_MEASUREMENT lt gt ADJUSTED QC long name quality flag lt PARAM gt _ADJ USTED_QC conventions Argo reference table 2 lt PARAM gt _ADJUSTED QC FillValue lt PARAM gt _ADJUSTE float D_ERROR lt gt USTED_ERROR N_MEASUREM lt gt USTED_ERROR long_name Contains the error on adjusted values as determined by the delayed mode QC process lt PARAM gt _ADJ FillValue lt X gt lt PARAM gt _ADJ USTED_ERROR units lt gt lt gt USTED_ERROR C_format lt gt lt PARAM gt _ADJ USTED_ERROR FORTRAN_for mat lt X gt lt gt USTED_ERROR resolution lt X gt float AXES ERROR ELLIPSE MAJOR N MEASUREM ENT AXES ER
23. or if additional cycles are recovered in delayed mode the CYCLE NUMBER INDEX ADJUSTED variable is adjusted accordingly CYCLE NUMBER INDEX always corresponds to the profile cycle number To look for the cycle that matches the profile cycle number users must look in the CYCLE NUMBER INDEX variable for the cycle number they are interested in If the CYCLE NUMBER INDEX ADJUSTED variable contains FillValue then this cycle is in real time mode and no corrected cycle number exists If the CYCLE NUMBER INDEX ADJUSTED variable is filled this is the correct cycle number as determined during delayed mode When a cycle is missing e g no data received no fill values are used to indicate a missing cycle Definition Comment JULD DESCENT START double Julian day UTC when float leaves the surface and begins JULD DESCENT START N CYCLE descent Example JULD DESCENT START long name 18833 8013889885 July 25 2001 19 14 00 Descent start date of the cycle JULD DESCENT START standard nam e time JULD DESCENT START units days since 1950 01 01 00 00 00 UTC JULD DESCENT START conventions Relative julian days with decimal part as part of JULD DESCENT START FillValue 999 999 JULD DESCENT START char Status flag on J ULD date and time STATUS JULD DESCENT START STATUS N CY The flag scale is described in reference table 19 CLE Example JULD DESCENT START STATUS conve 2 Value is transmitted by the float ntions
24. 14 for standard technical parameter names TECHNICAL PARAMETER VALUE char TECHNICAL PARAMETER VALUE N TEC H PARAM STRING128 TECHNICAL PARAMETER VALUE long n ame Value of technical parameter TECHNICAL PARAMETER VALUE FillVal ue Value of the technical parameter Example 125049 CYCLE_NUMBER int CYCLE NUMBER N TECH PARAM CYCLE NUMBER long name Float cycle number CYCLE_NUMBER conventions 0 N 0 launch cycle if exists 1 first complete cycle CYCLE_NUMBER FillValue 99999 Cycle number of the technical parameter Example 157 2 6 GDAC FTP directory file format 2 6 1 Profile directory file format The profile directory file describes all individual profile files of the GDAC ftp site Its format is an autodescriptive Ascii with comma separated values The directory file contains e A header with a list of general informations title description project name format version date of update ftp root addresses GDAC node e table with a description of each file of the GDAC ftp site This table is a comma separated list Argo data management User s manual 56 Profile directory format definition Title Profile directory file of the Argo Global Data Assembly Center Description The directory file describes all individual profile files of the argo GDAC ftp site Project ARGO Format version 2 0 Date of update YYYYMMDDHHMISS F
25. 5 1 GLOBAL ATTRIBUTES ask coves PAARE ES AEREE EE URN 53 2 5 2 DIMENSIONS AND DEFINITIONS peenise nnise entere enses erst tese tesi 54 2 5 3 GENERAL INFORMATION ON THE TECHNICAL DATA cerent 54 2 9 4 TECHNICAL DATA eee Tues nee ret 55 2 6 GDACFTP DIRECTORY FILE FORMAT ee ecce eese seen senos ense ense toes sesso sete sense ease eaae eaae eaae ea 55 2 6 1 PROFILE DIRECTORY FILE 55 2 6 2 PROFILE DIRECTORY FILE FORMAT VERSION 2 1 56 2 6 3 TRAJECTORY DIRECTORY FORMAT ccsccssssesscescesssecsecssecssccssecsaecsseceaecseeeseceaeseseeeseeesaeesseesaees 58 2 6 4 META DATA DIRECTORY FORMAT ccsscesssesssesscesssesseessccssecssecsaecsseceaecesseeseecseeeseceaaceaaecsaecsaees 59 3 REFERENCE 1 ccdssecdsdssecseastenscccddssscsutsessesttecssdstssssssbessceudverees 60 3 1 REFERENCE TABLE 1 DATA 60 3 2 REFERENCE TABLE 2 ARGO QUALITY CONTROL FLAG SCALE ccccssssscccssssccecsssccecssssccecsszses 60 3 2 1 REFERENCE TABLE 2 MEASUREMENT FLAG SCALE s ccssesssessseeseeesseessessecessceseseseeeeeeesseeeasensees 60 Argo data management User s manual s 3 2 20 REFERENCE TABLE 2A PROFILE QUALITY FLAG tren t
26. Example 20011229161700 December 29 2001 16 17 00 Date and time UTC of update of this file Format YYYYMMDDHHMISS Example 20011230090500 December 30 2001 09 05 00 Argo data management User s manual 2 3 4 General information on the float This section contains general information on the float PLATFORM_NUMBER PROJECT NAME NAME TRAJECTORY PARAMETERS DATA CENTRE DATA STATE INDICATOR FLOAT SERIAL NO FIRMWARE VERSION WMO INST TYPE POSITIONING SYSTEM Definition char PLATFORM NUMBER STRI NG8 PLATFORM NUMBER long name Float unique identifier PLATFORM NUMBER conventions WMO float identifier A9111 PLATFORM NUMBER FillValue char PROJECT NAME STRING64 PROJECT NAME long name Name of the project PROJECT NAME FillValue char Pl NAME STRING64 PI NAME long name Name of the principal investigator PI NAME FillValue char TRAJECTORY PARAMETERS N PARAM S TRING16 TRAJECTORY_PARAMETERS long_name List of available parameters for the station TRAJECTORY PARAMETERS conventions Argo reference table 3 TRAJECTORY PARAMETERS FillValue char DATA CENTRE STRING2 DATA CENTRE long name Data centre in charge of float data processing DATA CENTRE conventions Argo reference table 4 DATA CENTRE FillValue char DATA STATE INDICATOR STRING4 DATA STATE INDICATOR long name Degree of processi
27. HISTORY_INSTITUTION N_HISTORY STRING4 Comment Institution that performed the action Institution codes are described in reference table 4 HISTORY_INSTITUTION long_name Institution which performed Example ME for MEDS action HISTORY_INSTITUTION conventions Argo reference table 4 HISTORY_INSTITUTION _FillValue 1 Argo data management User s manual HISTORY_STEP char HISTORY STEP N HISTORY Code of the step in data processing for this history STRINGA record The step codes are described in reference HISTORY STEP long name Step table 12 in data processing Example HISTORY STEP conventions Argo Automatic QC of data reported in real time reference table 12 has been performed HISTORY STEP FillValue HISTORY SOFTWARE char HISTORY SOFTWARE Name of the software that performed the action HISTORY STRING4 This code is institution dependent HISTORY SOFTWARE long name Example OW Name of software which performed action HISTORY SOFTWARE conventions Institution dependent HISTORY SOFTWARE FillValue HISTORY_SOFTWARE_RELEASE char HISTORY_SOFTWARE_RELEASE Version of the software N_HISTORY STRING4 This name is institution dependent HISTORY SOFTWARE RELEASE long Example 1 0 name Version release of software which performed action HISTORY SOFTWARE RELEASE conv entions Institution dependent HISTORY SOFTWARE RE
28. Impossible Location test 4 16 Position on Land test 5 32 Impossible Speed test 6 64 Global Range test 7 128 Regional Global Parameter test 8 256 Pressure Increasing test 9 512 Spike test 10 1024 Top and Bottom Spike test obsolete 11 2048 Gradient test 12 4096 Digit Rollover test 13 8192 Stuck Value test 14 16384 Density Inversion test 15 32768 Grey List test 16 65536 Gross Salinity or Temperature Sensor Drift test Argo data management User s manual 17 131072 Visual test 18 261144 Frozen profile test 19 524288 Deepest pressure test 20 1044576 Questionable Argos position test Argo data management User s manual 3 12 Reference table 12 history steps codes ARFM Convert raw data from telecommunications system to a processing format ARGQ Automatic QC of data reported in real time has been performed 1603 Checking for duplicates has been performed ARSQ Delayed mode QC has been performed ARCA Calibration has been performed ARUP Real time data have been archived locally and sent to GDACs ARDU Delayed data have been archived locally and sent to GDACs RFMT Reformat software to convert hexadecimal format reported by the buoy to our standard format COOA Coriolis objective analysis performed If individual centres wish to record other codes they may add to this list as they feel is appropriate 3 13 Reference table 13 ocean code
29. J ULD_ADJ USTED date and time The flag scale is described in the reference table 2 Example 1 the date and time seems correct Latitude of the location or measurement Unit degree north Example 44 4991 for 44 29 56 76 N Longitude of the location or measurement Unit degree east Example 16 7222 for 16 43 19 92 E Argo data management User s manual POSITION_ACCURA POSITION QC B CYCLE NUMBER AD JUSTED MEASUREMENT CO DE lt PARAM gt lt PARAM gt _QC lt gt ADJUSTE D LONGITUDE FillValue 99999 LONGITUDE valid min 180 LONGITUDE valid max 180 LONGITUDE axis X char POSITION ACCURACY N MEASUREMENT POSITION ACCURACY long Estimated accuracy in latitude and longitude POSITION ACCURACY conventions Argo reference table 5 POSITION ACCURACY FillValue char POSITION QC N MEASUREMENT POSITION QC long name Quality on position POSITION QC conventions Argo reference table 2 POSITION QC FillValue int CYCLE NUMBER N MEASUREMENT CYCLE NUMBER long name Float cycle number of the measurement CYCLE NUMBER conventions 0 N 0 launch cycle 1 first complete cycle CYCLE NUMBER FillValue 99999 int CYCLE NUMBER ADJUSTED N MEASUREMENT CYCLE NUMBER ADJUSTED long name Adjusted float cycle number of the measurement CYCLE NUMBER ADJUSTED conventions 0 0 launch cycle 1
30. JULD_PARK_START long_name Drift start date of the cycle JULD_PARK_START standard_name time JULD PARK START units days since 1950 01 01 00 00 00 UTC JULD PARK START conventions Relative julian days with decimal part as part of day JULD PARK START FillValue 999999 JULD PARK START ST char ATUS JULD PARK START STATUS N CYCLE JULD PARK START STATUS conventio ns Argo reference table 19 JULD PARK START STATUS FillValue JULD_PARK_END double JULD PARK END N CYCLE JULD PARK END long name Drift end date of the cycle JULD PARK END standard name time JULD PARK END units days since 1950 01 01 00 00 00 UTC JULD PARK END conventions Relative julian days with decimal part as part of day ULD PARK END FillValue 999999 JULD PARK END STAT char US JULD PARK END STATUS N CYCLE JULD PARK END STATUS conventions Argo reference table 19 JULD PARK END STATUS FillValue ou D Status flag on JULD date and time The flag scale is described in reference table 19 Example 2 Value is transmitted by the float Julian day UTC when float first approaches within 396 of the eventual drift pressure Float may be transitioning from the surface or from a deep profile Example 18833 8013889885 July 25 2001 19 14 00 Status flag on JULD date and time The flag scale is described in reference table 19 Example 2 Value is transmitted by the float
31. Primary sampling averaged 2 dbar bin average N PROF 2 Secondary sampling discrete 1 1 Hz CTD data discrete DOXY N_PROF 3 Near surface sampling discrete unpumped auxiliary CTD 3 17 Reference table 17 obsolete This table has been removed 3 18 Reference table 18 metadata configuration parameter names metadata variable names and configuration parameter names are standardized The list of metadata variable names is available at e http www argodatamgt org Documentation under Argo Metadata Files Metadata variable names Argo data management User s manual The list of configuration parameter names is available at http www argodatamgt org Documentation under Argo Metadata Files Configuration parameter names If new names are required as new variables are reported by a float they must be added to this table before they will be accepted Please note that in this scheme configuration parameter values are stored as numerals and therefore any parameters with logical or string input will require an equivalent numeric code to be added to the Explanation section of the Configuration parameter names table Request for new names can be sent to argo dm chairman jcommops org for approval and inclusion flag Meaning ue is estimated from pre deployment information found in the metadata Value is estimated using information not transmitted by the float or by proce
32. descripion of table11 Add a new column in the table to explain the link between QC test binary ID and test number 53 14 table 14 technical parameter names revision links to naming convention and list of technical parameters added 56 1 1 Greylist definition chapter added 6 1 1 Who when how to add a float in the greylist 56 1 1 Who when how to remove floats from the greylist 86 1 1 How users should use the greylist 2 2 31 12 2009 81 3 Disclaimer argo data are continuously managed and updated 82 3 4 Trajectory locations and measurements Remove DC REFERENCE Do not report DATA MODE in this section report CYCLE NUMBER in this section 52 3 5 Trajectory cycle information from the float Missing cycle management Report DATA MODE in this section 53 2 1 Reference table 2 measurement flag scale For flag 2 comment is Treat as good data instead of Probably good data 53 3 2 Oxygen data management 53 14 Reference table 14 technical parameter names How to require new technical parameters 2 2 08 01 2010 Address the following messages listed and commented in argo user manual comment toulouse doc 04 01 2010 22 32 Annie Wong 31 12 2009 22 49 Claudia Schmid 31 12 2009 20 35 Claudia Schmid 31 12 2009 19 12 Annie Wong 2 31 08 09 2010 T Carval CONCENT_DOXY is renamed MOLAR DOXY to be compliant with the document Processing Argo OXYGEN data at the DAC level version 1 0 2 31 14 06 2011 T
33. done in delayed mode In addition to locations and cycle timing information a trajectory file often contains measurements such as pressure temperature salinity or conductivity performed at various times during the cycle The full pressure temperature and salinity profile collected upon ascent is not included in the trajectory file This is stored in the profile file There will be up to two possible trajectory files at one time for a float a real time trajectory file and a delayed mode trajectory file D For naming conventions see 4 1 The real time trajectory file will contain all the data obtained in real time for all the cycles the float has performed The R file will exist until the float dies and a delayed mode trajectory file exists for the entire float lifetime The delayed mode trajectory file will contain both real time and delayed mode data The delayed mode data will be the highest quality data available for each cycle that has been delayed mode quality controlled However delayed mode quality control may not be performed on all the float s cycles In this case the D file will contain both the real time and delayed mode data only for the cycles for which delayed mode quality control has been performed Therefore if both an R and D trajectory file exist to obtain the best quality data for the entire float record one must look at the D file for the cycles that have been delayed mode quality controlled and then in
34. equivalent numeric flags must also be added to the table by the proposer of the new configuration parameter All parameter names are standardized and are available in reference table 18 The mission is used to record information that changes from cycle to cycle for instance when a float changes its mission from 3 shallow profiles to 1 deep profile The shallow and deep profiles will have different mission numbers The value of the mission number is recorded in CONFIG MISSION NUMBER Mission parameters are pre deployment or launch instructions They are configuration parameters that are configured but not changeable and are therefore designated mission 0 so that they are clearly differentiated from the other mission variables that may change during the float lifetime The parameter CONFIG MISSION COMMBENT can be used to store information about mission or whether the mission was set pre deployment or transmitted by the float free form field 2 4 6 1 Note on floats with multiple configurations Typically an Argo float configuration is valid for the whole life of the float Each cycle is repeated with the same behaviour one configuration However some floats may be configured to change their behaviour from cycle to cycle multiple configurations When there is only one configuration CONFIG MISSION NUMBER is set to 1 all the cycles are programmed to be the same Note that in this case floats will still have mission 0
35. hertz TRANS FREQUENCY FillValue char POSITIONING SYSTEM N POSITIONING SYSTEM STRINGS POSITIONING SYSTEM long name Positioning system POSITIONING SYSTEM FillValue char PLATFORM_FAMILY STRING256 PLATFORM_FAMILY long_name Category of instrument PLATFORM FAMILY FillValue char PLATFORM_TYPE STRING32 PLATFORM_TYPE long_name Type of float PLATFORM TYPE FillValue char PLATFORM MAKER STRING256 PLATFORM MAKER long name Fhe nName of the manufacturer PLATFORM MAKER FillValue char FIRMWARE VERSION STRING16 FIRMWARE VERSION long name Fhe fFirmware version for the float FIRMWARE VERSION FillValue char MANUAL VERSI ON STRI NG16 MANUAL VERSION long name Fhe mManual version for the float MANUAL VERSION FillValue char FLOAT SERIAL NO STRING16 long name Serial number of the float FLOAT SERIAL NO FillValue char STANDARD FORMAT ID STRINGI16 STANDARD FORMAT ID long name A sStandard format number to describe the data format type for each float STANDARD FORMAT 10 FillValue char DAC FORMAT ID STRING16 DAC FORMAT ID long name Fhe Format number used by the DAC to describe the data format type for each float DAC FORMAT ID FillValue Name of the telecommunication system from reference table 10 Example ARGOS Frequency of transmission from the float Unit hertz Example 1
36. modified in D mode at levels where the qc flags are set incorrectly by the real time procedures and where erroneous data are not detected by the real time procedures Each parameter can be adjusted in delayed mode but also in real time if appropriate In that case lt PARAM gt _ADJUSTED contains the adjusted values lt PARAM gt _ADJUSTED_QC contains the QC flags set by the adjustment process and lt gt ADJUSTED ERROR contains the adjustment uncertainties A real time data file with no adjusted data has an adjusted section with fill values lt PARAM gt _ADJUSTED lt gt ADJUSTED QC and PARAM ADJUSTED ERROR The Argo profile delayed mode QC is described in Argo quality control manual by Annie Wong et Al Name Definition Comment lt PARAM gt float lt PARAM gt N_PROF N_LEVELS lt PARAM gt contains the original values lt PARAM gt long_name lt X gt of a parameter listed in reference table lt PARAM gt standard_name lt X gt 3 PARAM FillValue X X this field is specified in the lt PARAM gt units lt X gt reference table 3 lt PARAM gt valid_min X lt PARAM gt valid_max X lt PARAM gt C_format lt X gt lt PARAM gt FORTRAN_format lt gt lt PARAM gt resolution X lt PARAM gt _QC char lt PARAM gt _QC N_PROF N_LEVELS Quality flag applied on each lt PARAM gt lt PARAM gt _QC long_name quality flag valu
37. s manual 75 i e Provor NINJA Time JULD PARK START 251 275 unassigned Reserved for specific timing events around PST 276 299 see above Any measurement recorded during table transition towards PET 301 Representative Park lt PARAM gt found either from measurements taken during drift or from metafile information EPOR 3 around PET pce cp Ne table transition towards DDET 401 425 unassigned Reserved for specific timing events around DDET 426 449 see above Any measurement recorded during table transition towards DPST DPST All measurements made at time when float transitions to a deep park drift mission This variable is only defined if the float enters a deep drift phase i e DPST not defined in cases of constant deep pressure due to bottom hits or buoyancy issues 451 475 unassigned Reserved for specific timing events around DPST 476 499 see above Any measurement recorded during table transition towards AST down time parameter reported by APEX floats rl gt by APEX floats 505 Deepest bin reached during ascending Argo data management User s manual 504 525 unassigned Reserved for specific timing events around AST 526 549 see above Any measurement recorded during table transition towards DAST DAST All measurements made at the Time start of the float s ascent from Deep SOLO II profile pressure to drift pressure Used for fl
38. the file for the rest of the cycles which have not yet been delayed mode quality controlled Once a float dies and the entire float record has been quality controlled the D file will be the only file available on the GDAC and will contain both adjusted and not adjusted data The trajectory file contains two groups of data variables In this document the groups are differentiated by their dimension The variable group described in 1 1 5 which includes the locations cycle timing information and measurements from the float is N MEASUREMENT long It includes all the raw data from the float and there is no complimentary variable in the N CYCLE variable group If filled the best timing information is kept in the JULD_ADJUSTED variable If this is filled in real time that means either clock drift has been determined and adjustment has been applied inclusive of adjustment of zero or another timing estimate has been done based on typical float behavior Simultaneously the DATA MODE should be marked as A indicating an adjusted float and the CLOCK OFFSET variable should be appropriately filled The variable group described in 1 1 6 which includes the cycle timing information is N CYCLE long This array includes the best timing information which matches if filled the JULD ADJUSTED times in the N MEASUREMENT array else it matches the JULD N MEASUREMENT variable The times can be corrected for float clock drift or estimated The JULD STATUS
39. this float which does not achieve any measurement during the drift phase Argo data management User s manual 4 Data access The whole Argo data set is available in real time and delayed mode from the global data centres GDACs The internet addresses are e http www usgodae org argo argo html e http www argodatamgt org The FTP addresses are e ftp usgodae1 fnmoc navy mil pub outgoing argo ftp ftp ifremer fr ifremer argo The 2 GDACs offer the same data set that is mirrored in real time More on GDACs organization e http www argodatamgt org Media Argo Data Management Argo Documentation General documentation GDAC organisation 4 1 File naming convention on GDACs The GADC ftp sites comply with the following naming conventions Profile data For floats that collect no more than 1 ascending and 1 descending profile per cycle the file names for individual profiles are lt R D gt lt FloatID gt _ lt XXX gt lt D gt nc where the initial indicates Real Time data the initial D indicates Delayed Mode data XXX is the cycle number the second D indicates a descending profile profiles without this D are collected during ascent For floats that collect 2 or more ascending or descending profiles per cycle the file names for individual profiles are lt R D gt lt FloatID gt _ lt XXX gt lt D gt lt _YY gt nc where the initial indicates Real Time data the initial D indicates Delaye
40. to what constitutes original or raw data Despite the fact that an instrument may be capable of high sampling rates what is reported from the instrument defines what is considered raw For example Argo floats can certainly sample at finer scales than every 10 db but because of communications all we see for now is data at that or worse vertical resolution Therefore the data coming from the instrument is raw output at 1Odb resolution 2 Theconversion of the raw data stream from the communications system into profiles of variables causes the data state indicator to switch from level 0 to 1 3 Even though the data at global data centres use manual or semi automated QC procedures there is often not the intercomparisons to larger data collections and fields that would qualify the data state indicator to be set to class C This is generally only provided by scientific scrutiny of the data Argo data management User s manual 66 4 The transition from class 2 to 3 occurs when assumptions of scales of variability are applied During the course of normal data processing it is common to carry out some averaging and subsampling This is usually done to exploit oversampling by the instrument and to ensure good measurements are achieved These are considered to be part of the geospatial and temporal referencing process 3 7 Reference table 7 history action codes Code Meaning CF Change
41. user to check that the file he collected through FTP is identical to the original file Index file naming convention etc argo profile detailled index txt gz e etc argo profile detailled index txt gz md5 Detailed profile directory format definition Title Profile directory file of the Argo Global Data Assembly Center Description The directory file describes all individual profile files of the argo GDAC ftp site Project ARGO Format version 2 1 Date of update YYYYMMDDHHMISS FTP root number 1 ftp ftp ifremer fr ifremer argo dac FTP root number 2 ftp usgodae usgodae org pub outgoing argo dac GDAC node CORIOLIS file date latitude longitude ocean profiler type institution date update profile temp qc profile psal qc profile doxy qc ad psa adjustment mean ad psal adjustment deviation gdac date creation gdac date update n levels e file path and file name on the ftp site The file name contain the float number and the cycle number ill value none this field is mandatory date date of the profile YY YY MMDDHHMISS ill value blank atitude longitude location of the profile value 99999 Ocean code of the ocean of the profile as described in reference table 13 ill value blank F F F F profiler type type of profiling float as described in reference table 8 Fill value blank institution institution of the profiling float described in reference table 4 Fi
42. variables provide information on the state of the timing information The N CYCLE array also includes several variables that pertain only to the entire cycle such as GROUNDED CONFIG MISSION NUMBER etc In N MEASUREMENT group the MEASUREMENT CODE variable must be correctly understood This variable is designed to indicate where in the cycle the location times and measurements occur The Measurement Code Table Reference Table 15 contains all the flags and their meanings for the MEASUREMENT CODE variable This table is comprised of two parts a Absolute codes measurement code MC values can be primary mandatory or secondary highly desirable and b Relative codes measurement code values are relative to an absolute code and are Argo data management User s manual 5 further divided into two parts generic codes that can be used by a wide variety of floats and specific codes that are directly important to a specific float measurement All Primary and Secondary MC events that are experienced by the float are required to be present in the N MEASUREMENT array and redundantly in the N_CYCLE variables Secondary codes are codes that not as crucial as the primary codes but it is still recommended they be filled other codes are voluntary If the float experiences an event but the time is not able to be determined then most variables are set to fill value and a STATUS 9 is used in both the MEASUREMENT CYCL
43. 0 072 17 659 A 0845 AO 20030214155354 aoml 13857 13857_traj nc 0 543 19 622 A 0845 AO 20030214155619 jma 29051 29051 traj nc 32 280 30 280 143 238 140 238 846 A 20030212125117 jma 29051 29051 traj nc 32 352 30 057 143 206 140 115 846 JA 20030212125117 2 6 4 Meta data directory format The metadata directory file describes all metadata files of the GDAC ftp site Its format is an autodescriptive Ascii with comma separated values The directory file contains e A header with a list of general informations title description project name format version date of update ftp root addresses GDAC node e table with a description of each file of the GDAC ftp site This table is a comma separated list Metadata directory format definition Title Metadata directory file of the Argo Global Data Assembly Center Description The directory file describes all metadata files of the argo GDAC ftp site Project ARGO Format version 2 0 Date of update YYYYMMDDHHMISS FTP root number 1 ftp ftp ifremer fr ifremer argo dac FTP root number 2 ftp usgodae usgodae org pub outgoing argo dac GDAC node CORIOLIS file profiler type institution date update e path and file name on the ftp site Fill value none this field is mandatory profiler type type of profiling float as described in reference table 8 Fill value blank e institution institution of the profiling float described
44. 07 2013 83 3 remove the sensor names from oxygen related parameter s long name attributes 3 03 28 08 2013 52 4 2 add a STRING64 dimension 82 4 4 CONTROLLER BOARD SERIAL NO PRIMARY long name remove The 82 4 1 global attributes user manual version 3 03 3 03 30 08 2013 2 4 2 add a STRING32 dimension in definition column Argo data management User s manual 64 1 Introduction This document is the Argo data user s manual It contains the description of the formats and files produced by the Argo DACs 1 1 Notice on file format change transition This version of the User s manual is adjusting the file formats to the growing variety of floats and user needs It introduces a complete revision of metadata and technical files To cope with this radical change during a transition period the version 2 2 and 3 0 of the technical and metadata file will be valid among Argo data system 1 2 User Obligations A user of Argo data is expected to read and understand this manual and the documentation about the data contained in the attributes of the NetCDF data files as these contain essential information about data quality and accuracy A user should acknowledge use of Argo data in all publications and products where such data are used preferably with the following standard sentence These data were collected and made freely available by the international Argo project and the national programs that co
45. 1 17 28 34 19971217000000 December 17 1997 00 00 00 STRING64 STRING64 64 String dimensions from 2 to 64 STRING16 STRING16 16 Argo data management User s manual STRING8 STRING4 STRING2 STRING8 8 STRING4 4 STRING2 2 N PARAM N_PARAM lt int value gt Maximum number of parameters measured or calculated for a pressure sample Examples pressure temperature PARAM 2 pressure temperature salinity N PARAM 3 pressure temperature conductivity salinity N PARAM 4 N_MEASUREMENT N_MEASUREMENT This dimension is the number of recorded locations cycle timings and unlimited measurements of the file N_CYCLE N_CYCLE lt int Number of collected float cycles value gt If all the cycles have been collected i e if there are no missing cycles it is the number of cycles performed by the float In this particular case as some floats begin cycle numbering at 0 others at 1 in the former N_CYCLE max CYCLE_NUMBER 1 In the latter CYCLE2max CYCLE NUMBER Example CYCLE 100 Maximum number of history records for a location This dimension depends N HISTORY N HISTORY int value on the data set Example N HISTORY 10 2 3 3 General information on the trajectory file This section contains information about the whole file Name DATA_TYPE FORMAT_VERSION HANDBOOK_VERSION REFERENCE DATE TIME DATE CREATION DATE UPDATE Definition ch
46. 2002 Comments from version 0 9b are implemented 1 0 09 07 2002 Comments from version 0 9c are implemented 1 0a 31 12 2002 Missing values in trajectory and calibration 1 0a 17 01 2003 Description of directory file format 1 0a 24 01 2003 Update of reference tables 1 0a 24 01 2003 Update of measurements of each profile to handle corrected values 1 0a 24 01 2003 Increase the size of DC REFERENCE from STRING16 to STRING32 1 0b 17 03 2003 Replace corrected values with adjusted values 1 0b 29 04 2003 DC REFERENCE removed from trajectory format general information of the float section 1 0b 30 04 2003 Use blank fill values for character variables 1 0c 30 04 2003 Proposal submitted on 30 04 2003 1 0d 14 08 2003 Proposal submitted on 14 08 2003 green font 1 0e 23 10 2003 Proposal submitted on 12 11 2003 green font 2 0 12 11 2003 All comments from Argo user s manual comments ref ar dm 02 02 implemented General agreement from Argo data management meeting in Monterey Nov 5 7 2003 2 01 15 12 2003 History section updated 2 01 01 10 2004 Meta data section WMO INST TYPE added to history section INSTRUMENT TYPE renamed INST REFERENCE 2 01 10 11 2004 Reference table 2 quality control flag scale updated by Annie Wong 2 01 10 11 2004 Updates in reference table 3 parameter codes table DOXY TEMP DOXY TEMP use ITS 90 scale 2 01 23 11 2004 Reference table 14 instrument failure mode added by Annie Wong 2 01 25 02 2005 T
47. 4 HISTORY_STEP ARGQ Selected from the list in reference table 12 HISTORY_SOFTWARE FillValue This field does not apply HISTORY SOFTWARE RELEASE FillValue This field does not apply HISTORY REFERENCE FillValue This field does not apply HISTORY DATE 2003080500000 The year month day hour minute second that the process 0 ran HISTORY ACTION QCP Selected from the list in reference table 7 HISTORY PARAMETER FillValue This field does not apply HISTORY START PRES FillValue This field does not apply HISTORY STOP PRES FillValue This field does not apply HISTORY PREVIOUS VALUE FillValue This field does not apply HISTORY QCTEST 1 This is the result of all tests with IDs from 2 to 256 having Argo da ta management User s manual ss been applied see reference table 11 Record 2 Documenting the tests that failed Field Sample Explanation HISTORY INSTITUTION ME Selected from the list in reference table 4 HISTORY STEP ARGQ Selected from the list in reference table 12 HISTORY SOFTWARE FillValue This field does not apply HISTORY SOFTWARE RELEASE FillValue This field does not apply HISTORY REFERENCE FillValue This field does not apply HISTORY DATE 2003080500000 The year month day hour minute second that the process 0 ran HISTORY ACTION QCF Selected from the list in reference table 7 HISTORY PARAMETER FillValue This field does not apply HISTORY STA
48. 44 Position system from reference table 9 ARGOS or GPS are 2 positioning systems Example ARGOS Category of instrument Example Float POPS ITP Name of the manufacturer Example Webb Research Corporation The firmware version This is specified as per the format on the manufacturers manual Example 072804 The version date or number for the manual for each float Example 110610 or 004 This field should contain only the serial number of the float Example 1679 Argo data management User s manual WMO INST TYPE PROJECT NAME DATA CENTRE NAME ANOMALY BATTERY TYPE BATTERY PACKS CONTROLLER BOARD TY PE PRIMARY CONTROLLER BOARD TY PE SECONDARY CONTROLLER BOARD SE RIAL PRIMARY CONTROLLER BOARD SE RIAL SECONDARY SPECIAL FEATURES char WMO INST TYPE STRING4 WMO INST TYPE long name Coded instrument type WMO INST TYPE conventions Argo reference table 8 WMO INST TYPE FillValue char PROJECT NAME STRING64 PROJECT NAME long name Fhe pProgram under which the float was deployed PROJECT NAME FillValue char DATA CENTRE STRING2 DATA CENTRE long name Data centre in charge of float real time processing DATA CENTRE conventions Argo reference table 4 DATA CENTRE FillValue char PI NAME STRING64 PI NAME long name Name of the principal investigator NAME FillValue char ANOMALY STRING256 ANOMALY long na
49. 846 Webb Research float Seabird sensor Name of the project which operates the profiling float that performed the profile Example GYROSCOPE EU project for Argo program Code of the data centre in charge of the float data management The data centre codes are described in the reference table 4 Example ME for MEDS Name of the principal investigator in charge of the profiling float Example Yves Desaubies This field describes any anomaly or problem the float may have had Example the immersion drift is not stable Describes the type of battery packs in the float Example Alkaline Lithium or Alkaline and Lithium Describes the configuration of battery packs in the float number and type Example 4DD Li 1C Alk Describes the type of controller board Example APF8 APF9i Only applicable if there is more than one controller board in the float Describes the second type of controller board The serial number for the primary controller board Example 4567 Only applicable if there is more than one controller board in the float The serial number for the secondary controller board Example 4567 Additional float features can be specified here such as algorithms used by the float Ice Sensing Algorithm Interim Storage Algorithm grounding avoidance or additional hardware such as a compressee buoyancy compensator Example Argo data management User s manual REDEPLOYED FL
50. 9 JULD DEEP DESCENT END STATUS FillValue double JULD DEEP PARK START CYCLE JULD DEEP PARK START long name Deep Descent end date of the cycle JULD DEEP PARK START standard name time JULD DEEP PARK START units days since 1950 01 01 00 00 00 UTC JULD DEEP PARK START conventions Relative julian days with decimal part as part of day JULD DEEP PARK START FillValue 999999 charJULD DEEP PARK START STATUS N CYCLE JULD DEEP PARK START STATUS conventions Argo reference table 19 JULD DEEP PARK START STATUS FillValue double JULD ASCENT START N CYCLE JULD ASCENT START long name Start date of the ascent to the surface JULD ASCENT START standard name time JULD ASCENT START units days since 1950 01 01 00 00 00 UTC JULD ASCENT START conventions Relative julian days with decimal part as part of day JULD ASCENT START FillValue29999 99 char JULD ASCENT START STATUS N LE JULD ASCENT START STATUS conven tions Argo reference table 19 JULD ASCENT START STATUS FillVal 1 double JULD DEEP ASCENT START N CYCLE JULD DEEP ASCENT START long nam Julian day UTC when float first approaches within 396 of the eventual deep drift profile pressure Example 18833 8013889885 July 25 2001 19 14 00 Status flag on JULD date and time The flag scale is described in reference table 19 Example 2 Value i
51. 9 2 4 METADATA FORMAT VERSION 3 0 isscssscscsssscccensvssecsesssecsssoacscnscoseasoscscessestuteieesescasseessceseseszecestesee 42 24 1 GEOBAL A TIRIB TES hern ee sae nere ead et onus e en diano rede v EE ear d 42 2 4 2 DIMENSIONS AND DEFINITIONS eese nennen nnne tese tenete stern 42 2 4 5 GENERAL INFORMATION ON THE META DATA 43 244 BEOATCHARAGTERISTICS nittciteecsecs i cte iesi v e eee o eee pes ee ae ed e ed uen 43 2 4 5 FLOAT DEPLOYMENT AND MISSION INFORMATION ccssccsseesseesseessecseceseceseceseeeeeeeeeeeseseaeesaees 46 2 4 6 CONFIGURATION PARAMETERS cccssscssscesscesscesscessecsscessecssccsaecsaecsaecssesseesesesesesesseeaseesseesseensees 47 2 4 6 1 Note on floats with multiple configurations 00 0 ee ee esee 48 2 4 6 2 Determining which mission applies to a particular float 49 2 4 7 FLOAT SENSOR INFORMATION ccsccssscssscesscesscessecseccsecessccssccssecsaecssecssseseseeecesseeseeesaeesseeasceaeees 50 2 4 8 FLOAT CALIBRATION INFORMATION ccssscesssesssesceseecsecssecssecsaecsseceseceseceseseseseseeeaaeeaseesaeesaees 51 2 4 9 MANDATORY META DATA PARAMETERS csssesssesssesseecssecssessecsaecssecesecusecesscessseseeeseecasecsseenaees 52 2410 HIGHLY DESIRABLE METADATA 53 2 5 TECHNICAL INFORMATION FORMAT VERSION 3 0 cscssscssscsscssccssscssceccssccssecsssccssccsscsesscseseee 53 2
52. Argo data management ar um 02 01 ARGO USER S MANUAL Version 3 03 August 28 2013 5 E 6 E o 6 ARGO part of the integrated global observation strategy ARGO part of the integrated global observation strategy Argo data management User s manual Ref ar um 02 01 Ref ifremer cor do dti mut 02 084 Authors Thierry Carval Ifremer Bob Keeley MEDS Yasushi Takatsuki JAMSTEC Takashi Yoshida JMA Stephen Loch BODC Claudia Schmid AOML Roger Goldsmith WHOI Annie Wong UW Rebecca McCreadie BODC Ann Thresher CSIRO Anh Tran MEDS 3 Table of contents MB iS OLOH RI KOD E 10 1 1 NOTICE ON FILE FORMAT CHANGE TRANSITION cccscssssssssscecscccessccesccesssccccssccesccsssscersssceeoesee 10 1 2 USER OBLIGATIONS 10 1 5 DIOE IUIUS 10 1 4 FURTHER INFORMATION SOURCES AND CONTACT INFORMATION eee esee seen tests etas etus etn 10 1 5 ARGO PROGRAM DATA MANAGEMENT CONTEXT ee ee ee eese eee en esten sesta sesso setas see sees seen a 11 1 6 CYCLES e 11 1 7 REAL TIME AND DELAYED MODE DATA cscssssscssscccccccesccessccecssccccsccesccesssccecscceccccsescesssscersocsee 12 2 FORMATS DESCRIPTION xci choses kein a a ti dex ep ME A EL
53. Argo reference table 19 JULD DESCENT START STATUS FillV alue JULD_FIRST_STABILIZA double Julian day UTC of time when a float first becomes water TION JULD_FIRST_STABILIZATION N_CYCLE neutral Example 18833 8013889885 July 25 2001 19 14 00 JULD FIRST STABILIZATI ON long na me Time when a float first becomes water neutral JULD FIRST STABILIZATION standard _ time JULD FIRST STABILIZATI ON units days since 1950 01 01 00 00 00 UTC JULD FIRST STABILIZATI ON conventions Relative julian days Argo data management User s manual with decimal part as part of day JULD FIRST STABILIZATION FillValue 999999 JULD_FIRST_STABILIZA char TION_STATUS JULD_FIRST_STABILIZATION_STATUS N_CYCLE JULD_FIRST_STABILIZATION_STATUS conventions Argo reference table 19 JULD STABILIZATION STATUS FillVal JULD_DESCENT_END double JULD DESCENT END N CYCLE JULD DESCENT END long name Descent end date of the cycle JULD DESCENT END standard name time JULD DESCENT END units days since 1950 01 01 00 00 00 UTC JULD DESCENT END conventions Relative julian days with decimal part as part of day JULD DESCENT END FillValue 99999 9 JULD_DESCENT_END_S char TATUS JULD_DESCENT_END_STATUS N_CYCL E JULD DESCENT END STATUS conventi ons Argo reference table 19 JULD DESCENT END STATUS FillValu eas JULD_PARK_START double J ULD_PARK_START N_CYCLE
54. C FillValue float TEMP ADJUSTED N PROF N LEVELS TEMP ADJUSTED long name ADJ USTED SEA TEMPERATURE IN SITU 175 90 SCALE TEMP standard name sea water temperature TEMP ADJUSTED FillValue 99999 f TEMP ADJUSTED units degree Celsius TEMP ADJUSTED valid min 2 f TEMP ADJUSTED valid max 40 f TEMP ADJUSTED C format 9 3f TEMP ADJUSTED FORTRAN format F9 3 TEMP ADJUSTED resolution 0 001f char TEMP 5 QC N PROF LEVELS TEMP ADJUSTED QC long name quality flag TEMP ADJUSTED QC conventions Argo reference table 2 TEMP ADJUSTED QC FillValue float TEMP ADJUSTED ERROR N PROF N LEVELS TEMP ADJUSTED ERROR long name ERROR ON ADJUSTED SEA TEMPERATURE IN SITU ITS 90 SCALE TEMP ADJUSTED ERROR FillValue 99999 f TEMP ADJUSTED ERROR units degree Celsius TEMP ADJUSTED ERROR C format 96 9 3f TEMP ADJUSTED ERROR FORTRAN format F9 3 TEMP ADJUSTED ERROR resolution 0 001f Argo data management User s manual 21 2 2 6 Calibration information for each profile Calibrations are applied to parameters to create adjusted parameters Different calibration methods will be used by groups processing Argo data When a method is applied its description is stored in the following fields This section contains calibration information for each parameter of each profile Each item of this section has a N_PROF number of profiles N CA
55. CORIOLIS website TRANS FREQUENCY not empty TRANS FREQUENCY 1 44 Argo data management User s manual TRANS_SYSTEM see reference table 10 TRANS_SYSTEM ARGOS TRANS SYSTEM ID not empty TRANS SYSTEM ID 14281 WMO INST TYPE not empty WMO INST TYPE 846 Highly desirable metadata parameters should be correctly filled according to the following table Highly desirable meta data Example BATTERY_PACKS Please populate this field BATTERY PACKS 400 1C Alk according to the standard abbreviations and notations if at all possible in reference table If unknown fill with FillValue 2 5 Technical information format version 3 0 The format version 3 0 of Argo technical data will replace versions 2 3 and 2 2 gradually During the transition period both formats will be valid However when a Data Assembly Center DAC produces technical files with the new 3 0 format all its technical files must be provided in version 3 0 An Argo technical file contains technical information from an Argo float This information is registered for each cycle performed by the float The number and the type of technical information is different from one float model to an other To be flexible for each cycle the name of the parameters and their values are recorded The name of the parameters recorded may therefore change from one model of float to another For file naming conventions see 4 1 2 5 1 Global attrib
56. Carval Add a NMDIS Chinese DAC 2 4 19 11 2011 Thierry Carval general revision of the document presentation 2 4 19 11 2011 52 3 Megan Scanderberg update of trajectory format following Seoul trajectory amp ADMT12 Argo data management User s manual Ae meeting 2 4 19 11 2011 3 3 Thierry Carval CNDC conductivity valid min is set to 8 5 instead of 60 0 2 4 10 02 2012 2 2 3 Thierry Carval vertical sampling scheme to manage profiles performed on different vertical axes 2 4 10 02 2012 2 4 Esmee Vanwijk meta data format version 2 4 2 4 10 02 2012 2 2 3 Thierry Carval global attributes and parameter attributes for CF compatibility 2 4 13 02 0212 82 5 Thierry Carval remove chapter technical information format version 2 2 keep technical information format version 2 3 2 4 20 02 2012 Feedbacks from the draft User s manual sent on 13 02 2012 The changes are highlighted in green The comments are available in argo dm user manual seoul update comment docx 2 4 14 03 2012 Feedbacks from the draft User s manual sent on 14 03 2012 The changes are highlighted in grey The comments are available in argo dm user manual seoul update comment docx 30 03 2012 The version 2 4 of Argo user s manual is officially released 3 02 18
57. DING QC TESTS PERFORMED AND FAILED ccssscssssscsssccsssccescssssscsssscssssssessascsssssssscees 84 5 4 RECORDING CHANGES IN VALUES ENS UE REN ENTE PE 85 6 DAC GDAC DATA MANAGEMENT csssccsssosessornsvsronsossssoonsvosorsovnsvosensnssevacnsvoressornsvercnsorneses 87 ee 87 6 2 GREYLIST FILES OPERATIONS pesssccessctsoosescssecsescssenssensvonacosssonassteespaccocoseessissenss sossessssecrosctecses esses 87 6 2 1 GREYLIST DEFINITION AND MANAGEMENT cccssssssssseescsessecseeecscesecseseecaeeseseeaecessecsesaeeaeeaenees 87 6 2 2 AGRE YEIST FILES pacscefid teet da donnie 88 6 3 GDAC FILES NU CEN 89 II 89 Argo data management User s manual eS History of the document 0 9 29 12 2001 Thierry Carval creation of the document 0 9a 18 01 2002 Bob Keeley general comments and updates 0 9a 24 01 2002 Val rie Harscoat general comments and updates 0 9a 25 01 2002 Claudia Schmid general comments and updates 0 9a 24 01 2002 Roger Goldsmith general comments and updates 0 9b 05 03 2002 Roger Goldsmith Yasushi Takatsuki and Claudia Schmid comments implemented 0 9c 24 04
58. D_ float lt gt ADJUSTED ERROR N PROF lt gt ADJUSTED ERROR contains ERROR N LEVELS the error on the adjusted values of the lt gt ADJUSTED ERROR long name lt X gt parameter lt gt ADJUSTED ERROR FillValue X X this field is specified in the lt gt ADJUSTED ERROR units lt X gt reference table 3 lt gt ADJUSTED ERROR C format lt gt lt gt ADJUSTED ERROR is Argo data management User s manual 20 lt PARAM gt _ADJUSTED_ERROR FORTRAN_format mandatory When no adjustment is lt gt performed the FillValue is inserted lt PARAM gt _ADJ USTED ERROR resolution X The variable PRES pressure is the vertical axis The PRES declaration contains the variable attribute PRES axis Z Example of a profiling float performing temperature measurements with adjusted values of temperature Parameter definition PRES TEMP TEMP_ADJUSTED float TEMP N_PROF N_LEVELS TEMP long_name SEA TEMPERATURE IN SITU ITS 90 SCALE TEMP standard_name sea water temperature TEMP FillValue 99999 f TEMP units degree Celsius TEMP valid min 2 f TEMP valid max 40 f TEMP C format 969 3f TEMP FORTRAN format F9 3 TEMP resolution 0 001f char TEMP QC N PROF LEVELS TEMP QC long name quality flag TEMP QC conventions Argo reference table 2 TEMP Q
59. E arrays This indicates that it might be possible to estimate in the future and acts as a placeholder If a float does not experience an event then the fill values are used for all N CYCLE variables These non events do not get a placeholder in the N MEASUREMENT arrays For file naming conventions see 4 1 2 3 1 Global attributes The global attributes section is used for data discovery The following 11 global attributes should appear in the global section The NetCDF Climate and Forecast CF Metadata Conventions version 1 6 5 December 2011 are available from e http cf pcmdi Inl gov documents cf conventions 1 6 cf conventions pdf global attributes title Argo float trajectory file institution CORIOLIS source Argo float history 2011 04 22T06 00 00Z creation references http www argodatamgt org Documentation comment free text user manual version 3 03 Conventions Argo 3 0 CF 1 6 featureType trajectory dac_decoder_version Argo Coriolis Matlab decoder v3 0 dac_format_id 4 21 2 3 2 Dimensions and definitions Name Definition Comment DATE_TIME DATE_TIME 14 This dimension is the length of an ASCII date and time value Date time convention is YYYYMMDDHHMISS YYYY year MM month DD day HH hour of the day MI minutes SS seconds Date and time values are always in universal time coordinates UTC Examples 20010105172834 January 5 200
60. LEASE Fill Value HISTORY_REFERENCE char HISTORY_REFERENCE Code of the reference database used for quality N HISTORY STRING64 control in conjunction with the software HISTORY REFERENCE long This code is institution dependent Reference of database Example WOD2001 HISTORY REFERENCE conventions Institution dependent HISTORY REFERENCE FillValue HISTORY DATE char HISTORY DATE N HISTORY Date of the action DATE TIME Example 20011217160057 HISTORY DATE long name Date the history record was created HISTORY DATE conventions YYYYMMDDHHMISS HISTORY DATE FillValue HISTORY ACTION char HISTORY ACTION N HISTORY Name of the action STRINGA The action codes are described in reference table 7 HISTORY ACTION long name Example QCF for QC failed Action performed on data HISTORY ACTION conventions Argo reference table 7 HISTORY ACTION FillValue HISTORY PARAMETER char Name of the parameter on which the action is HISTORY PARAMETER N HISTORY performed STRING16 Example PSAL HISTORY PARAMETER long name Station parameter action is performed on HISTORY PARAMETER conventions Argo reference table 3 HISTORY PARAMETER FillValue HISTORY PREVIOUS VALUE float Parameter or flag of the previous value before action HISTORY PREVIOUS VALUE N HIST Example 2 probably good for a flag that was ORY changed to 1 good HISTORY
61. LE_NUMBER_ADJUSTED_INDEX 1 2 3 4 5 6 7 8 9 10 Here FillValue is added to CYCLE NUMBER and CYCLE NUMBER INDEX to indicate that no profile file exists with cycle number 5 A second example of an error that might be discovered in cycle number in delayed mode involves floats that do not send cycle number and for which cycle number must be calculated Here cycle number 5 was incorrectly skipped in real time and is introduced in delayed mode CYCLE NUMBER 1 2 3 4 6 7 8 9 10 11 12 CYCLE NUMBER INDEX 1 2 3 4 6 7 8 9 10 11 12 CYCLE NUMBER ADJUSTED 1 2 3 4 5 6 7 8 9 10 11 CYCLE NUMBER ADJUSTED INDEX 1 2 3 4 5 6 7 8 9 10 11 _ CYCLE_NUMBER 6 which was assigned in real time should actually be assigned cycle number 5 as reflected by the CYCLE_NUMBER_ADJUSTED variable CYCLE_NUMBER always corresponds to the profile cycle number To look for the cycle that matches the profile cycle number users must look in the CYCLE_NUMBER variable for the cycle number they are interested in If the CYCLE NUMBER ADJUSTED variable is Fill Value then this cycle is in real time mode and no corrected cycle number exists If the CYCLE NUMBER ADJUSTED variable is filled this is the correct cycle number as determined during delayed mode For the previous example profile cycle number 6 corresponds to CYCLE NUMBER 6 and CYCLE NUMBER ADJUSTED 5 PARAM contains the uncorrected real time data transmitted by th
62. LIB number of calibrations N_PARAM number of parameters dimension If no calibration is available N CALIB is set to 1 all values of calibration section are set to fill values Name PARAMETER Definition char PARAMETER N PROF N CALIB N_PARAM STRING16 PARAMETER long name List of parameters with calibration information PARAMETER conventions Argo reference table 3 PARAMETER FillValue Comment Name of the calibrated parameter The list of parameters is in reference table 3 Example PSAL SCIENTIFIC CALIB EQUATION char SCIENTIFIC CALIB EQUATION N PROF N CALIB PARAM STRING256 SCIENTIFIC CALIB EQUATION long name Calibration equation for this parameter SCIENTIFIC CALIB EQUATION FillValue ou Calibration equation applied to the parameter Example Tc al T a0 SCIENTIFIC_CALIB_COEFFICIENT char SCIENTIFIC_CALIB_COEFFICIENT N_PROF N_CALIB N_PARAM STRING256 SCIENTIFIC_CALIB_COEFFICIENT long_na me Calibration coefficients for this equation SCIENTIFIC CALIB COEFFICIENT FillValu ez Calibration coefficients for this equation Example 1 0 99997 a0 0 0021 SCIENTIFIC_CALIB_COMMENT char SCIENTIFIC CALIB COMMENT N PROF N CALIB N PARAM STRING256 SCIENTIFIC CALIB COMMENT long name Comment applying to this parameter calibration SCIENTIFIC CALIB COMMENT FillValue Comment about this calibration Example The sensor is not s
63. L_NO long_name Serial number of the sensor SENSOR SERIAL FillValue SENSOR UNITS char SENSOR UNITS N PARAM STRING16 SENSOR UNITS long name fhe Units of accuracy and resolution of the sensor SENSOR UNITS FillValue SENSOR ACCURACY STRING32 char SENSOR PARAM Example 2646 036 073 Units of accuracy of the sensor Example psu Accuracy of the sensor Example 8 micromole l or 596 SENSOR ACCURACY long name Fhe of the sensor SENSOR ACCURACY FillValue SENSOR_RESOLUTION STRING32 char SENSOR RESOLUTION N PARAM Resolution of the sensor Example 0 001 micromole l SENSOR RESOLUTION long name Fhe FResolution of the sensor SENSOR RESOLUTION FillValue 2 4 8 Float calibration information This section contains information about the calibration of the profiler The calibration described in this section is an instrumental calibration The delayed mode calibration based on a data analysis is described in the profile format Name PARAMETER PREDEPLOYMENT_CALIB _EQUATION PREDEPLOYMENT_CALIB_COEFFICIENT PREDEPLOYMENT_CALIB_COMMENT Definition char PARAMETER N_PARAM STRING16 PARAMETER long name List of parameters with calibration information PARAMETER conventions Argo reference table 3 PARAMETER FillValue char PREDEPLOYMENT CALIB EQUATION N PAR AM STRING1024 PREDEPLOYMEN
64. MENT or N CYCLE depending on the corrected parameter Example 150 This field records the tests performed when ACTION is set to QCP qc performed the test failed when ACTION is set to QCF qc failed The QCTEST codes are describe in reference table 11 Example 0A in hexadecimal form The usage of history section is described in 5 Using the History section of the Argo netCDF Structure Argo data management User s manual gt 2 4 Metadata format version 3 0 The format version 3 0 of Argo metadata will replace version 2 2 gradually During the transition period all formats will be valid However when a Data Assembly Center DAC produces metadata files with the new 3 0 format all its metadata files must be provided in version 3 0 An Argo meta data file contains information about an Argo float For file naming conventions see 4 1 2 4 4 Global attributes The global attributes section is used for data discovery The following 8 global attributes should appear in the global section The NetCDF Climate and Forecast CF Metadata Conventions version 1 6 5 December 2011 are available from e http cf pcmdi lInl gov documents cf conventions 1 6 cf conventions pdf global attributes title Argo float metadata file institution CSIRO source Argo float history 2011 04 22T06 00 00Z creation references http www argodatamgt org Documentation comment free t
65. MISSIONS N CONF PARAM CONFIG Mission Number 0 1 2 CONFIG PistonPositionPressureActivation COUNT 100 100 100 CONFIG ParkPressure dBAR 1000 1500 CONFIG ProfilePressure dBAR 2000 2000 CONFIG Direction LOGICAL CONFIG AscentToSurfaceTimeout DecimalHour 3 3 CONFIG ParkPistonPosition COUNT 113 75 CONFIG MeasureBattery LOGICAL 0 0 1 Ascending 2 Descending 0 1 Yes 2 4 7 Float sensor information This section contains information about the sensors of the profiler Name Definition Comment SENSOR char SENSOR N_PARAM STRING16 Parameters measured by sensors of the float The SENSOR long_name List of sensors on the parameter names are listed in reference table 3 float Examples TEMP PSAL CNDC TEMP SENSOR conventions Argo reference table temperature in celsius PSAL practical salinity in 3 psu CNDC conductvity mhos m SENSOR _FillValue SENSOR_MAKER char SENSOR_MAKER N_PARAM STRING256 Name of the manufacturer of the sensor Example SENSOR MAKER long name Fhe aName of SEABIRD the manufacturer SENSOR MAKER FillValue SENSOR MODEL char SENSOR MODEL N PARAM STRING256 Model of sensor SENSOR MODEL long name Type of Example SBE41 sensor SENSOR MODEL FillValue Argo data management User s manual char SENSOR_SERIAL_NO SENSOR_SERIAL_NO N_PARAM STRING16 Serial number of the sensor SENSOR_SERIA
66. Major axis of error ellipse reported by the positioning system Minor axis of error ellipse reported by the positioning system Angle of error ellipse reported by the positioning system Satellite name from positioning system This section contains information on the variables with dimension N CYCLE They include variables that contain the best estimate of float timing Argo data management User s manual 33 Each field in this section has a CYCLE dimension N_CYCLE is the number of collected cycles performed by the float A cycle is defined as a series of actions including collection of data made by a float that ends with transmission of data If the float fails to collect or transmit data a cycle has not occurred and CYCLE_NUMBER_INDEX should not be incremented Floats begin with different cycle numbers depending on float type To understand how the N CYCLE dimension variable group relates to the N MEASUREMENT variable group the user must consult the CYCLE_NUMBER_INDEX variable This variable indicates the cycle number of the float information that is contained in that particular N CYCLE index For example to find the N CYCLE information that corresponds to CYCLE_NUMBER 1 look for CYCLE_NUMBER_INDEX 1 Additionally CYCLE NUMBER INDEX is the number of the profile cycle associated with the trajectory cycle in that index of the N CYCLE array If any errors are discovered in how the cycle numbers were assigned
67. OAT_OWNER OPERATING_INSTITUTIO N CUSTOMISATION char REDEPLOYED STRING32 REDEPLOYED long name Indicates if the float has been previously deployed REDEPLOYED FillValue char FLOAT OWNER STRING64 FLOAT name Fhe fFloat owner FLOAT OWNER FillValue char OPERATING INSTITUTI ON STRING64 OPERATING INSTITUTION long name The eOperating institution of the float OPERATING INSTITUTION FillValue char CUSTOMI SATI ON STRING1024 CUSTOMISATION long name Float customisation i e institution and modifications CUSTOMISATION FillValue 2 4 5 Float deployment and mission information Name LAUNCH_DATE LAUNCH_LATITUDE LAUNCH_LONGITUDE LAUNCH_QC Definition char LAUNCH_DATE DATE_TIME LAUNCH_DATE long_name Date UTC of the deployment LAUNCH DATE conventions YYYYMMDDHHMISS LAUNCH DATE FillValue double LAUNCH LATITUDE LAUNCH LATITUDE long name Latitude of the float when deployed LAUNCH LATITUDE units degrees north LAUNCH LATITUDE FillValue 99999 LAUNCH LATITUDE valid min 90 LAUNCH LATITUDE valid max 90 double LAUNCH LONGITUDE LAUNCH LONGITUDE long name Longitude of the float when deployed LAUNCH LONGITUDE units degrees east LAUNCH LONGITUDE FillValue 99999 LAUNCH LONGITUDE valid min 180 LAUNCH LONGITUDE valid max 180 char LAUNCH QC LAUNCH QC long Qual
68. ORY N_HISTORY Number of history records UNLIMITED 2 2 3 General information on the profile file This section contains information about the whole file Definition Comment DATA_TYPE char DATA_TYPE STRING16 This field contains the type of data DATA_TYPE long_name Data type contained in the file Argo data management User s manual l DATA TYPE FillValue The list of acceptable data types is in the reference table 1 Example Argo profile FORMAT VERSION char FORMAT VERSI ON STRING4 FORMAT VERSION long name File format version FORMAT VERSION FillValue File format version Example 3 0 HANDBOOK VERSION char HANDBOOK VERSI ON STRING4 HANDBOOK VERSION long name Data handbook version HANDBOOK VERSION FillValue Version number of the data handbook This field indicates that the data contained in this file are managed according to the policy described in the Argo data management handbook Example 1 0 REFERENCE DATE TIME char REFERENCE DATE TIME DATE TIME REFERENCE DATE TIME long name Date of reference for Julian days REFERENCE DATE TIME conventions YYYYMMDDHHMISS REFERENCE DATE TIME FillValue Date of reference for julian days The recommended reference date time is 19500101000000 January 1 1950 00 00 00 DATE CREATION char DATE CREATION DATE TIME Date and time
69. OXY ADJUSTED is calculated from the other ADJUSTED fields Calibration coefficients equations and references used to convert the telemetered variables in DOXY must be carefully documented in the metadata Argo data management User s manual 4 The Argo oxygen data management is described at Cookbook documents Processing Argo 3 4 Reference table 4 data centres and institutions codes Data centres and institutions AO AOML USA BO BODC United Kingdom Cl Institute of Ocean Sciences Canada CS CSIRO Australia GE BSH Germany GT GTS used for data coming from WMO GTS network HZ CSIO China Second Institute of Oceanography IF Ifremer France IN INCOIS India JA JMA Japan M amstec Japan KM KMA Korea KO KORDI Korea ME MEDS Canada NA NAVO USA NM NMDIS China PM PMEL USA RU Russia Sl 510 Scripps USA SP Spain UW University of Washington USA VL Far Eastern Regional Hydrometeorological Research Institute of Vladivostock Russia WH Woods Hole Oceanographic Institution USA 3 5 Reference table 5 location classes ARGOS location classes Value Estimated accuracy in latitude and longitude 0 Argos accuracy estimation over 1500m radius 1 Argos accuracy estimation better than 1500m radius 2 Argos accuracy estimation better than 500 m radius Argos accuracy estimation better than 250 m radius GPS positioning accur
70. PREVIOUS VALUE long na me Parameter Flag previous value before action HISTORY PREVIOUS VALUE FillVal 99999 Argo data management User s manual HISTORY INDEX DIMENSION HISTORY START INDEX HISTORY STOP INDEX HISTORY QCTEST char HISTORY INDEX DIMENSION N HIS TORY HISTORY INDEX DIMENSION long name Name of dimension to which HISTORY START INDEX and HISTORY STOP INDEX correspond HISTORY INDEX DIMENSION conve ntions C N CYCLE M N MEASUREMENT HISTORY INDEX DIMENSION FillVa lue int HISTORY START INDEX HISTORY HISTORY START INDEX long name Start index action applied on HISTORY START INDEX FillValue 99999 int HISTORY STOP INDEX HISTORY HISTORY STOP INDEX long name Stop index action applied on HISTORY STOP INDEX FillValue 99999 char HISTORY QCTEST N HISTORY STRING16 HISTORY_QCTEST long_name Documentation of tests performed tests failed in hex form HISTORY_QCTEST conventions Write tests performed when ACTION QCP tests failed when ACTION QCF HISTORY_QCTEST FillValue Name of dimension to which HISTORY_START_INDEX and HISORY_STOP_INDEX correspond N_CYCLE M Start index the action is applied to This index corresponds to N MEASUREMENT CYCLE depending on the corrected parameter Example 100 Stop index the action is applied to This index corresponds to N MEASURE
71. RANSMISSION END STATUS FillValue double CLOCK_OFFSET N_CYCLE CLOCK_OFFSET long_name Time of float clock drift CLOCK OFFSET units days CLOCK OFFSET conventions Days with decimal part as part of day CLOCK OFFSET FillValue 999999 char GROUNDED N CYCLE GROUNDED long name Did the profiler touch the ground for that cycle GROUNDED conventions Argo reference table 20 GROUNDED FillValue float REPRESENTATIVE_PARK_PRESSURE N_CYCLE REPRESENTATIVE PARK PRESSURE IO ng name Best pressure value during drift phase REPRESENTATIVE PARK PRESSURE un its lt gt REPRESENTATIVE PARK PRESSURE F illValue lt X gt char REPRESENTATIVE_PARK_PRESSURE_S TATUS N_CYCLE REPRESENTATIVE_PARK_PRESSURE_S TATUS conventions Argo reference table 21 REPRESENTATIVE PARK PRESSURE S TATUS FillValuez X int CONFIG MISSION NUMBER CYCLE CONFIG MISSION NUMBER long nam e Unique number denoting the missions performed by the float CONFIG MISSION NUMBER convention 5 Q N 0 launch mission if exists 1 first complete mission CONFIG MISSION NUMBER FillValue Julian day UTC of the end of transmission Example 18833 8013889885 July 25 2001 19 14 00 Status flag on JULD date and time The flag scale is described in reference table 19 Example 2 Value is transmitted by the float Decimal part of day that float clock has drifted Float clock dri
72. ROR ELLIPSE MAJOR long name Major axis of error ellipse from positioning system AXES ERROR ELLIPSE MAJOR units meters AXES ERROR ELLIPSE MAJOR FillValue 99999 float AXES ERROR ELLIPSE MINOR N MEASUREM ENT AXES ERROR ELLIPSE MINOR long name Minor axis of error ellipse from positioning system AXES ERROR ELLIPSE MINOR units meters AXES ERROR ELLIPSE MINOR FillValue 99999 float AXES ERROR ELLIPSE ANGLE N MEASUREE NT AXES ERROR ELLIPSE ANGLE long name Angle of error ellipse from positioning system AXES ERROR ELLIPSE ANGLE units Degrees from North when heading East AXES ERROR ELLIPSE ANGLE FillValue 99999 char SATELLITE NAME N MEASUREMENT SATELLITE NAME long name Satellite name from positioning system SATELLITE NAME FillValuez AXES ERROR ELLIP SE MAJOR AXES ERROR ELLIP SE MINOR AXES ERROR ELLIP SE ANGLE SATELLITE NAME 2 3 6 N CYCLE dimension variable group Quality flag applied on each lt PARAM gt _ADJ USTED values The flag scale is specified in reference table 2 lt gt ADJUSTED is mandatory When no adjustment is performed the FillValue is inserted lt gt ADJUSTED ERROR contains the error on the adjusted values of the parameter X these fields are specified in the columns of the reference table 3 lt gt ADJUSTED ERROR is mandatory When no adjustment is performed the FillValue is inserted
73. RT PRES FillValue This field does not apply HISTORY STOP PRES FillValue This field does not apply HISTORY PREVIOUS VALUE FillValue This field does not apply HISTORY QCTEST AO This is the result when data fail tests with IDs of 32 and 128 see reference table 11 5 4 Recording changes in values The PIs have the final word on the content of the data files in the Argo data system In comparing their data to others there may arise occasions when changes may be required in the data We will use the example of recomputation of where the float first surfaced as an example This computation process can be carried out once all of the messages from a float have been received Not all real time processing centres make this computation but it can be made later on and added to the delayed mode data If this is the case we would insert the new position of the profile into the latitude and longitude fields in the profile and we would record the previous values in two history entries Recording these allows us to return to the original value if we have made an error in the newly computed position The two history entries would look as follows Example Changed latitude Field Sample Explanation HISTORY INSTITUTION Cl Selected from the list in reference table 4 HISTORY STEP ARGQ Selected from the list in reference table 12 HISTORY SOFTWARE FillValue This field does not apply HISTORY SOFTWARE RELEASE FillV
74. T CALIB EQUATION long n ame Calibration equation for this parameter PREDEPLOYMENT CALIB EQUATION FillVal ue char PREDEPLOYMENT_CALIB_COEFFICIENT N_P ARAM STRING1024 PREDEPLOYMENT CALIB COEFFICIENT long _name Calibration coefficients for this equation PREDEPLOYMENT CALIB COEFFICIENT Fill Value char PREDEPLOYMENT_CALIB_COMMENT N_PAR AM STRING1024 PREDEPLOYMENT CALIB COMMENT long na me Comment applying to this parameter calibration PREDEPLOYMENT CALIB COMMENT FillVal Comment Parameters measured on this float The parameter names are listed inreference table 3 Examples TEMP PSAL CNDC TEMP temperature in celsius PSAL practical salinity in psu CNDC conductvity in mhos m Calibration equation for this parameter Example Tc al T a0 Calibration coefficients for this equation Example a120 99997 a0 0 0021 Comments applying to this parameter calibration Example The sensor is not stable Argo data management User s manual 2 4 9 Mandatory meta data parameters Mandatory formerly known as highly desirable meta data parameters should be correctly filled according to the following table Mandatory meta data Mandatory format Example BATTERY_TYPE not empty BATTERY_TYPE Alkaline or Lithium or Alkaline and Lithium CONTROLLER BOARD SERIAL NO PRIM not empty CONTROLLER BOARD SERIAL NO PRIMARY ARY 4567 LA
75. TP root number 1 ftp ftp ifremer fr ifremer argo dac FTP root number 2 ftp usgodae usgodae org pub outgoing argo dac GDAC node CORIOLIS file date latitude longitude ocean profiler_type institution date_update e path and file name on the ftp site The file name contain the float number and the cycle number Fill value none this field is mandatory date date of the profile YY YYMMDDHHMISS Fill value blank e latitude longitude location of the profile Fill value 99999 e Ocean code of the ocean of the profile as described in reference table 13 Fill value blank profiler type type of profiling float as described in reference table 8 Fill value blank institution institution of the profiling float described in reference table 4 Fill value blank date update date of last update of the file YYYY MMDDHHMISS Fill value blank Each line describes a file of the gdac ftp site Profile directory format example Title Profile directory file of the Argo Global Data Assembly Center Description The directory file describes all profile files of the argo GDAC ftp site Project ARGO Format version 2 0 Date of update 20031028075500 FTP root number 1 ftp ftp ifremer fr ifremer argo dac FTP root number 2 ftp usgodae usgodae org pub outgoing argo dac GDAC node CORIOLIS file date latitude longitud
76. TY sea water salinity psu 0 f 42 f 99999 f TEMP SEA TEMPERATURE IN sea water temperat degree 2 f 40 f 99999 f SITU ITS 90 SCALE ure Celsius DOXY DISSOLVED OXYGEN moles of oxygen p micromo 0 f 650 f 99999 f er unit mass in se le kg a water TEMP DOXY SEA TEMPERATURE FROM temperature of sen degree 2 f 40 f 99999 f DOXY SENSOR ITS 90 sor for oxygen in s Celsius SCALE ea water PRES DOX dedbar f 12000 f 99999 VOLTAGE DOXY Voltage reported by volt 0 f 100 f 99999 f oxygen sensor SBE43 FREQUENCY DOX Frequency reported by hertz 0 f 25000 f 99999 f Y oxygen sensorXSBE43 COUNT_DOXY Count reported by oxygen 0 f 100 f 99999 f DPHASE_DOXY Calibrated phase shift reported by oxygen sensor foptede Aanderaa 4330 MOLAR_DOXY concentration reported by the oxygen sensor 4330 it degree 10 f 70 f 99999 f I 10 f 70 f 99999 f degree 10 70 f 99999 f 101 70 99999 mole_concentration_ micromo 0 f 650 f 99999 f of dissolved molecu le litre lar oxygen in water degree 70 f 99999 f mil 04 650 f 99999 f Argo data management User s manual 63 If new parameters are required they have to be added to this table before they will be accepted A request for new parameters can be sent to argo dm
77. UNCH LATITUDE not empty 90 lt real lt 90 LAUNCH LONGITUDE not empty 180 lt real lt LAUNCH LONGITUDE 179 828338623047 180 LAUNCH QC see reference table 2 LAUNCH QC 1 MANUAL VERSION not empty MANUAL VERSION 004 or 041708 PARAMETER see reference table 3 PARAMETER PRES TEMP PSAL PI NAME not empty PI NAME Susan Wijffels PLATFORM FAMILY see reference table PLATFORM FAMILY subsurface profiling float I TP POPS PLATFORM MAKER PLATFORM MAKER Optimare PLATFORM NUMBER XXXXX or XXXXXXX PLATFORM NUMBER 5900077 PLATFORM TYPE not empty PLATFORM TYPE SOLO or APEX or PROVOR POSITIONING SYSTEM see reference table 9 POSITIONING SYSTEM ARGOS PREDEPLOYMENT CALIB COEFFICIENT not empty PREDEPLOYMENT CALIB COEFFICIENT ser 3016 temperature coeffs AO 0 0000 1 0 0003 A2 0 0000 0 0000 PREDEPLOYMENT CALIB EQUATION not empty PREDEPLOYMENT CALIB EQUATION Temperature 175 90 1 a0 al lambda nu n a2 lambda 2 n a3 lambda nu 3 n 273 15 deg PTT not empty PTT 23978 Default value n a SENSOR not empty SENSOR TEMP PRES CNDC SENSOR MAKER not empty SENSOR MAKER SEABIRD SENSOR MODEL not empty SENSOR MODEL SBE41 SENSOR SERIAL NO SENSOR SERIAL NO 6785 SENSOR UNITS SENSOR UNITS deg C decibars STANDARD FORMAT ID reference table available at STANDARD FORMAT ID 1 ADMT or
78. a quality flag CR Create record CV Change value DC Station was checked by duplicate checking software ED Edit a parameter value IP This history group operates on the complete input record NG No good trace PE Position error Profile position has been erroneously encoded Corrected if possible QC Quality Control QCF Tests failed QCP Test performed SV Set a value TE Time error Profile date time has been erroneously encoded Corrected if possible UP Station passed through the update program 3 8 Reference table 8 instrument types The instrument type codes come from WMO table 1770 The WMO instrument types are available on the following web site http www meds sdmm dfo mpo gc ca meds Prog_Int J COMM CODES wmotable_e htm ct1770 Code Instrument number E P Alace float 840 Provor no conductivity 841 Provor Seabird conductivity sensor 842 Provor FSI conductivity sensor 843 POPS ice Buoy Float 844 Arvor Seabird conductivity sensor 845 Webb Research no conductivity 846 Webb Research Seabird sensor m Webb Research FSI sensor 850 Solo no conductivity 851 Solo Seabird conductivity sensor 852 Solo FSI conductivity sensor 853 Solo2 Seabird conductivity sensor 855 Ninja no conductivity sensor 856 Ninja SBE conductivity sensor 857 Ninja FSI conductivity sensor 858 Ninja TSK conductivit
79. able 11 updated for frozen profile and deepest pressure tests from Rebecca Macreadie 2 01 28 02 2005 Table 4 updated CSIO China Second Institute of Oceanography 2 01 12 04 2005 Mathieu Belbeoch table 5 updated argos location classes 2 01 12 06 2005 Change lengths of all parameter name variables to accomodate longer parameter names Affects STATION PARAMETERS section 2 2 3 PARAMETER section 2 2 5 and HISTORY PARAMETER section 2 2 6 in the profile format TRAJ ECTORY PARAMETERS section 2 3 3 and HISTORY PARAMETER section 2 3 6 in the trajectory format SENSOR section 2 4 5 and PARAMETER section 2 4 6 in the meta data format 2 01 12 06 2005 Change conventions attribute and description of PROFILE lt gt QC in section 2 2 3 2 01 12 06 2005 Add reference table 2a for the redefined PROFILE lt PARAM gt QC variables 2 01 20 06 2005 New long name for TEMP DOXY in section 3 3 2 01 22 06 2005 Claudia Schmid general update of trajectory file history section N MEASUREMENT dimension removed 2 01 07 11 2005 Claudia Schmid create reference table 14 for technical parameter names Minor typo corrections 2 01 07 11 2005 Thierry Carval add a GPS code for position accuracy in ref Table 5 2 01 08 11 2005 Ann Thresher exemple of sensor type in meta data 2 01 09 11 2005 Annie Wong 3 2 2 usage of PARAM ADJUSTED QC and PARAM QC Reference table 2 updated qc 3 and 4
80. able 4 Example ME for MEDS Degree of processing the data has passed through The data state indicator is described in the reference table 6 This field should contain only the serial number of the float Example 1679 Firmware version of the float Example 013108 Instrument type from WMO code table 1770 A subset of WMO table 1770 is documented in the reference table 8 Example 831 Name of the system used to derive the float locations see reference table 9 Example ARGOS Argo data management User s manual 2 3 5 N MEASUREMENT dimension variable group This section describes the variables found in the N MEASUREMENT dimension variable group In this variable group you find the unadjusted data as reported by the float adjusted timing the reported locations as well as measurements performed along the surface and subsurface trajectory N MEASUREMENT is the number of locations cycle timings and measurements received or estimated from information sent by the float If a cycle is missed nothing is entered into the MEASUREMENT array e g no fill values are allowed to indicate a missing cycle JULD contains the raw timing values either from the satellite system or from the float The values in JULD cannot be estimated nor altered such as for clock drift JULD ADJUSTED contains the best estimate of float timing available for this float If necessary it contains adjusted timing variables d
81. acy ow Iridium accuracy 3 6 Reference table 6 data state indicators Level Descriptor 0 Data are the raw output from instruments without calibration and not necessarily converted to engineering units These data are rarely exchanged 1 Data have been converted to values independent of detailed instrument knowledge Automated calibrations may have been done Data may not have full geospatial and temporal referencing but have sufficient information to uniquely reference the data to the point of measurement Data have complete geospatial and temporal references Information may have been compressed e g subsampled averaged etc but no assumptions of scales of variability or thermodynamic relationships have been used in the processing The data have been processed with assumptions about the scales of variability or thermodynamic relationships The data are normally reduced to regular space time intervals with enhanced signal to noise Argo data management User s manual 65 Class Descriptor Subclass A No scrutiny value judgements or intercomparisons Some reductions or subsampling has been are performed on the data The records are derived performed but the original record is available directly from the input with no filtering or subsampling Geospatial and temporal properties are checked Geophysical values are validated If not validated thi
82. alue This field does not apply HISTORY REFERENCE FillValue This field does not apply HISTORY DATE 2003080500000 The year month day hour minute second that the process 0 ran HISTORY ACTION CV Selected from the list in reference table 7 HISTORY_PARAMETER LAT A new entry for reference table 3 created by institution Cl to indicate changes have been made in the latitude HISTORY START PRES FillValue This field does not apply HISTORY STOP PRES FillValue This field does not apply HISTORY PREVIOUS VALUE 23 456 This is the value of the latitude before the change was made HISTORY QCTEST FillValue This field does not apply Notes 1 Be sure that the new value is recorded in the latitude and longitude of the profile section 2 Besure that the POSITION QC flag is set to 5 to indicate to a user that the value now in the position has been changed from the original one that was there 3 Besure to record the previous value in history entries Argo data management User s manual s6 It is also sometimes desirable to record changes in quality flags that may arise from reprocessing data through some QC procedures In this example assume that whereas prior to the analysis all temperature values from 75 to 105 dbars were considered correct after the analysis they are considered wrong The history entry to record this would look as follows Example Changed flags
83. anagement User s manual CONFIG PARAMETER VALUE double CONFIG PARAMETER VALUE N MISSIONS Value of the configuration N CONF PARAM parameter Example 1500 CONFIG_ PARAMETER VALUE long namez Value of configuration parameter CONFIG_ PARAMETER VALUE FillValue CONFIG MISSION NUMBER int CONFIG MISSION NUMBER N MISSIONS Unique number of the mission CONFIG MISSION NUMBER long name Unique number to which this parameter denoting the missions performed by the floatMission belongs CONFIG MISSION NUMBER conventions 0 N 0 launch Example 0 mission if exists 1 first complete mission See note on floats with CONFIG MISSION NUMBER FillValue 99999 multiple configurations CONFIG MISSION COMMENT char CONFIG MISSION COMMENT N MISSIONS Comment on this configuration STRING256 mission Example This CONFIG MISSION COMMENT long name Comment on mission follows a 1000 dbar configuration meddie during parking CONFIG MISSION COMMENT FillValue The mission settings or parameter values are recorded as numbers In this scheme strings will need to be converted to numbers and will require measurement codes for the relevant parameters The numeric codes for the affected parameters are defined in the Explanation section of the Configuration parameter names table please see reference table 18 Only a few existing parameters are affected If new floats with new configuration parameters as strings are introduced then
84. ar DATA TYPE STRING16 DATA TYPE long name Data type DATA TYPE FillValue char FORMAT VERSION STRING4 FORMAT VERSION long name File format version FORMAT VERSION FillValue char HANDBOOK VERSI ON STRING4 HANDBOOK VERSION long name Data handbook version HANDBOOK VERSION FillValue char REFERENCE DATE TIME DATE TIME REFERENCE DATE TIME long name Date of reference for Julian days REFERENCE DATE TIME conventions YYYYMMDDHHMISS REFERENCE DATE TIME FillValue char DATE CREATION DATE TIME DATE CREATION long Date of file creation DATE CREATIOON conventions YYYYMMDDHHMISS DATE CREATION FillValue char DATE UPDATE DATE TIME DATE UPDATE long name Date of update of this file DATE UPDATE conventions YYYYMMDDHHMISS DATE UPDATE FillValue Comment This field contains the type of data contained in the file The list of acceptable data types is in the reference table 1 Example Argo trajector File format version Example 3 0 Version number of the data handbook This field indicates that the data contained in this file are managed according to the policy described in the Argo data management handbook Example 3 0 Date of reference for julian days The recommended reference date time is 19500101000000 January 1 1950 00 00 00 Date and time UTC of creation of this file Format YYYYMMDDHHMISS
85. ata trajectories and technical data are included in this standardization effort The Argo data formats are based on NetCDF because e Itis a widely accepted data format by the user community e It is a self describing format for which tools are widely available e 15 and efficient format for data exchange 1 6 Argo float cycles A typical Argo float drifts for three years or more in the ocean It continuously performs measurement cycles Each cycle lasts about 10 days and can be divided into 4 stages A descent from surface to a parking pressure e g 1500 decibars A subsurface drift at the parking pressure e g 10 days An ascent from a fixed pressure to surface e g 2000 decibars A surface drift with positioning and data transmission to a communication satellite e g 8 hours Profile measurements e g pressure temperature salinity are performed during ascent occasionally during descent Subsurface measurements during parking are sometime performed e g every 12 hours launch surface drift 0 VEKA pores to profile depth ascent 1500 dbar drift at parking depth 2000 dbar shorter cycle than nominal cycle 0 A typical Argo float performs continuously measurement cycle during 3 years or more in the ocean A more detailed cycle description is available in reference table 15 chapter 3 15 Argo data management User s manual i2 Cycle nami
86. aw information into a complete profile located in space and time 1A note 2 3 The national centre passes the data through automated QC procedures and prepares the data for 2B distribution on the GTS to global servers and to Pls 4 Real time data are received at global data centres that apply QC including visual inspection of the data 2B note These are then distributed to users in near real time 3 5 Data are reviewed by Pls and returned to processing centres The processing centres forward the data to 2C the global Argo servers 6 Scientists accept data from various sources combine them as they see fit with other data and generate a product Results of the scientific analysis may be returned to regional centres or global servers Incorporation of these results improves the quality of the data 7 Scientists working as part of GODAE generate fields of gridded products delivered in near real time for distribution from the global servers Generally these products mostly will be based on data having passed through automated QC procedures 8 Scientists working as part of GODAE generate fields of gridded products delivered with some time delay for distribution from the global servers Generally these products mostly will be based on data having passed through manual or more sophisticated QC procedures than employed on the real time data 2 3B note 4 3C Notes 1 We need to have a pragmatic approach
87. chairman jcommops org for approval and inclusion For each parameter the resolution attribute is mandatory However the resolution value is sensor dependant 3 3 1 Parameters from duplicate sensors Some floats are equipped with 2 different sensors measuring the same physical parameter In that case add the integer 2 at the end of the code of the duplicate parameter e g DOXY2 If more sensors that measure the same physical parameter are added then the integer will simply increase by 1 i e DOXY3 DOXYA and so on Example If a float has one Optode and one SBE oxygen sensor Use DOXY and TEMP DOXY for Optode e Use DOXY2 for SBE If a float has two Optode oxygen sensors e Use DOXY and TEMP_DOXY and DOXY2 and TEMP_DOXY2 If a float has two SBE oxygen sensors e Use DOXY and DOXY2 3 3 2 Oxygen related parameters Some Argo floats perform Oxygen observation from different types of sensors such as the Aandera Optode or the Seabird SBE 43 IDO To provide homogeneous observations from heterogeneous sensors oxygen measurement should be converted and reported as DOXY DOXY is the dissolved oxygen concentration estimated from the telemetered calibrations coefficients and CTD values PRES TEMP or TEMP DOXY and PSAL Pressure and salinity compensations e g Optode are taken into account e DOXY unit micromole kg e DOXY ADJUSTED is the dissolved oxygen concentration corrected for any sensor drift and offset D
88. d Mode data XXX is the cycle number the second D indicates a descending profile profiles without this D are collected during ascent YY counts multiple ascending descending profiles separately Since floats can alternate between the two modes they may have file names following both conventions Examples a 1900045 003 nc 1900045 003D nc b R1900046 007 01 R1900067 007 02 nc 1900067 007 03 nc c R1900046 0070 01 nc R1900067_007D_02 nc 1900067 0070 03 d 1900045 003 nc 1900045 004 01 nc R1900045 004 02 nc R1900045 004 03 nc R1900045 004 04 nc 1900045 005 nc Argo data management User s manual 4 lt FloatID gt _ lt R D gt traj nc real time data delayed mode data Examples Metadata lt FloatID gt _meta nc Example 1900045_meta nc Technical Data e FloatID tech nc Example 1900045 tech nc 4 2 Other data sources Argo data are available from Argo GDACS Global data centres Most Argo data are also available from GTS Global Telecommunication System a network operated by WMO World Meteorological Organization On GTS there are 2 formats for Argo profiles TESAC an Ascii format e BUFR a binary format under development The description of these format is available from the WMO web site e http www wmo ch e http www wmo ch web www DPS NewCodesTables WM O306vol I 1PartA pdf Argo data management User s manual 5 Us
89. d locations of the float are located LATITUDE valid min 90 in the trajectory file LATITUDE valid max 90 Example 44 4991 44 29 56 76 N LATITUDE axis Y LONGITUDE double LONGITUDE N PROF Longitude of the profile LONGITUDE long name Longitude of the Unit degree east station best estimate This field contains the best estimated longitude LONGITUDE standard name longitude The longitude value may be improved in delayed LONGITUDE units degree east mode LONGITUDE FillValue 99999 The measured locations of the float are located LONGITUDE valid min 180 in the trajectory file LONGITUDE valid max 180 Example 16 7222 16 43 19 92 E LONGITUDE axis X POSITION QC char POSITION QC N PROF Quality flag on position The flag on position is set according to LATITUDE LONGITUDE quality The flag scale is described in the reference table 2 Example 1 position seems correct POSITIONING SYSTEM char POSITIONING SYSTEM N PROF STRINGS POSITIONING SYSTEM long name Positioning system POSITIONING SYSTEM FillValue Name of the system in charge of positioning the float locations from reference table 9 Examples ARGOS PROFILE lt gt QC char PROFILE PARAM QC N PROF PROFILE lt gt QC long name Global quality flag of lt PARAM gt profile PROFILE lt gt QC conventions Argo reference table 2a PROFILE PARAM
90. de longitude ocean profiler type institution date update profile temp qc profile psal qc profile doxy qc ad ps al adjustment mean ad psal adjustment deviation aoml 13857 profiles R13857_001 nc 19970729200300 0 267 16 032 A 845 A0 20080918131927 A aoml 13857 profiles R13857_002 nc 19970809192112 0 072 17 659 A 845 A0 20080918131929 A aoml 13857 profiles R13857_003 nc 19970820184545 0 543 19 622 A 845 A0 20080918131931 A meds 3900084 profiles D3900084_099 nc 20050830130800 45 74 58 67 A 846 ME 20060509152833 A A 0 029 0 000 meds 3900084 profiles D3900084_103 nc 20051009125300 42 867 56 903 A 846 ME 20060509152833 A A 0 003 0 000 2 6 3 Trajectory directory format The trajectory directory file describes all trajectory files of the GDAC ftp site Its format is an autodescriptive Ascii with comma separated values The directory file contains A header with a list of general informations title description project name format version date of update ftp root addresses GDAC node e table with a description of each file of the GDAC ftp site This table is a comma separated list Trajectory directory format definition O Title Trajectory directory file of the Argo Global Data Assembly Center Description The directory file describes all trajectory files of the argo GDAC ftp site Project ARGO Format version 2 0 3t Date of update YYYYMMDDHHMISS 3t FTP root
91. described in the reference table 4 Example ME for MEDS DATE CREATION char DATE CREATION DATE TIME DATE CREATION long Date of file creation DATE CREATION conventions YYYYMMDDHHMISS DATE CREATION FillValue Date and time UTC of creation of this file Format YYYYMMDDHHMISS Example 20011229161700 December 29 2001 16 17 00 Argo data management User s manual 55 DATA_UPDATE char DATE_UPDATE DATE_TIME DATE_UPDATE long_name Date of update of this file DATE_UPDATE conventions YYYYMMDDHHMISS DATE UPDATE FillValue Example Date and time UTC of update of this file Format YYYYMMDDHHMISS 20011230090500 December 30 2001 09 05 00 2 5 4 Technical data This section contains a set of technical data for each profile For each cycle for each technical parameter the name of the parameter and the value of the parameter are recorded The parameter name and its value are recorded as strings of 128 characters All parameter names are standardized and available in reference table 14 Name TECHNICAL_PARAMETER_NAME Definition char TECHNICAL PARAMETER NAME N TEC H PARAM STRING128 TECHNICAL PARAMETER NAME long n amez Name of technical parameter TECHNICAL PARAMETER NAME FillVal ue Name of the technical parameter Example CLOCK FloatTime HHMMSS See reference table
92. dimension is the length of an ASCII date and time value Date_time convention is YYYYMMDDHHMISS YYYY year MM month DD day HH hour of the day as 0 to 23 MI minutes as 0 to 59 SS seconds as 0 to 59 Date and time values are always in universal time coordinates UTC Examples 20010105172834 January 5 2001 17 28 34 19971217000000 December 17 1997 00 00 00 STRING256 STRING256 256 String dimensions from 2 to 256 STRING64 STRING64 64 STRING32 STRING32 32 STRING16 STRING16 16 STRING8 STRING8 8 STRING4 STRING4 4 STRING2 STRING2 2 N_PROF N_PROF lt int Number of profiles contained in the file value gt This dimension depends on the data set A file contains at least one profile There is no defined limit on the maximum number of profiles in a file Example N PROF 100 N_PARAM N_PARAM lt int Maximum number of parameters measured or calculated for a pressure value gt sample This dimension depends on the data set Examples pressure temperature N PARAM 2 pressure temperature salinity N PARAM 3 pressure temperature conductivity salinity N PARAM 4 N_LEVELS N_LEVELS lt int Maximum number of pressure levels contained in a profile value gt This dimension depends on the data set Example N_LEVELS 100 N_CALIB N_CALIB lt int Maximum number of calibrations performed on a profile value gt This dimension depends on the data set Example N_CALIB 10 N_HIST
93. ding profiles DIRECTION FillValue Type of profile on which measurement occurs A ascending profile D descending profile DATA CENTRE char DATA CENTRE N PROF STRING2 DATA CENTRE long name Data centre in charge of float data processing DATA CENTRE conventions Argo reference table 4 DATA CENTRE FillValue Code for the data centre in charge of the float data management The data centre codes are described in the reference table 4 Example ME for MEDS DC REFERENCE DATA STATE INDICATOR DATA MODE PLATFORM ROAT SERIAL NO char DC REFERENCE N PROF STRING32 DC REFERENCE long name Station unique identifier in data centre DC REFERENCE conventions Data centre convention DC REFERENCE FillValue char DATA STATE INDICATOR N PROF STRING4 DATA STATE INDICATOR long name Degree of processing the data have passed through DATA STATE INDICATOR conventions Argo reference table 6 DATA STATE INDICATOR FillValue char DATA MODE N PROF DATA MODE long name Delayed mode or real time data DATA MODE conventions R real time D delayed mode A real time with adjustment DATA MODE FillValue Unique identifier of the profile in the data centre Data centres may have different identifier schemes DC REFERENCE is therefore not unique across data centres Degree of processing the data has passed throug
94. dures that rely on typical float behavior Value is transmitted by the float ue is directly computed from relevant transmitted float information Value is determined by satellite Value is not immediately known but believe it can be estimated later o e o lt Argo data management User s manual flag Meaning Y Yes the float touched the ground B Yes the float touched the ground after bathymetry check with an outside database N No the float did not touch the ground S Float is known to be drifting at a shallower depth than originally programmed U Unknown flag Meaning 1 Value is the weighted average of pressure measurements regularly sampled during the drift phase and provided by the float 2 Value is the mean value directly provided by the float of the pressure measurements regularly sampled during the drift phase 3 Value is the median value directly provided by the float of the pressure measurements regularly sampled during the drift phase 4 Value is the pressure measurement sampled at DDST 5 Value is the average of the min and max pressure measurements sampled during the drift phase the precision is 1 bar 6 Value is the PARKING PRESSURE meta data but the float is programmed to sample measurements during the drift phase i e drift measurement is missing 7 Value is the PARKING PRESSURE meta data for
95. e entry for each of these through which the data have passed If data pass through one of these steps more than once an entry for each passage should be written and the variable N HISTORY updated appropriately Argo data management User s manual Some institutions may wish to record more details of what they do In this case adding additional local entries to table 12 is permissible as long as the meaning is documented and is readily available These individual additions can be recommended to the wider community for international adoption Example History entry to record decoding of the data Field Sample Explanation HISTORY INSTITUTION ME Selected from the list in reference table 4 HISTORY STEP ARFM Selected from the list in reference table 12 HISTORY SOFTWARE FillValue This field does not apply HISTORY SOFTWARE RELEASE FillValue This field does not apply HISTORY REFERENCE FillValue This field does not apply HISTORY DATE 2003080500000 The year month day hour minute second that the process 0 ran HISTORY ACTION IP Selected from the list in reference table 7 HISTORY PARAMETER FillValue This field does not apply HISTORY START PRES FillValue This field does not apply HISTORY STOP PRES FillValue This field does not apply HISTORY PREVIOUS VALUE FillValue This field does not apply HISTORY QCTEST FillValue This field does not apply 5 3 Recording QC Tests Perfo
96. e first descent of the float START DATE conventions YYYYMMDDHHMISS START DATE FillValue char START DATE QC START DATE QC long name Quality on start date START DATE QcC conventions Argo reference table 2 START DATE QC FillValue char DEPLOYMENT PLATFORM STRING32 DEPLOYMENT PLATFORM long name Identifier of the deployment platform DEPLOYMENT PLATFORM FillValue char DEPLOYMENT CRUISE ID STRING32 DEPLOYMENT CRUISE ID long Identification number or reference number of the cruise used to deploy the float DEPLOYMENT CRUISE ID FillValue char DEPLOYMENT REFERENCE STATION ID STRING256 DEPLOYMENT REFERENCE STATION ID long name Identifier or reference number of co located stations used to verify the first profile DEPLOYMENT REFERENCE STATION ID FillValue char END MISSION DATE DATE TIME END MISSION DATE long name Date UTC of the end of mission of the float END MISSION DATE conventions YYYYMMDDHHMISS END MISSION DATE FillValue char END MISSION STATUS END MISSION STATUS long name Status of the end of mission of the float END MISSION STATUS conventions T No more transmission received Retrieved END MISSION STATUS FillValue Date and time UTC of the first descent of the float Format YYYYMMDDHHMISS Example 20011230090500 December 30th 2001 06 05 00 Quality flag on start date The flag scal
97. e floats The values in lt gt should never be altered lt PARAM_QC gt contains QC flags that pertain to the values in lt PARAM gt Values in lt QC are set initially in real time by the automatic real time tests They are later modified in D mode at levels where the QC flags are set incorrectly by the real time procedures and where erroneous data are not detected by the real time procedures Each parameter can be adjusted In that case lt PARAM gt _ADJUSTED contains the adjusted values lt gt ADJUSTED QC contains the QC flags set by the delayed mode process and lt gt ADJUSTED ERROR contains the adjustment uncertainties A file A mode processing contains adjusted sections with fill values lt PARAM gt _ADJUSTED lt gt ADJUSTED QC and lt gt ADJUSTED ERROR This is the same for all other ADJUSTED files e g JULD ADJUSTED When no parameter is measured along the trajectory N PARAM number of parameters and any fields relative to parameter are not in the file lt PARAM gt lt gt Argo data management User s manual lt PARAM gt _ADJUSTED lt PARAM gt _ADJUSTED_QC lt PARAM gt _ADJUSTED_ERROR and TRAJECTORY_PARAMETERS Name definition JULD double JULD N_MEASUREMENT JULD long_name Julian day UTC of each measurement relative to REFERENCE_DATE_TIME JULD standard name time JULD units days since 1950 01 01
98. e is described in the reference table 2 Example 1 start date seems correct Identifier of the deployment platform i e vessel or ship name Example L ATALANTE Identification number or reference number of the cruise used to deploy the platform Example POMME2 Identifier or reference number of co located CTD or XBT stations used to verify the first profile Example 58716 58777 Date UTC of the end of mission of the float Format YYYYMMDDHHMISS Example 20011230090500 December 30th 2001 03 05 00 Status of the end of mission of the float T No more transmission received R Retrieved 2 4 6 Configuration parameters This section describes the configuration parameters for a float It is important to note that configuration parameters are float settings not measurements reported by the float Configuration parameters may or may not be reported by a float Configuration parameters are identified by the CONFIG prefix For each configuration parameter the name of the parameter and the value of the parameter are recorded CONFIG PARAMETER NAME Definition char CONFIG PARAMETER NAME N CONF PARAM STRING128 CONFIG_PARAMETER_NAME long_name Name of configuration parameter CONFIG PARAMETER NAME FillValue Comment Name of the configuration parameter Example CONFIG ParkPressure dBAR See reference table 14b for standard configuraton parameter names Argo data m
99. e ocean profiler_type institution date_update aoml 13857 profiles R13857_001 nc 199707292003 0 267 16 032 A 0845 AO 20030214155117 aoml 13857 profiles R13857_002 nc 199708091921 0 072 17 659 A 0845 A0 20030214155354 aoml 13857 profiles R13857_003 nc 199708201845 0 543 19 622 A 0845 A0 20030214155619 jma 29051 profiles R29051 025 nc 200110250010 30 280 143 238 P 846 A 20030212125117 jma 29051 profiles R29051 026 nc 200111040004 30 057 143 206 P 846 A 20030212125117 2 6 2 Profile directory file format version 2 1 The profile directory file describes all individual profile files of the GDAC ftp site Its format is an auto descriptive ASCII with comma separated values This directory file format is more detailed than the previous version 2 0 it will eventually replace it The directory file contains e A header with a list of general information title description project name format version date of update ftp root addresses GDAC node e table with a description of each file of the ftp site This table is comma separated list Argo data management User s manual 57 The detailed index file is limited to core mission Argo sampling scheme temperature salinity and oxygen observations Compression of the profile directory file The profile directory file is compressed with gzip MD5 signature For each update of the directory file an MD5 signature is produced The 5 signature file allows
100. es lt PARAM gt _QC conventions Argo reference table 2 The flag scale is specified in table 2 lt gt FillValue lt PARAM gt _ADJ USTED float PARAM ADJUSTED N PROF LEVELS lt gt ADJUSTED contains the lt gt ADJUSTED long name lt X gt adjusted values derived from the lt gt ADJUSTED standard name lt gt original values of the parameter lt gt ADJUSTED FillValue X X this field is specified in the lt gt ADJUSTED units lt gt reference table 3 lt gt ADJUSTED valid min X lt gt ADJUSTED is mandatory lt gt ADJUSTED valid max X When no adjustment is performed the lt gt ADJUSTED C format lt X gt FillValue is inserted lt gt ADJUSTED FORTRAN format lt X gt lt gt ADJUSTED resolution X lt gt ADJUSTED char lt gt ADJUSTED QC N PROF N LEVELS Quality flag applied on each QC lt gt ADJUSTED QC long name quality flag lt gt ADJUSTED values lt gt ADJUSTED QC conventions Argo The flag scale is specified in reference reference table 2 table 2 lt gt ADJUSTED QC FillValue lt gt ADJUSTED 15 mandatory When no adjustment is performed the FillValue is inserted lt PARAM gt _ADJUSTE
101. ext user manual version 3 03 Conventions Argo 3 0 CF 1 6 2 4 2 Dimensions and definitions Definition Comment DATE_TIME DATE_TIME 14 This dimension is the length of an ASCII date and time value Date_time convention is YYYYMMDDHHMISS YYYY year MM month DD day HH hour of the day MI minutes SS seconds Date and time values are always in universal time coordinates UTC Examples 20010105172834 January 5th 2001 17 28 34 19971217000000 December 17th 1997 00 00 00 STRING1024 STRING1024 1024 STRING256 STRING256 256 STRING64 STRING64 64 STRING32 STRING32 32 String dimensions from 2 to 1024 STRING16 STRING16 16 STRING8 STRING8 8 STRING4 STRING4 4 STRING2 STRING2 2 N_PARAM N_PARAM lt int value gt Number of parameters measured or calculated for a pressure sample Examples pressure temperature N PARAM 2 pressure temperature salinity N PARAM 3 pressure temperature conductivity salinity 4 Argo data management User s manual N CONF PARAM MISSIONS N POSITIONING SYSTEM N TRANS SYSTEM N CONF PARAM int value Number of configuration parameters N MISSIONS unlimited N TRANS SYSTEM int value cn Ne SYSTEMS lt mt Number of positioning systems Number of transmission systems 2 4 3 General information on the meta data file This section contains information about the whole file Name
102. file includes near surface measurements that are focused on the top pumped unpumped description 5dbar of the sea surface For the purpose of cross calibration this profile or can extend deeper than the top 5dbar so as to overlap with the Primary Near surface sampling discrete sampling profile These measurements are taken at pressure levels pumped unpumped description different from the Primary CTD profile or with sampling methods different or from the Primary CTD profile If the Primary sampling profile measures Near surface sampling mixed above 5dbar in the same manner as deeper data there is no need to place pumped unpumped description the near surface data here Bounce sampling averaged description gt 1 This scheme contains profiles that are collected on multiple rises falls during or a single cycle The profiles are temporally offset from each other and or the Bounce sampling discrete description Primary sampling profile They can be sampled with the Primary CTD or or with auxiliary sensors Bounce sampling mixed description Use the term averaged if the data in the profile are pressure binned averages using multiple data measurements pollings from a sensor Use the term discrete if the data in the profile are from a single polling from a sensor If both methods are used in the profile use the term mixed Example for a SOLOII V1 2 float N_PROF 1 Primary sampling averaged nominal 2 dbar binned data sa
103. file itself Name PLATFORM_NUMBER DATA_TYPE Definition char PLATFORM NUMBER STRI NG8 PLATFORM NUMBER long name Float unique identifier PLATFORM NUMBER conventions WMO float identifier A9IIITI PLATFORM NUMBER FillValue char DATA TYPE STRING32 DATA TYPE long name Data type DATA TYPE FillValue Comment WMO float identifier WMO is the World Meteorological Organization This platform number is unique Example 6900045 This field contains the type of data contained in the file The list of acceptable data types is in the reference table 1 Example Argo technical data FORMAT_VERSION char FORMAT VERSION STRINGA FORMAT VERSION long name File format version FORMAT VERSION FillValue File format version Example 3 0 HANDBOOK VERSION char HANDBOOK VERSION STRING4 HANDBOOK VERSION long name Data handbook version HANDBOOK VERSION FillValue Version number of the data handbook This field indicates that the data contained in this file are managed according to the policy described in the Argo data management handbook Example 1 0 DATA CENTRE char DATA CENTRE STRING2 DATA CENTRE long name Data centre in charge of float data processing DATA CENTRE conventions Argo reference table 4 DATA CENTRE FillValue Code of the data centre in charge of the float data management The data centre codes are
104. ft is defined as Float time provided by the inboard Real Time Clock RTC of the float UTC time This makes the clock drift is lt 0 if float RTC is before UTC time Float clock drift can be corrected in real time or in delayed mode Real time corrections correspond to a data mode of A For A mode files JULD ADJUSTED JULD CLOCK OFFSET D mode files may have corrections for clock drift only or additional time corrections based on expert review Example 1 08546 the clock drift is estimated to be equal to 1 day 2 hours 3 minutes and 4 seconds at the time of the corresponding cycle surfacing GROUNDED indicates the best estimate of whether the float touched the ground for that cycle The conventions are described in Argo reference table 20 Examples Y yes the float touched the ground B yes the float touched the ground after a bathymetry check The Representative Park Pressure RPP is the best pressure value assigned to the drift phase See the REPRESENTATIVE PARK PRESSURE STATUS variable to understand how this pressure was evaluated It should match the PRES N MEASUREMENT values with MC 301 X these fields are specified in the columns of the reference table 3 Example 1025 Status flag on the Representative Park Pressure RPP The flag scale is described in reference table 21 Example 2 mean value directly provided by the float of pressure measurements regularly sampled during the drift p
105. ght happen if the float s first cycle has a cycle number of zero rather than one Additionally all the elements of the N MEASUREMENT variables for which CYCLE NUMBER 3 are likewise associated with the 4th N CYCLE elements and with the WMO_003 nc profile file This clearly links the index in the N CYCLE array to the cycle number in the N MEASUREMENT array Additionally CYCLE NUMBER 1 indicates the float s launch and JULD and LATITUDE and LONGITUDE variables should contain the float s launch time and location CYCLE NUMBER ADJUSTED contains a cycle numbering which has been assessed and adjusted to be correct especially for the purposes of trajectory calculations If a cycle is recovered during delayed mode and no profile file is created the cycle must be added into the CYCLE NUMBER ADJUSTED and CYCLE NUMBER ADJUSTED INDEX variables Two examples recovered cycles are below The first example is where cycle number 5 is recovered in delayed mode The cycle number variables must be rewritten as follows Argo data management User s manual _ 1 2 3 4 6 7 8 9 10 11 CYCLE_NUMBER_INDEX 1 2 3 4 6 7 8 9 10 11 CYCLE_NUMBER_ADJUSTED 1 2 3 4 5 6 7 8 9 10 _ CYCLE_NUMBER_ADJUSTED_INDEX 1 2 3 4 5 6 7 8 9 10 _ CYCLE_NUMBER 1 2 3 4 6 7 8 9 10 11 CYCLE_NUMBER_INDEX 1 2 3 4 6 7 8 9 10 11 CYCLE_NUMBER_ADJUSTED 1 2 3 4 5 6 7 8 9 10 _ CYC
106. h The data state indicator is described in the reference table 6 Indicates if the profile contains real time delayed mode or adjusted data R real time data D delayed mode data A real time data with adjusted values FIRMWARE VERSION char FIRMWARE VERSION N PROF FIRMWARE VERSION long name Instrument version FIRMWARE VERSION FillValue Firmware version of the float Example 013108 WMO INST TYPE char WMO INST TYPE N PROF STRINGA4 WMO INST TYPE long name Coded instrument type WMO INST TYPE conventions Argo reference table 8 WMO INST TYPE FillValue Instrument type from WMO code table 1770 A subset of WMO table 1770 is documented in the reference table 8 Example 846 Webb Research float Seabird sensor JULD double JULD N PROF Julian day of the profile JULD long name Julian day UTC of the The integer part represents the day the decimal station relative to REFERENCE DATE TIME part represents the time of the profile JULD standard name time Date and time are in universal time coordinates JULD units days since 1950 01 01 The julian day is relative to 00 00 00 UTC REFERENCE DATE TIME JULD conventions Relative julian days with Example decimal part as parts of day 18833 8013889885 July 25 2001 19 14 00 JULD FillValue 999999 JULD axis JULD_QC char JULD QC N PROF Quality flag on JULD date and time
107. hase Unique number of the mission to which this parameter belongs Example 1 See 82 4 5 Configuration parameters and note on floats with multiple configurations Argo data management User s manual pC 99999 CYCLE NUMBER INDEX CYCLE NUMBER INDEX _ADJ SUTED DATA_MODE int CYCLE_NUMBER_INDEX N_CYCLE CYCLE_NUMBER_INDEX long_name Cycle number that corresponds to the current index CYCLE_NUMBER_INDEX conventions 0 0 launch cycle 1 first complete cycle CYCLE NUMBER INDEX FillValue 99999 int CYCLE NUMBER INDEX ADJSUTED CYCLE CYCLE NUMBER INDEX SUTED lon g name Cycle number that corresponds to the current index CYCLE NUMBER INDEX SUTED co nventions 0 N 0 launch cycle 1 first complete cycle CYCLE NUMBER INDEX SUTED Fill Value 99999 char DATA MODE N CYCLE DATA MODE long name Delayed mode or real time data DATA MODE conventions R real time D delayed mode A real time with adjustment DATA MODE FillValue 2 3 7 History information Cycle number of the float that corresponds to the information contained in the current index This cycle number must match the profile cycle number ensuring that the trajectory and profile with the same cycle number contain data from the same cycle Example 17 means information for the 17 cycle of the float is contained in this index Corrected cycle number of the float
108. he GPS positioning sytem Examples 3 for a latitude and longitude accuracy 250 m G for GPS accuracy Quality flag on position The flag on position is set according to LATITUDE LONGITUDE JULD quality The flag scale is described in the reference table 2 Example 1 position seems correct Cycle number of the float for this series of measurements locations and timings Some floats begin with a cycle 0 and some begin at cycle number 1 Cycle number is 1 for the float s launch and includes the time and location For one cycle number there are usually several locations measurement received This cycle number must match the profile cycle number Example 17 for measurements performed during the 17 cycle of the float Adjusted cycle number of the float for this series of measurements locations and timings Some floats begin with a cycle 0 and some begin at cycle number 1 For one cycle number there are usually several locations measurement received Sometimes cycle numbers are assigned erroneously and need to be corrected This variable contains the corrected cycle numbers Example 17 for measurements performed during the 17 cycle of the float Flag for each event in the cycle which corresponds to Argo reference table 15 Example 100 All measurements made at start of descent to drift pressure Could be time location surface pressure etc lt PARAM gt contains the original values of a parameter listed
109. hn 61 3 3 REFERENCE TABLE 3 PARAMETER CODE TABLE eee ee ee eee enne eee en sese etta sese tetas esee tense see ea sese 62 3 3 1 PARAMETERS FROM DUPLICATE SENSORS cccssscesscesscesssesseeceecseecssecsaecsaeceseceseceseeesseessecsseesaees 63 3 3 2 OXYGEN RELATED PARAMETERS ccccsscessecssscseceseecseecssecssecssecssccssecsseesseeeeseeeseseseaeeesseeaaeeneees 63 3 4 REFERENCE TABLE 4 DATA CENTRES AND INSTITUTIONS CODES ccsscssssscsssscsssssessessssescessses 64 3 5 REFERENCE TABLE 5 LOCATION CLASSES eee ee eere eee eene enne reete sete seen seen seen senos snae 64 3 6 REFERENCE TABLE 6 DATA STATE INDICATORS ee eee eee eee ene to esto st sean seen seen eese sonas 64 3 7 REFERENCE TABLE 7 HISTORY ACTION CODES eee ee esee eese ta sete sese teta sesta ea aeuo 66 3 8 REFERENCE TABLE 8 INSTRUMENT TYPES eeeeee esee eee en ases tease s tease see aset eaae s eo na aeo 66 3 9 REFERENCE TABLE 9 POSITIONING SYSTEM ecce ee ee eese ense eee en nose etta sese teta sese tetas eset 67 3 10 REFERENCE TABLE 10 TRANSMISSION SYSTEM eeeee esee eee en sese ense sesta sese teta se sese 67 3 11 REFERENCE TABLE 11 QC TEST BINARY IDS eee eere eene een eee eo sette setas stans essa aea 67 3 12 REFERENCE TABLE 12 HISTORY STEPS CODES
110. in reference table 4 Fill value blank ate update date of last update of the file YYYY MMDDHHMISS ill value blank e mao Metadata directory example Title Metadata directory file of the Argo Global Data Assembly Center Description The directory file describes all metadata files of the argo GDAC ftp site Project ARGO Format version 2 0 Date of update 20031028075500 FTP root number 1 ftp ftp ifremer fr ifremer argo dac 3t FTP root number 2 ftp usgodae usgodae org pub outgoing argo dac GDAC node CORIOLIS file profiler type institution date update aoml 13857 13857_meta nc 0845 A0 20030214155117 aoml 13857 13857_meta nc 0845 A0 20030214155354 aoml 13857 13857_meta nc 0845 A0 20030214155619 jma 29051 29051 meta nc 846 A 20030212125117 jma 29051 29051_meta nc 846 A 20030212125117 Argo data management User s manual 60 3 Reference tables 3 1 Reference table 1 data type This table contains the list of acceptable values for DATA TYPE field Argo profile Argo trajectory Argo meta data Argo technical data 3 2 Reference table 2 Argo quality control flag scale 3 2 1 Reference table 2 measurement flag scale A quality flag indicates the quality of an observation The flags are assigned in real time or delayed mode according to the Argo quality control manual available at e http www argodatamgt org Documentation
111. ing the History section of the Argo netCDF Structure Within the netCDF format are a number of fields that are used to track the progression of the data through the data system This section records the processing stages results of actions that may have altered the original values and information about QC tests performed and failed The purpose of this document is to describe how to use this section of the format The creation of entries in the history section is the same for both profile and trajectory data The next sections provide examples of what is expected The information shown in the column labeled Sample is what would be written into the associated Field name in the netCDF format 5 1 Recording information about the Delayed Mode QC process The process of carrying out delayed mode QC may result in adjustments being made to observed variables The table below shows how to record that the delayed mode QC has been done Note that the fields HISTORY SOFTWARE HISTORY SOFTWARE RELEASE and HISTORY REFERENCE are used together to document the name and version of software used to carry out the delayed QC and the reference database used in the process The contents of these three fields are defined locally by the person carrying out the QC Example History entry to record that delayed mode QC has been carried out Field Sample Explanation HISTORY_INSTITUTION Cl Selected from the list in reference table 4
112. ions Argo reference table 19 JULD_DEEP_ASCENT_START_STATUS _FillValue double JULD ASCENT END N CYCLE JULD ASCENT END long name End date of the float s ascent to the surface JULD ASCENT END standard name time JULD ASCENT END units days since 1950 01 01 00 00 00 UTC JULD ASCENT END conventions Relative julian days with decimal part as part of JULD ASCENT END FillValue 999999 char JULD ASCENT END STATUS N CYCLE y JULD ASCENT END STATUS conventio ns Argo reference table 19 JULD ASCENT END STATUS FillValue double JULD TRANSMISSION START N CYCL E JULD TRANSMISSION START long na me Start date of transmssion JULD TRANSMISSION START standard _ time JULD_TRANSMISSION_START units days since 1950 01 01 00 00 00 UTC JULD TRANSMISSION START conventi ons Relative julian days with decimal part as part of day JULD TRANSMISSION START FillValu e 999999 char JULD TRANSMISSION START STATUS CYCLE JULD TRANSMISSION START STATUS conventions Argo reference table 19 JULD_TRANSMISSION_START_STATUS FillValue double JULD FIRST MESSAGE N CYCLE JULD FIRST MESSAGE long name Date of earliest float message received JULD FIRST MESSAGE standard name time JULD FIRST MESSAGE units days since 1950 01 01 00 00 00 UTC Status flag on JULD date and time The flag scale is described in reference table 19 Example 2 Va
113. iple float types They are believed to be valuable enough in trajectory estimation that they are defined here and not within the generically defined MC minus 24 to MC minus 1 span MC codes in this span will be specific to the MC code and will NOT be repeated for other Primary and Secondary MCs An example APEX floats report the Down time end date which is important in determining the start of ascent MC 500 The MC for Down time end date is recorded with MC plus 1 MC 501 Relative Generic Code Table Key from MC minus 24 to MC minus 1 This table pertains to any measurement code that has lower value and within 24 of a Primary or Secondary Measurement Code see below These definitions apply relative to every Primary and Secondary code For example AST time of ascent start MC 500 and AET time of ascent end MC 600 are both Primary MCs There exists a measurement code MC minus 4 for both AST and AET which is assigned to any averaged measurement that is taken while transitioning towards the MC If an averaged measurement is recorded while transitioning towards AST the correct MC 496 If an averaged measurement is recorded while transitioning towards AET the correct MC 596 Relative Measure ment code Any single measurement transitioning towards MC see MC 10 for a series of measurements Maximum value while float is transitioning towards an MC e g pressure Minimum value while float is transitioning towards an MC e g
114. ity on launch date time and location LAUNCH QC conventions Argo reference table 2 LAUNCH QC FillValue Indicates if the float has been previously deployed i e recovered after first mission and deployed with a new wmo id In this case you would fill this field with the previous wmo id Example The owner of the float may be different from the data centre and operating institution The operating institution of the float may be different from the float owner and data centre Example ACE CRC Free form field to record changes made to the float after manufacture and before deployment i e this could be the customisation institution plus a list of modifications Comment Date and time UTC of launch of the float Format YYYYMMDDHHMISS Example 20011230090500 December 30th 2001 03 05 00 Latitude of the launch Unit degree north Example 44 4991 44 29 56 76 Longitude of the launch Unit degree east Example 16 7222 16 43 19 92 E Quality flag on launch date time and location The flag scale is described in the reference table 2 Example 1 launch location seems correct Argo data management User s manual START_DATE START_DATE_QC DEPLOYMENT_PLATFO RM DEPLOY MISSION DEPLOYMENT_CRUISE _ID DEPLOYMENT_REFERE NCE_STATION_ID END_MISSION_DATE END_MISSION_STATU 5 char START_DATE DATE_TIME START_DATE long_name Date UTC of th
115. liest position Example 18833 8013889885 July 25 2001 19 14 00 Status flag on JULD date and time The flag scale is described in reference table 19 Example 2 Value is transmitted by the float Julian day UTC of the latest position Example 18833 8013889885 July 25 2001 19 14 00 Status flag on JULD date and time The flag scale is described in reference table 19 Example 2 Value is transmitted by the float Julian day UTC of the latest float message received May or may not have a position associated with it Example 18833 8013889885 July 25 2001 19 14 00 Status flag on JULD date and time The flag scale is described in reference table 19 Example 2 Value is transmitted by the float Argo data management User s manual JULD_TRANSMISSION_ END JULD_TRANSMISSION_ END_STATUS CLOCK_OFFSET GROUNDED REPRESENTATIVE_PAR K_PRESSURE REPRESENTATIVE_PAR K_PRESSURE_STATUS CONFIG MISSION NUM BER double JULD TRANSMISSION END N CYCLE JULD TRANSMISSION END long name Transmssion end date JULD TRANSMISSION END standard n ame time JULD TRANSMISSION END units days since 1950 01 01 00 00 00 UTC JULD TRANSMISSION END convention S Relative julian days with decimal part as part of day JULD TRANSMISSION END FillValue 999999 char JULD TRANSMISSION END STATUS N CYCLE JULD TRANSMISSION END STATUS c onventions Argo reference table 19 JULD T
116. lines refer to some floats that DPST FMT LMT AST TST LLT DST FST DET PST PET DDET si LT TET Surface I I Argos GPS locations I 1 Parking l pressure l 1 1 1 Profile riot Cycle N 1 1 i profile on descent Cycle 1 AAA A 1 Depth DDET DAST AST DPST Figure 1 Figure showing float cycle and the cycle timing variables Floats can profile either on descent or ascent Most floats profile on ascent Their float path is shown with a solid black line Some floats profile on descent One such float the new SOLO II Deep float has a cycle as shown by the dashed line Floats that profile on ascent would have the following mandatory cycle timings e DST DET PET DDET AST AET and all surface times Floats that profile on descent might have the following cycle timings DST DDET DAST DET PET AST and all surface times Time Long name Traj data name Description DST Descent Start JULD DESCENT START Time when float leaves the surface beginning Argo data management User s manual JULD DESCENT START descent STATUS FST First JULD FIRST STABILIZATION Time when a float first becomes water neutral Stabilization JULD FIRST STABILIZATION STATUS Time DET Descent End JULD DESCENT END Time when float first approaches within 396 of the Time JULD DESCENT END STATUS eventual drift pressure Float may be transitioning
117. ll value blank date update date of last update of the file YYYYMMDDHHMISS Fill value blank profile temp qc profile psal qc profile doxy qc global quality flag on temperature salinity and oxygene profile Fill value blank ad psal adjustment mean for delayed mode or adjusted mode Mean of psal adjusted psal on the deepest 500 meters with good psal adjusted qc equal to 1 Fill value blank e psal adjustment deviation for delayed mode or adjusted mode Standard deviation of psal adjusted psal on the deepest 500 meters with good psal adjusted qc equal to 1 Fill value blank gdac date creation cr ation date of the file on GDAC YYYYMMDDHHMISS gdac date update update date of the file on GDAC YYYYMMDDHHMISS e levels maximum number of pressure levels contained in a profile Fill value blank Each line describes a file of the gdac ftp site Profile directory format example Title Profile directory file of the Argo Global Data Assembly Center Description The directory file describes all individual profile files of the argo GDAC ftp site Project ARGO Format version 2 1 Argo data management User s manual 58 Date of update 20081025220004 FTP root number 1 ftp ftp ifremer fr ifremer argo dac 3t FTP root number 2 ftp usgodae usgodae org pub outgoing argo dac GDAC node CORIOLIS file date latitu
118. lue is transmitted by the float Julian day UTC of the end of the ascent to the surface Example 18833 8013889885 July 25 2001 19 14 00 Status flag on JULD date and time The flag scale is described in reference table 19 Example 2 Value is transmitted by the float Julian day UTC of the beginning of data transmission Example 18833 8013889885 July 25 2001 19 14 00 Status flag on JULD date and time The flag scale is described in reference table 19 Example 2 Value is transmitted by the float Julian day UTC of the earliest float message received May or may not have a position associated with it Example 18833 8013889885 July 25 2001 19 14 00 Argo data management User s manual JULD_FIRST_ MESSAGE _STATUS JULD_FIRST_LOCATION JULD_FIRST_LOCATION _STATUS JULD_LAST_LOCATION JULD_LAST_LOCATION _STATUS JULD_LAST_MESSAGE JULD_LAST_MESSAGE_ STATUS J ULD_FIRST_MESSAGE conventions Relative julian days with decimal part as part of day JULD_FIRST_MESSAGE _FillValue 999 999 char JULD FIRST MESSAGE STATUS N CY CLE JULD FIRST MESSAGE STATUS conve ntions Argo reference table 19 JULD FIRST MESSAGE STATUS FillVa lue double JULD_FIRST_LOCATION N_CYCLE JULD FIRST LOCATION long name Date of earliest location JULD FIRST LOCATION standard nam e time JULD FIRST LOCATION units days since 1950 01 01 00 00 00 UTC JULD FIRST LOCATION co
119. me Describe any anomalies or problems the float may have had ANOMALY FillValue char BATTERY TYPE STRING64 BATTERY TYPE long name Fhe tType of battery packs in the float BATTERY TYPE FillValue char BATTERY PACKS STRING64 BATTERY PACKS long name The configuration of battery packs in the float BATTERY PACKS FillValue char CONTROLLER BOARD TYPE PRI MARY STRING32 CONTROLLER BOARD TYPE PRIMARY long name FhetType of controller board CONTROLLER BOARD TYPE PRIMARY FillValue char CONTROLLER BOARD TYPE SECONDARY STRING32 CONTROLLER BOARD TYPE SECONDARY long name Fhe sSecondary type of controller board CONTROLLER BOARD TYPE SECONDARY FillValue n 1 CONTROLLER_BOARD_SERIAL_NO_PRIMARY STRING32 CONTROLLER_BOARD_SERIAL_NO_PRIMARY long name Fhe sSerial number of the primary controller board CONTROLLER BOARD SERIAL NO PRIMARY FillValue D char CONTROLLER BOARD SERIAL NO SECONDARY STRIN G32 CONTROLLER_BOARD_SERIAL_NO_SECONDARY long name Serial number of the secondary controller board CONTROLLER BOARD SERIAL NO SECONDARY FillVal ue char SPECIAL_FEATURES STRING1024 SPECIAL_FEATURES long_name Extra features of the float algorithms compressee SPECIAL FEATURES FillValue Instrument type from WMO code table 1770 A subset of WMO table 1770 is documented in the reference table 8 Example
120. mpled at 0 5 Hz from a SBE41CP N_PROF 2 Near surface sampling discrete pumped shallowest polling of a SBE41CP Argo data management User s manual l Note In this example by adding a single data point in N_PROF 2 the size of the profile file will double Example for a Provor bio 5 0 float This float is equipped with a Seabird CTD and a Wetlab Satrover optical sensor CTD sampling scheme The threshold between deep sampling and upper sampling is 200 decibars e Upper sampling 10 decibars slice thickness 10 seconds sampling rate e Deep sampling 25 decibars slice thickness 10 seconds sampling rate Chlorophyll optical sampling scheme e The threshold between deep sampling and upper sampling is 300 decibars e Upper sampling 1 decibar slice thickness 1 seconds sampling rate e Deep sampling 10 decibars slice thickness 10 seconds sampling rate e Deepest sampling 1000 decibars Description of the 2 vertical sampling schemes N_PROF 1 Primary sampling averaged 10 seconds sampling 25 decibars average from bottom to 200 decibars 10 seconds sampling 10 decibars average from 200 decibars to surface N_PROF 2 Secondary sampling averaged 10 seconds sampling 10 decibars average from 1000 decibars to 300 decibars 1 second sampling 1 decibar average from 300 decibars to surface Example for an APEX Iridium float with an Optode oxygen sensor and an auxiliary CTD for near surface measurements N_PROF 1
121. ng convention Float cycle numbers usually start at 1 The next cycles are increasing numbers e g 2 3 N If the float reports cycle number this is what should be used in all Argo files Very conveniently some floats transmit their configuration during the transmissions before they descent for profile 1 Cycle 0 contains the first surface drift with technical data transmission or configuration information This data is reported in the technical data files Cycle 0 may contain subsurface measurements if a descending ascending profile is performed before any data transmission The time length of this cycle is usually shorter than the next nominal cycles The cycle time is therefore regular only for later profiles and may be variable if the float is reprogrammed during its mission 1 7 Real time and Delayed mode data Data from Argo floats are transmitted from the float passed through processing and automatic quality control procedures as quickly as possible after the float begins reporting at the surface The target is to issue the data to the GTS and Global Data servers within 24 hours of surfacing or as quickly thereafter as possible These are called real time data The data are also issued to the Principle Investigators on the same schedule as they are sent to the Global servers These scientists apply other procedures to check data quality and the target is for these data to be returned to the global data centres within 6 to 12 months
122. ng information but are not as important as the primary or secondary timing variables The value span is subdivided into two halves Measurement codes in this section will be described relative to the values of the Primary and Secondary codes Secondary Measurement Codes MC Each marks a suggested to fill cycle timing variable Secondary MC are not always applicable to all floats but are very useful in determining trajectory estimates Relative Generic Codes Values spanning from MC minus 24 to MC minus 1 Measurement codes that have lower value and within 24 of a Primary or Secondary Measurement Code These code definitions are phrased generally so can be attached to data from many different floats These code values MC minus 24 to MC minus 1 are assigned when a float records a measurement while transitioning TOWARDS the MC The definitions of the MC from MC minus 24 to MC minus 1 are repeated for all Primary and Secondary MC An example most floats record pressure temperature salinity during drift The float is transitioning towards PET MC 300 during this period Thus the pressure temperature salinity measurements will have an MC between MC minus 24 and MC minus 1 where MC 300 thus between MC 276 and MC 299 Which value is chosen is determined by the measurement itself See table below Relative Specific Codes Values spanning from MC plus 1 to MC plus 25 These are specific measurements that are generally NOT recorded by mult
123. ng schemes This variable differentiates the various vertical sampling schemes for multiple profiles from a single cycle This variable can vary between cycles to accommodate floats with two way communication capabilities The profile with N_PROF 1 is required to be the Primary sampling profile Other profiles will have N_PROF gt 1 in any order There can be only one Primary sampling profile while other vertical sampling schemes can have more than one profile Code STRING256 N_PROF Code Description FORMAT name nominal measurement type full description indicates optional Primary sampling averaged description Primary CTD measurements and measurements from auxiliary sensors that or are taken at the same pressure levels and with the same sampling method Primary sampling discrete description as the Primary CTD profile For auxiliary sensor measurements it is not or required that all pressure levels contain data Primary sampling mixed description Secondary sampling averaged gt 1 Excluding Primary sampling this profile includes measurements that are description taken at pressure levels different from the Primary CTD profile or with or sampling methods different from the Primary CTD profile Measurements Secondary sampling discrete description can be taken by the Primary CTD or by auxiliary sensors or Secondary sampling mixed description Near surface sampling averaged gt 1 This pro
124. ng the data have passed through DATA STATE INDICATOR conventions Argo reference table 6 DATA STATE INDICATOR FillValue 1 char FLOAT_SERIAL_NO STRING16 FLOAT_SERIAL_NO long_name 5 number of the float FLOAT SERIAL NO FillValue char FIRMWARE VERSION FIRMWARE VERSION long name Instrument firmware version FIRMWARE VERSION FillValue char WMO INST TYPE STRINGA WMO INST TYPE long name Coded instrument type WMO INST TYPE conventions Argo reference table 8 WMO INST TYPE FillValue char POSITIONING SYSTEM STRINGB8 POSITIONING SYSTEM long name Positioning system POSITIONING SYSTEM FillValue 27 Comment WMO float identifier WMO is the World Meteorological Organization This platform number is unique Example 6900045 Name of the project which operates the float that performed the trajectory Example GYROSCOPE EU project for ARGO program Name of the principal investigator in charge of the float Example Yves Desaubies List of parameters contained in this trajectory file The parameter names are listed in reference table 3 Examples PRES TEMP PSAL CNDC DOXY etc PRES pressure TEMP temperature PSAL practical salinity CNDC electrical conductivity DOXY dissolved oxygen Code for the data centre in charge of the float data management The data centre codes are described in the reference t
125. ntribute to it 1 3 Disclaimer Argo data are published without any warranty express or implied The user assumes all risk arising from his her use of Argo data Argo data are intended to be research quality and include estimates of data quality and accuracy but it is possible that these estimates or the data themselves may contain errors It is the sole responsibility of the user to assess if the data are appropriate for his her use and to interpret the data data quality and data accuracy accordingly Argo welcomes users to ask questions and report problems to the contact addresses listed on the Argo internet page Argo data are continuously managed the user should be aware that after he downloaded data those data may have been updated on Argo data server 1 4 Further information sources and contact information Argo website http www argo net If you detect any problem in the Argo data set please give us your feedback via support argo net Argo data management User s manual ul 1 5 Argo program data management context The objective of Argo program is to operate and manage a set of 3000 floats distributed in all oceans with the vision that the network will be a permanent and operational system The Argo data management group is creating a unique data format for internet distribution to users and for data exchange between national data centres DACs and global data centres GDACs Profile data metad
126. number 1 ftp ftp ifremer fr ifremer argo dac FTP root number 2 ftp usgodae usgodae org pub outgoing argo dac GDAC node CORIOLIS file latitude max latitude min longitude max longitude min profiler type institution date update file path and file name on the ftp site Fill value none this fiel is mandatory latitude max latitude min longitude max longitude min extreme locations of the float Fill values 99999 profiler type type of profiling float as described in reference table 8 Fill value blank institution institution of the profiling float described in reference table 4 Fill value blank date update date of last update of the file YYYYMMDDHHMISS Fill value blank Trajectory directory format example Title Trajectory directory file of the Argo Global Data Assembly Center Description The directory file describes all trajectory files of the argo GDAC ftp site 3t Project ARGO Format version 2 0 3t Date of update 20031028075500 3t FTP root number 1 ftp ftp ifremer fr ifremer argo dac 3t FTP root number 2 ftp usgodae usgodae org pub outgoing argo dac GDAC node CORIOLIS file latitude max latitude min longitude max longitude min profiler type institution date update Argo data management User s manual so aoml 13857 13857_traj nc 1 25 0 267 16 032 18 5 0845 A0 20030214155117 aoml 13857 13857_traj nc
127. nventions Relative julian days with decimal part as part of day JULD FIRST LOCATION FillValue 999 999 char JULD FIRST LOCATION STATUS N CY CLE JULD FIRST LOCATION STATUS conv entions Argo reference table 19 JULD FIRST LOCATION STATUS FillV alue double JULD_LAST_LOCATION N_CYCLE JULD LAST LOCATION long name Date of latest location JULD LAST LOCATION standard name time JULD LAST LOCATION units days since 1950 01 01 00 00 00 UTC JULD LAST LOCATION conventions Relative julian days with decimal part as part of JULD LAST LOCATION FillValue 999 999 char JULD LAST LOCATION STATUS N CY CLE JULD LAST LOCATION STATUS conve ntions Argo reference table 19 JULD LAST LOCATION STATUS FillVa lue double JULD LAST MESSAGE N CYCLE JULD LAST MESSAGE long name Date of latest float message received JULD LAST MESSAGE standard name time JULD LAST MESSAGE units days since 1950 01 01 00 00 00 UTC JULD LAST MESSAGE conventions Relative julian days with decimal part as part of JULD LAST MESSAGE FillValue29999 99 char JULD LAST MESSAGE STATUS N CYC LE JULD LAST MESSAGE STATUS conven tions Argo reference table 19 JULD LAST MESSAGE STATUS FillVal Status flag on JULD date and time The flag scale is described in reference table 19 Example 2 Value is transmitted by the float Julian day UTC of the ear
128. oats that profile on descent and then move back up to drift pressure Time JULD DEEP ASCENT START 551 575 unassigned em for specific timing events around DAST 576 599 see above Any measurement recorded during table transition towards AET 601 625 unassigned Reserved for specific timing events around AET 676 699 see above Any measurement recorded during table transition towards TST 701 Transmission start time directly APEX transmitted by APEX float Earliest time of all messages All floats received by telecommunications system may or may not have a location fix Time JULD FIRST MESSAGE times and locations during All floats drift Should be listed in chronological order ERN Latest time of all messages All floats received by telecommunications system may or may not have a location fix Time J ULD LAST MESSAGE RR UM a 7 alat RR table transition towards TET 801 825 unassigned Reserved for specific timing events around TET E fl 90 1 flag p Argo data management User s manual 77 Configuration phase 902 Last time before float recovery For floats that have been recovered it is important to know when this occurred This time in the J ULD array will be the last time before the float was recovered Determined by inspection of data Pressure offset used to correct APEX APEX pressure measurements 3 16 Reference table 16 vertical sampli
129. of 9 missing are NOT USED in the computation other QC flag values are BAD data The computation should be taken from lt ADJUSTED QC if available and from lt QC otherwise No QC performed N 100 All profile levels contain good data 75 lt N lt 100 50 lt N lt 75 25 lt N lt 50 0 lt N lt 25 N 0 No profile levels have good data WD S Example a TEMP profile has 60 levels 3 levels contain missing values 45 levels are flagged as 1 levels are flagged as 2 7 levels are flagged as 4 3 levels are flagged as 9 missing Percentage of good levels 45 5 57 100 87 7 PROFILE TEMP QC Argo data management User s manual ULUOIOCO 6 IOOUOOO CAO w SQqQqgGNq gq0q0s030q0212121 3 3 Reference table 3 parameter code table The following table describes the parameter codes used for Argo data management long ELECTRICAL CONDUCTIVITY standard name sea Water electrical conductivity unit mhos m 8 5 f C Form at FORTR AN For mat resoluti Fill value 99999 f BPHASE_DOXY sensorXSBE43 Uncalibrated phase shift reported by oxygen sensor degree PRES SEA PRESSURE sea water pressure decibar 0 f 12000 f 99999 f PSAL PRACTICAL SALINI
130. of the principal investigator PI NAME FillValue Name of the principal investigator in charge of the profiling float Example Yves Desaubies STATION PARAMETERS char STATION PARAMETERS N PROF N PARAM STRING16 STATION PARAMETERS long name List of available parameters for the station STATION PARAMETERS conventions Argo reference table 3 STATION PARAMETERS FillValue List of parameters contained in this profile The parameter names are listed in reference table 3 Examples TEMP PSAL CNDC TEMP temperature PSAL practical salinity CNDC conductvity CYCLE NUMBER int CYCLE NUMBER N PROF CYCLE NUMBER long name Float cycle number CYCLE NUMBER conventions 0 N 0 launch cycle if exists 1 first complete cycle CYCLE NUMBER FillValue 99999 Float cycle number A profiling float performs cycles each cycle it performs an ascending vertical profile a subsurface drift and a surface drift some cases it also performs a descending vertical profile 0 is the number of the launch cycle The subsurface drift of the cycle 0 may not be complete Argo data management User s manual m 1 is the number of the first complete cycle Example 10 cycle number 10 DIRECTION char DIRECTION N_PROF DIRECTION long_name Direction of the station profiles DIRECTION conventions A ascending profiles D descen
131. ompressed file for each DAC Example ftp ftp ifremer fr ifremer argo etc argo zip dac aoml tar gz The compressed index of profile files ftp ftp ifremer fr ifremer argo etc argo zip dac ar index global proftxt gz Geo directory e Onecompressed file for each ocean Example ftp ftp ifremer fr ifremer argo etc argo zip geo atlantic ocean tar gz Latest data directory The compressed latest data directory ftp ftp ifremer fr ifremer argo etc argo zip latest_data latest_data tar gz A DAC can push to GDAC a compressed file containing a series of files The GDAC will process all its content This is useful to submit an important batch of files example delayed mode data The compressed file is a tar ed file or directory compressed with gzip Argo data management User s manual 90 Compressed file naming convention XXX tar gz compressed file name with no specific requirement e tar tar suffix e gz gzip suffix Example coriolis 201210 DelayedMode tar gz Argo data management User s manual
132. orded and the value of the real time QC flag to be applied to each observation of this parameter during that period The problem is reported in the ANOMALY field of the meta data file Who when how to remove floats from the greylist In collaboration with the PI of the float a DAC removes a float from the greylist when delayed mode quality control was performed and the suspicious sensor s observations could be recovered after adjustment If the delayed mode quality control decided that the sensor observation cannot be recovered the float remains in the greylist How users should use the greylist The greylist provides an easy way to get information on suspicious floats However the best information on a float s sensors bad behaviour is recorded in the ANOMALY field of the meta data file 6 2 2 Greylist files collection Each DAC maintains a greylist that is submitted to the GDAC for updates The DACs greylist are collected by the GDAC and merged into a global Argo greylist Greylist file collection from DAC to GDAC 1 Query xxx_greylist csv file in each DAC submit directory xxx must be identical to the DAC eg aoml coriolis otherwise the file is rejected 2 Check the format of xxx_greylist csv The whole file is rejected is the format check fails o Floatid valid Argo float id the corresponding meta data file must exist Parameter PSAL TEMP PRES or DOXY Start date YYYYMMDD valid mandatory End date YYYYMMDD
133. pressure Meaning Any averaged measurements made during transition to MC Median value while float is transitioning towards an MC MC minus 6 to MC currently unassigned minus 9 MC minus 10 Any series of measurements recorded while transitioning towards MC e g Provor spy measurements SOLOII pressure time pairs etc Argo data management User s manual 7 MC minus 11 Active adjustment to buoyancy made at this time MC minus 12 to MC currently unassigned minus 24 Measurement Code Table Measure METTI Meaning Transmitted by listed float ment type Value can be code estimated in other floats o Launch time and location of the float All float types 76 99 see above Any measurement recorded during table transition towards DST hori OY around DST E table transition towards FST FST All measurements made at time PROVOR ARVOR when a float first becomes water neutral Time JULD FIRST STABILIZATION eee around FST table transition towards DET la E 204 225 around DET BOE rr descending profile ee table transition towards PST PST All measurements made at time APEX non APF9 APEX APF9 when float transitions to its Park APEX APF9i SIO SOLO or Drift mission This variable is SOLO II NEMO NEMOIR based on float logic based on a descent timer i e SOLO or be CTD based on measurements of pressure WHOI SOLO Argo data management User
134. rmed and Failed The delayed mode QC process is recorded separately from the other QC tests that are performed because of the unique nature of the process and the requirement to record other information about the reference database used When other tests are performed such as the automated real time QC a group of tests are applied all at once In this case instead of recording that each individual test was performed and whether or not the test was failed it is possible to document all of this in two history records The first documents what suite of tests was performed and the second documents which tests in the suite were failed A test is failed if the value is considered to be something other than good i e the resulting QC flag is set to anything other than 1 An example of each is provided If data pass through QC more than once an entry for each passage should be written and the variable N HISTORY updated appropriately Example QC tests performed and failed The example shown here records that the data have passed through real time QC and that two tests failed The encoding of tests performed is done by adding the ID numbers provided in reference table 11 for all tests performed then translating this to a hexadecimal number and recording this result Record 1 Documenting the tests performed Field Sample Explanation HISTORY_INSTITUTION ME Selected from the list in reference table
135. ry file A float technical data file An float s cycle file The DAC s geylist A removal file A compressed file containing a series of above files Each GDAC checks the file format If agreed the file is pushed on the GDAC ftp server or processed Otherwise the file is moved in the reject directory an error message is sent to the DAC contact point Rejected files are kept in the reject directory for one month at least 6 2 Greylist files operations 6 2 1 Greylist definition and management The greylist is used for real time operations to detect a sensor malfunction It is a list of suspicious or malfunctioning float sensors It is managed by each DAC and available from both GDAC ftp site at e ftp usgodae org pub outgoing argo ar greylist txt ftp ftp ifremer fr ifremer argo ar greylist txt The greylist is used in real time QC test 15 to stop the real time dissemination on the GTS of measurements from a sensor that is not working correctly The grey list test is described in Argo quality control manual http www argodatamgt org Media Argo Data Management Argo Documentation General documentation Argo Quality Control manual October 2009 Who when how to add a float in the greylist Under the float s PI supervision a DAC inserts a float in the greylist when a sensor is suspicious or malfunctioning Argo data management User s manual ss For each affected parameter the start end date of malfunction is rec
136. s The ocean codes are used in the GDAC ftp directory files The ocean code is not used in Argo NetCDF files Code Meaning A Atlantic ocean area Indian ocean area P Pacific ocean area e The Pacific Atlantic boundary is 70 W Pacific Indian boundary is 145 E e Atlantic Indian boundary is 20 E Argo data management User s manual 3 14 Reference table 14 technical parameter names All technical parameter names are standardized The list of technical parameter names is available at e http www argodatamgt org Media Argo Data Management Argo Documentation General documentation Data format Argo technical parameter names The naming convention for technical parameters is available at e http www argodatamgt org Media Argo Data Management Argo Documentation General documentation Data format Technical parameter naming convention If new names are required as new variables are reported by a float they must be added to this table before they will be accepted Request for new names can be sent to argo dm chairman jcommops org for approval and inclusion Older style files will be accepted for a short time and then all technical files must use approved names for standardized variables Argo data management User s manual n 3 15 Reference Table 15 codes of trajectory measurements performed within a cycle Dashed
137. s is clearly indicated B Data have been scrutinized and evaluated against a Measures are completely automated or defined and documented set of measures The documentation is not widely available process is often automated i e has no human intervention and the measures are published and The measures have been tested on independent widely available data sets for completeness and robustness and are widely accepted Data have been scrutinized fully including intra Procedures are not published or widely available record and intra dataset comparison and consistency Procedures have not undergone full scrutiny and checks Scientists have been involved in the testing evaluation and brought latest knowledge to bear The procedures are published widely available and Data are fully quality controlled peer reviewed widely accepted and are widely accepted as valid Documentation is complete and widely available Data state indicator recommended use The following table describes the processing stage of data and the value to be assigned the data state indicator DS Indicator It is the concatenation of level and class described above Processing Stage 05 1 Data pass through a communications system and arrive at a processing centre The data resolution is the 0 note 1 highest permitted by the technical constraints of the floats and communications system 2 The national centre assembles all of the r
138. s transmitted by the float Julian day UTC when float transitions to its Deep Park or Deep Drift mission This variable is based on float logic based on a descent timer i e SOLO or be based on measurements of pressure i e Provor Example 18833 8013889885 July 25 2001 19 14 00 Status flag on JULD date and time The flag scale is described in reference table 19 Example 2 Value is transmitted by the float Julian day UTC of the beginning of the float s ascent to the surface Example 18833 8013889885 July 25 2001 19 14 00 Status flag on JULD date and time The flag scale is described in reference table 19 Example 2 Value is transmitted by the float Julian day UTC when float begins its rise to drift pressure Typical for profile on descent floats Example 18833 8013889885 July 25 2001 19 14 00 Argo data management User s manual JULD_DEEP_ASCENT_S TART_STATUS JULD_ASCENT_END JULD_ASCENT_END_ST ATUS JULD_TRANSMISSION_ START JULD_TRANSMISSION_ START_STATUS JULD_FIRST_MESSAGE e Deep ascent start date of the cycle JULD_DEEP_ASCENT_START standard_ name time JULD DEEP ASCENT START units days since 1950 01 01 00 00 00 UTC JULD DEEP ASCENT START conventio ns Relative julian days with decimal part as part of day JULD DEEP ASCENT START FillValue 999999 char JULD_DEEP_ASCENT_START_STATUS N_CYCLE JULD_DEEP_ASCENT_START_STATUS c onvent
139. should be greater than START PRES Example 1757 0 HISTORY PREVIOUS VALUE float HISTORY PREVIOUS VALUE N HIS TORY N PROF HISTORY PREVIOUS VALUE long n ame Parameter Flag previous value before action HISTORY PREVIOUS VALUE FillVal ue 99999 f Parameter or flag of the previous value before action Example 2 probably good for a flag that was changed to 1 good HISTORY QCTEST char HISTORY QCTEST N HISTORY N PROF STRING16 HISTORY QCTEST long name Documentation of tests performed tests failed in hex form HISTORY QCTEST conventions Write tests performed when ACTION QCP tests failed when ACTION QCF HISTORY _QCTEST FillValue This field records the tests performed when ACTION is set to QCP qc performed the test failed when ACTION is set to QCF qc failed The QCTEST codes are describe in reference table 11 Example 0A in hexadecimal form The usage of the History section is described in 5 Using the History section of the Argo netCDF Structure Argo data management User s manual d Argo trajectory files contain all received locations of Argo floats The trajectory file also contains cycle timing information important for making velocity calculations These times may come directly from the float in real time from calculations based on float information in real time from the satellite system in real time or from estimations
140. ssing HISTORY STEP conventions Argo reference table 12 HISTORY STEP FillValue Code of the step in data processing for this history record The step codes are described in reference table 12 Example ARGQ Automatic QC of data reported in real time has been performed HISTORY SOFTWARE char HISTORY SOFTWARE HISTORY N PROF STRING4 HISTORY SOFTWARE long name Name of software which performed action HISTORY SOFTWARE conventions Institution dependent HISTORY SOFTWARE FillValue Name of the software that performed the action This code is institution dependent Example WJO HISTORY SOFTWARE RELEASE char HISTORY SOFTWARE RELEASE N HISTORY PROF STRING4 HISTORY SOFTWARE RELEASE lon g name Version release of software which performed action HISTORY SOFTWARE RELEASE con ventions Institution dependent HISTORY SOFTWARE RELEASE Fil Value Version of the software This name is institution dependent Example 1 0 HISTORY_REFERENCE char HISTORY_REFERENCE N_HISTORY N_PROF STRING64 HISTORY REFERENCE long name Reference of database HISTORY REFERENCE conventions Institution dependent HISTORY REFERENCE FillValue Code of the reference database used for quality control in conjunction with the software This code is institution dependent Example WOD2001 HISTORY DATE char HISTORY DATE N HISTORY N PROF DATE TIME
141. t behaviours to record with park depth varying between 1500 2000 and Missi 0 ese new behaviours requires a new mission number This is in addition to the info contained in mission 0 pre deployment or launch CONFIG_PARAMETER_NAME CONFIG_ParkPressure_dBAR CONFIG PARAMETER VALUE 1500 CONFIG_MISSION_NUMBER 1 CONFIG PARAMETER NAME CONFIG ParkPressure dBAR CONFIG PARAMETER VALUE 2000 CONFIG MISSION NUMBER 2 CONFIG PARAMETER NAME CONFIG _ParkPressure_dBAR CONFIG PARAMETER VALUE 1700 CONFIG MISSION NUMBER 3 A further example for a float with multiple missions is shown below For this float the only change to the mission behaviour is the depth at which the float parks with changes in two configuration parameters However all configuration parameters from mission 1 must still be reported for each subsequent mission even those that do not change In this example there is one configuration mission 0 variable which is set before launch then there are another 6 variables that may change and control the float behaviour in subsequent missions missions 1 to n In this example even though only Argo data management User s manual 50 CONFIG_ParkPressure_dBAR CONFIG_ParkPistonPosition_COUNT are changing the other mission variables are also repeated for each subsequent mission CONFIG PARAMETER NAME Mission Settings N CONF PARAM N
142. t the data contained in this file are managed according to the policy described in the Argo data management handbook Example 1 0 Date and time UTC of creation of this file Format YYYYMMDDHHMISS Example 20011229161700 December 29 2001 16 17 00 Date and time UTC of update of this file Format YYYYMMDDHHMISS Example 20011230090500 December 30 2001 09 05 00 WMO float identifier WMO is the World Meteorological Organization This platform number is unique Example 6900045 Transmission identifier of the float Comma separated list for multi beacon transmission Example 22507 the float is equipped with one ARGOS beacon 22598 22768 the float is equipped with 2 ARGOS beacons Argo data management User s manual TRANS_SYSTEM TRANS SYSTEM ID TRANS FREQUENCY POSITIONING SYSTEM PLATFORM FAMILY PLATFORM TYPE PLATFORM MAKER FIRMWARE VERSION MANUAL VERSION FLOAT SERIAL NO STANDARD FORMAT ID DAC FORMAT ID char TRANS SYSTEM N TRANS SYSTEM STRING16 TRANS SYSTEM long name elecommunications system used TRANS SYSTEM FillValue char TRANS SYSTEM ID N TRANS SYSTEM STRING32 TRANS SYSTEM ID long name FRe Program identifier used by the transmission system TRANS SYSTEM ID FillValue char TRANS FREQUENCY STRING16 TRANS FREQUENCY long name fhe fFrequency of transmission from the float TRANS FREQUENCY units
143. table SCIENTIFIC_CALIB_DATE char SCIENTIFIC CALIB DATE N PROF N CALIB N_PARAM DATE TIME SCIENTIFIC CALIB DATE FillValue SCIENTIFIC CALIB DATE long name Date of calibration 2 2 7 History information for each profile Date of the calibration Example 20011217161700 This section contains history information for each action performed on each profile by a data centre Each item of this section has a N HISTORY number of history records N PROF number of profiles dimension A history record is created whenever an action is performed on a profile The recorded actions are coded and described in the history code table from the reference table 7 Argo data management User s manual gt On the GDAC multi profile history section is empty to reduce the size of the file History section is available on mono profile files or in multi profile files distributed from the web data selection Name HISTORY_INSTITUTION Definition char HISTORY_INSTITUTION N_HISTOR Y N_PROF STRING4 HISTORY INSTITUTION long name Institution which performed action HISTORY INSTITUTION convention S Argo reference table 4 HISTORY INSTITUTION FillValue Comment Institution that performed the action Institution codes are described in reference table 4 Example ME for MEDS HISTORY STEP char HISTORY STEP N HISTORY N PROF STRING4 HISTORY STEP long name Step in data proce
144. tandard name latitude LATITUDE units degree north LATITUDE FillValue 99999 LATITUDE valid min 90 LATITUDE valid max 90 LATITUDE axis Y double LONGITUDE N MEASUREMENT LONGITUDE long name Longitude of each location LONGITUDE standard name longitude LONGITUDE units degree east LATITUDE LONGITUDE comment Julian day of the location or measurement The integer part represents the day the decimal part represents the time of the measurement Date and time are in universal time coordinates The julian day is relative to REFERENCE DATE TIME Example 18833 8013889885 July 25 2001 19 14 00 Status flag on JULD date and time The flag scale is described in reference table 19 Example 2 Value is transmitted by the float Quality flag on J date and time The flag scale is described in the reference table 2 Example 1 the date and time seems correct Adjusted julian day of the location or measurement The integer part represents the day the decimal part represents the time of the measurement Date and time are in universal time coordinates The julian day is relative to REFERENCE DATE TIME The date may be adjusted due to float clock drift or expert review Example 18833 8013889885 July 25 2001 19 14 00 Status flag on JULD date and time The flag scale is described in reference table 19 Example 2 Value is transmitted by the float Quality flag on
145. that corresponds to the information contained in the current index Errors may be found in CYCLE NUMBER INDEX variable which are corrected and contained in this variable Example 17 means information for the 17 cycle of the float is contained in this index Indicates if the trajectory cycle contains real time adjusted or delayed mode data A delayed mode cycle means the positions times cycle number pressure temperature and salinity if measured have been quality controlled Additional parameters like oxygen may not be quality controlled Floats often have delayed mode data only after they die but can have both delayed mode and real time data When this occurs two trajectory files exist a real time file R with only real time data for all the cycles in the float record and a delayed mode file D with both real time and delayed mode data for all the cycles that have been delayed mode quality controlled Floats can be adjusted in real time with adjusted time values only in the JULD_ADJ USTED variable and its associated STATUS and QC variables This occurs when floats are corrected in real time for clock drift Examles R real time data D delayed mode data real time data with JULD ADJUSTED values This section contains history information for each action performed on each measurement Each item of this section has a N HISTORY number of history records dimension HISTORY INSTITUTION Definition char
146. ue to clock drift The times can be adjusted either in real time or in delayed mode due to clock drift or estimation of times based on float behaviour by a float expert The JULD ADJUSTED STATUS variable indicates how the JULD ADJUSTED value was filled and indicates whether the time is estimated or measured The ADJUSTED QC contain the QC flags for the adjusted times This may lead to times where JULD ADJUSTED is filled but JULD contains FillValue That is because the time is estimated rather than measured In R mode no times are adjusted and JULD is filled while JULD_ADJUSTED is contains Fill Value In A mode JULD_ADJUSTED contains real time correction of clock drift and real time estimates if applicable In D mode JULD_ADJUSTED is filled with the best estimate of float timing after expert review If no clock drift is determined to have occurred and no other adjustments to event times are needed then all values found in should be replicated in JULD ADJUSTED CYCLE NUMBER contains the cycle number of the cycle that is assigned in real time This cycle number must match the profile cycle number which is the number recorded in the CYCLE NUMBER N PROP variable in profile files CYCLE NUMBER INDEX indicates which cycle number information is contained in that index of the N CYCLE array For example CYCLE NUMBER INDEX 4 23 means the 4th element of all N CYCLE variables is associated with the WMO_003 nc profile file This mi
147. utes The global attributes section is used for data discovery The following 8 global attributes should appear in the global section The NetCDF Climate and Forecast CF Metadata Conventions version 1 6 5 December 2011 are available from e http cf pcmdi lnl gov documents cf conventions 1 6 cf conventions pdf global attributes title Argo float technical data file institution CSIRO source Argo float history 2011 04 22T06 00 00Z creation references http www argodatamgt org Documentation comment free text user manual version 3 03 Conventions Argo 3 0 CF 1 6 Argo data management User s manual 2 5 2 Dimensions and definitions Name Definition Comment DATE_TIME DATE_TIME 14 This dimension is the length of an ASCII date and time value Date and time values are always in universal time coordinates UTC Date_time convention is YYYYMMDDHHMISS YYYY year MM month DD day HH hour of the day MI minutes SS seconds Examples 20010105172834 January 5 2001 17 28 34 19971217000000 December 17 1997 00 00 00 STRING128 STRING128 128 String dimensions from 2 to 128 STRING32 STRING32 32 STRING8 STRING8 8 STRING4 STRING4 4 STRING2 STRING2 2 N_TECH_PARAM N_TECH_PARAM Number of technical parameters UNLIMITED 2 5 3 General information on the technical data file This section contains information about the technical data
148. valid fill value Flag valid argo flag Comment free DAC valid DAC mandatory Oo O O O 3 Remove all the floats of the DAC from the GDAC grey list and add the content of the submitted xxx greylist csv file Note after each submission a copy of the Argo greylist is stored in etc greylist ar greylist txt YYYYMMDD The global Argo greylist is sorted by DAC PLATFORM CODE and START DATE in alphabetical order Argo data management User s manual 6 3 GDAC files removal A DAC can ask the GDAC to remove individual profile trajectory technical or meta data files A removal file is submitted to GDAC which will perform the removals The removal file contains one line per file to remove Removal file collection from DAC to GDAC Query xxx removal txt file in each DAC submit directory xxx must be identical to the DAC eg aoml coriolis otherwise the file is rejected Check format of xxx removal txt The whole file is rejected is the format check fails o Filename valid Argo file name the corresponding meta data file must exist for this DAC Move all the named files from into a etc removed directory The removed files are kept for 3 months in etc removed directory and erased after that delay Once a month a compressed version of dac geo and latest data directories is distributed on ftp ftp ifremer fr ifremer argo etc argo zip DAC directory c
149. y sensor 859 Profiling Float NEMO no conductivity 860 Profiling Float NEMO SBE conductivity sensor 861 Profiling Float NEMO FSI conductivity sensor Argo data management User s manual 3 9 Reference table 9 positioning system Code Description ARGOS ARGOS positioning system GPS GPS positioning system RAFOS RAFOS positioning system IRIDIUM Iridium positioning system 3 10 Reference table 10 transmission system Code Description ARGOS Argos transmission system IRIDIUM Iridium transmission system ORBCOMM Orbcomm transmission system 3 11 Reference table 11 QC test binary IDs This table is used to record the result of the quality control tests in the history section The binary IDs of the QC tests are used to define the history variable HISTORY_QCTEST whose value is computed by adding the binary ID together then translating to a hexadecimal number An example is given on 5 3 The test numbers and the test names are listed in the Argo Quality Control Manual 2 1 Argo Real Time Quality Control Test Procedures on Vertical Profiles and 22 Argo Real Time Quality Control Test Procedures on Trajectories See http www argodatamgt org Documentation Test Qc Test name number test binary ID 1 Platform Identification test 2 4 Impossible Date test 3 8

Argo user's manual - Archimer

Contents

Download Pdf Manuals

Related Search

Related Contents