Home

USER'S MANUAL - Argo Data Management

Contents

1. char DATE CREATION DATE TIME DATE CREATION comment Date of file creation DATE CREATION 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 3 3 General information on the float This section contains general information on the float PLATFORM NUMBER PROJECT NAME NAME TRAJECTORY PARAMETERS Argo data management Definition 23 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 trajectory File format version Example 2 2 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 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 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 char PLATFORM NUMBER STRING8 PLATFORM NUMBER long name Float unique identifier PLATFORM NUMBER conventions WMO float iden
2. lt PARAM gt QC FillValue float lt PARAM gt _ADJUSTED N_MEASUREMENT lt PARAM gt _ADJ USTED long_name lt X gt lt PARAM gt _ADJ USTED _FillValue X lt PARAM gt _ADJ USTED units lt X gt lt PARAM gt _ADJ USTED valid_min X lt PARAM gt _ADJ USTED valid_max X PARAM ADJUSTED comment lt X gt lt PARAM gt _ADJ USTED C_format lt X gt PARAM ADJUSTED FORTRAN format lt gt lt PARAM gt _ADJ USTED resolution X char lt PARAM gt _ADJ USTED_QC N_MEASUREMENT lt PARAM gt _ADJUSTED_QC long_name quality flag lt PARAM gt _ADJUSTED_QC conventions Argo reference table 2 lt PARAM gt _ADJUSTED_QC _ FillValue float lt PARAM gt _ADJ USTED_ERROR N_MEASUREM ENT lt PARAM gt _ADJUSTED_ERROR long_name lt gt Argo data management Position accuracy received from the positioning system The location classes from ARGOS are described in the reference table 5 Example 3 for a latitude and longitude accuracy lt 150 m 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 measurement For one cycle number there are usually several locations measurement received Example 17 for measurements performed during the 17 cycle of the float Provides the
3. 2 4 Meta data format version 2 2 An Argo meta data file contains information about an Argo float For file naming conventions see 4 1 2 4 1 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 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 8 STRING8 STRING8 STRING4 STRING4 STRING2 STRING2 N_CYCLES N_CYCLES lt int Number of different nominal cycles value gt This value is usually set to 1 all the cycles are programmed to be the same However some floats may perform cycles with different programming Example a float is programmed to perform regularly 4 cycles with 400 decibar profiles and the 5 cycle with 2000 decibar profile In that case N CYCLE is set to 2 N CYCLES 2 The first N CYCLE has a REPETITION RATE of 4 and the second has a REPETITION RATE of 1 N PARAM PARAM int Number of parameters measured or calculated for a pressure sample value Examples pressure temperature N PARAM 2 pressure temperature salinity N PARAM 3
4. 7 Notused Not used 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 1s defined as the percentage of levels with good data where o QC flag values of 1 2 5 or 8 are GOOD data o QC flag values of 9 missing are NOT USED in the computation o Allother QC flag values are BAD data The computation should be taken from lt PARAM ADJUSTED QC gt if available and from lt PARAM gt otherwise n Meaning No QC performed A IN 100 All profile levels contain good data B 7596 lt N lt 100 D 25 lt N lt 50 9 9 0 O Example A TEMP profile has 60 levels 3 levels contain missing values 45 levels are flagged as 1 o 5 levels are flagged as 2 o 7levels are flagged as 4 o 3levels are flagged as 9 missing Percentage of good levels 45 5 57 100 87 7 PROFILE TEMP QC Argo data management User s manual 61 3 3 Reference table 3 parameter code table The following table describes the parameter codes used for Argo data management Code Parameter Comment Unit Valid Valid Format Fill value long name min max FORTRAN_ Format resolution 0 1 60 1 10 4 99999 f F10 4 0 0001f 0 12000 f 967 1f 99999 f F7 1 0 1f n situ measurement psu
5. Parking Depth Time Progress code __Meaning descent start end of the surface drift beginning of drift at parking pressure end of drift at parking pressure start of ascent from maximal pressure ascent end start of the surface drift start of transmission end of transmission best estimate of parking pressure can be either measured or from meta data More detail may be available in the metadata and technical files 100 descending phase between codes 1 and 2 parking pressure phase between codes 2 and 3 descent to maximum pressure between codes 3 and 4 ascent to surface between codes 4 and 5 surface drift phase between code 5 and code 1 of the following cycle On N On BR OO PO Codes from 1 to 99 are specific events They occur more than once per cycle Codes 100 and above describe phases of the cycle They can occur multiple times some are measured events some may be estimated Argo data management User s manual lt lt lt 4 Data access The whole Argo data set is available in real time and delayed mode from the global data centres GDACSs The internet addresses are http www usgodae org argo argo html http www argodatamgt org The FTP addresses are ftp usgodael fnmoc navy mil pub outgoing argo e ftp ftp ifremer fr ifremer argo The 2 GDACs offer the same data set that is mirrored in real t
6. Example History entry to record decoding of the data Field Sample Explanation Selected from the list in reference table 4 Selected from the list in reference table 12 This field does not apply HISTORY_SOFTWARE_RELEAS FillValue This field does not apply E HISTORY_REFERENCE FillValue This field does not apply HISTORY_DATE The year month day hour minute second that 0000 the process ran HISTORY IP J Selected from the list in reference table 7 This field does not apply This field does not apply This field does not apply This field does not apply This field does not apply Argo data management User s manual 5 3 Recording QC Tests Performed 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 1 the resulting QC flag
7. However some floats may perform cycles with different programming Example a float is programmed to perform regularly 4 cycles with 400 decibar profiles and the 57 cycle with a 2000 decibar profile In that case N CYCLE is set to 2 The first N CYCLE has a REPETITION RATE of 4 and the second has a REPETITION RATE of 1 Total time of a cycle This time includes the descending time the parking time the ascending time and the surface time Unit decimal hour Example 240 hours for a ten day cycle Time spent at the parking pressure This time does not include the descending and ascending times Unit decimal day Example 222 for 9 days and 6 hours at parking pressure Time spent in descent Unit decimal hour Example 8 5 for 8 hours 30 minutes of descending Time spent in ascent Unit decimal hour Example 7 5 for 7 hours 30 minutes of descending Time spent on the surface surface drift Unit decimal hour Example 10 for a 10 hours surface drift Pressure of the subsurface drift Unit decibar Example 1500 0 for a subsurface drift at 1500 0 decibars Deepest pressure sampled in the ascending profile Unit decibar Example 2000 0 for an ascending profile starting at 2000 0 decibar Deepest pressure sampled in the descending profile Unit decibar Example 500 0 for a descending profile ending at 500 0 decibar User s manual 389 2 4 8 Highly desirable meta d
8. year MM month DD day HH hour of the day 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 256 STRING32 STRING32 32 STRING8 STRING8 STRING4 STRING4 STRING2 STRING2 N_TECH_PARAM N_TECH_PARAM Number of technical parameters UNLIMITED Argo data management User s manual S 2 7 2 General information on the technical data file This section contains information about the technical data file itself PLATFORM_NUMBER DATA_TYPE FORMAT_VERSION HANDBOOK_VERSION DATA_CENTRE DATE_CREATION DATA_UPDATE Argo data management Definition char PLATFORM_NUMBER STRING8 PLATFORM NUMBER long name Float unique identifier PLATFORM NUMBER convention s WMO float identifier AQI PLATFORM NUMBER FillValue char DATA TYPE STRING32 DATA TYPE comment Data type DATA TYPE FillValue char FORMAT VERSI ON STRINGA FORMAT VERSION comment File format version FORMAT VERSION FillValue char HANDBOOK VERSI ON STRING4 HANDBOOK VERSION comment Data handbook version HANDBOOK VERSION 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 DATE CREATION DATE TIME DATE CREATION comment Date
9. CLOCK DRIFT float CLOCK DRIFT CLOCK DRIFT long name The rate of drift of the float clock CLOCK DRIFT units decisecond day CLOCK DRIFT FillValue 99999 f PLATFORM MODEL char PLATFORM MODEL STRING16 PLATFORM MODEL long name Model of the float PLATFORM MODEL FillValue PLATFORM MAKER char PLATFORM MAKER STRING256 PLATFORM MAKER long name The name of the manufacturer PLATFORM MAKER FillValue INST REFERENCE char INST REFERENCE STRING64 INST REFERENCE long name Instrument type INST REFERENCE conventions Brand type serial number INST REFERENCE FillValue WMO INST TYPE char WMO INST 5 4 WMO INST TYPE long name Coded instrument Argo data management Comment 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 Name of the telecommunication system from reference table 10 Example ARGOS Program identifier of the telecommunication subscription Use N A when not applicable eg Iridium or Orbcomm Example 38511 is a program number for all the beacons of an ARGOS customer Frequency of transmission from the float Unit hertz Example 1 44
10. Example of a profiling float performing temperature measurements with adjusted values of temperature Parameter definition PRES TEMP TEMP ADJUSTED float PRES N PROF N LEVELS PRES long name SEA PRESSURE sea surface 0 PRES FillValue 99999 f PRES units decibar PRES valid_min 0 PRES valid_max 1200 f PRES comment In situ measurement sea surface 0 PRES C format 7 1f PRES FORTRAN format F7 1 PRES resolution 0 1f char PRES QC N PROF LEVELS PRES QC long name quality flag PRES QC conventions Argo reference table 2 PRES QC FillValue float TEMP N PROF N LEVELS TEMP long name SEA TEMPERATURE TEMP FillValue 99999 f TEMP units degree Celsius TEMP valid min 2 f TEMP valid max 40 f TEMP comment In situ measurement TEMP C format 9 3f TEMP FORTRAN_format F9 3 TEMP resolution 0 001f char TEMP_QC N_PROF N_LEVELS TEMP_QC long_name quality flag TEMP_QC conventions Argo reference table 2 TEMP QC FillValue float TEMP ADJUSTED N PROF N LEVELS TEMP ADJUSTED long name ADJ USTED SEA 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 comment Adjusted parameter TEMP ADJUSTED C format 96 9 3f TEMP ADJUSTED FORTRAN format F9 3 TEMP ADJUSTED resolution 0 001f
11. FillValue 99999 LONGI TUDE valid min 180 LONGITUDE valid max 180 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 STAGE MEASUREMENT CYCLE STAGE long name Stage of the measurement in the cycle CYCLE STAGE conventions 100 descending 200 parking pressure 300 descent to maximum pressure ascent to surface 500 surface drift CYCLE STAGE FillValue 99999 float PARAM N MEASUREMENT PARAM long name lt X gt lt gt FillValue X lt PARAM gt units lt X gt PARAM valid min X PARAM valid max X lt PARAM gt comment lt X gt lt PARAM gt C_format lt gt lt PARAM gt FORTRAN_ format lt X gt lt PARAM gt resolution 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
12. The data resolution is the highest permitted by the technical constraints of the floats and communications system 2 The national centre assembles all of the raw information into a complete profile located in space and time 3 The national centre passes the data through automated QC procedures and prepares the data for 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 These are then distributed to users in near real time Argo data management I ndicator S OA note 1 1A note 2 2B note 3 User s manual 65 5 Data are reviewed by Pls and returned to processing centres The processing 2C centres forward the data to the global Argo servers 6 Scientists accept data from various sources combine them as they see fit with other B 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 3B note 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 3C with some time delay for distributi
13. User s manual PREDEPLOYMENT_CALIB _COMMENT Argo data management Calibration coefficients for this equation PREDEPLOYMENT CALIB COEFFICIENT FillValue char Comments applying to this parameter PREDEPLOYMENT CALIB COMMENT N PARAM STRING2 calibration 56 Example PREDEPLOYMENT CALIB COMMENT long name The sensor is not stable Comment applying to this parameter calibration PREDEPLOYMENT CALIB COMMENT FillValue User s manual 65654 2 4 7 Float cycle information This section contains information on the cycle characteristics of the float The values included in this section are programmed or estimated They are not measured Each value has CYCLES dimension Each CYCLE describes a cycle configuration REPETITION_RATE CYCLE_TIME PARKING_TIME DESCENDING PROFILING _TIME ASCENDING_PROFILING_ TIME SURFACE_TIME PARKING_PRESSURE DEEPEST_PRESSURE DEEPEST_PRESSURE_DE SCENDING Argo data management Definition int REPETITION RATE N CYCLES REPETITION RATE long name The number of times this cycle repeats REPETITION RATE units number REPETITION RATE FillValue 99999 float CYCLE TIME N CYCLES CYCLE TIME long name The total time of a cycle descent parking ascent surface CYCLE TIME units decimal hour CYCLE TIME FillValue 99999 f float PARKING TIME N CYCLES PARKING TIME long name The time spent at the parking press
14. contained in the file The list of acceptable data types is in the reference table 1 Example Argo meta data File format version Example 2 3 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 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 User s manual 2 5 3 Float characteristics This section contains the main characteristics of the float Definition Comment PLATFORM NUMBER char PLATFORM NUMBER STRINGS8 WMO float identifier PLATFORM NUMBER long name Float unique WMO is the World Meteorological identifier Organization PLATFORM NUMBER conventions WMO float identifier This platform number is unique Example 6900045 PLATFORM NUMBER FillValue Argo data management User s manual lt 2 5 4 Configuration parameters This section contains the configuration parameters for a float For each configuration 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 The parameter names are standardized and availab
15. pressure temperature conductivity salinity N PARAM 4 Argo data management User s manual 2 4 2 General information on the meta data file This section contains information about the whole file Name DATA_TYPE FORMAT_VERSION HANDBOOK_VERSION DATE_CREATION DATE_UPDATE Argo data management Definition char DATA_TYPE STRING16 DATA_TYPE comment Data type DATA TYPE FillValue char FORMAT VERSION STRI NG4 FORMAT VERSI ON comment File format version FORMAT VERSION FillValue char HANDBOOK VERSI ON STRI NG4 HANDBOOK VERSI ON comment Data handbook version HANDBOOK VERSION FillValue char DATE CREATION DATE TIME DATE CREATION comment Date of file creation DATE CREATION 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 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 2 2 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 Date and time UTC of creation of this file Format YYYYMMDDHHMISS Examp
16. Reference table 5 location classes ARGOS ARGOS location classes O accuracy estimation over 1500mradius 1 accuracy estimation better than 1500m radius Cd 2 accuracy estimation better than 500 m radius accuracy estimation better than 250 m radius GPS positioning Argo data management User s manual 64 3 6 Reference table 6 data state indicators Level Descriptor Data are the raw output from instruments without calibration and not necessarily converted to engineering units These data are rarely exchanged 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 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 hermodynamic relationships The data are normally reduced to regular space time intervals with enhanced signal to noise Data have complete geospatial and temporal references Information may have been compressed e g Class Descriptor No scrutiny value judgements or intercomparisons are performed on the data The records are derived directly from the input with no filtering or subsampling Data have been scrutin
17. TIME Example 18833 8013889885 July 25 2001 19 14 00 Quality flag on JULD date and time The flag scale is described in the reference table 2 Example 1 the date and time seems correct 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 Latitude of the profile Unit degree north This field contains the best estimated latitude The latitude value may be improved in delayed mode The measured locations of the float are located in the trajectory file Example 44 4991 44 29 56 76 N Longitude of the profile Unit degree east This field contains the best estimated longitude The longitude value may be improved in delayed mode The measured locations of the float are located in the trajectory file Example 16 7222 16 43 19 92 E 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 Name of the system in charge of positioning the float locations from reference table 9 Examples ARGOS Global quality flag on the PARAM profile PARAM is among the STATION PARAMETERS The overall flag is set to indicate the percentage
18. Yves Desaubies STATION PARAMETERS char STATION PARAMETERS N PROF List of parameters contained in this profile Argo data management User s manual CYCLE_NUMBER DIRECTION DATA_CENTRE DC_REFERENCE DATA_STATE_INDICATOR DATA_MODE INST_REFERENCE FIRMWARE_VERSION WMO_INST_TYPE JULD Argo data management N_PARAM STRING16 STATION_PARAMETERS long_name List of available parameters for the station STATION_PARAMETERS conventions Argo reference table 3 STATION PARAMETERS FillValue 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 char DIRECTION N PROF DIRECTION long name Direction of the station profiles DI RECTI ON conventions A ascending profiles D descending profiles DIRECTION FillValue char DATA PROF STRING2 DATA CENTRE long name Data centre in charge of float data processing DATA CENTRE conventions Argo reference table 4 DATA CENTRE FillValue 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 ST
19. according to the policy described in the Argo data management handbook Example 1 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 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 This section contains general information on each profile Each item of this section has a N PROF number of profiles dimension PLATFORM NUMBER PROJECT NAME Definition char PLATFORM NUMBER N PROF STRING8 PLATFORM NUMBER long name Float unique identifier PLATFORM NUMBER conventions WMO float identifier PLATFORM NUMBER FillValue char PROJECT NAME N PROF STRING64 PROJECT NAME comment Name of the project PROJECT NAME FillValue char NAME N PROF STRING64 NAME comment Name of the principal investigator NAME FillValue Comment WMO float identifier WMO is the World Meteorological Organization This platform number is unique Example 6900045 Name of the project which operates the profiling float that performed the profile Example GYROSCOPE EU project for ARGO program Name of the principal investigator in charge of the profiling float Example
20. char TEMP ADJUSTED QC N PROF N 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 ADJ USTED SEA TEMPERATURE TEMP ADJUSTED ERROR FillValue 99999 f TEMP ADJUSTED ERROR units degree Celsius TEMP ADJUSTED ERROR comment Contains the error on the adjusted values as Argo data management User s manual determined by the delayed mode QC process TEMP ADJUSTED ERROR C_format 9 3f TEMP ADJUSTED ERROR FORTRAN_ format F9 3 TEMP ADJUSTED ERROR resolution 0 001f 2 2 5 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 CALIB number of calibrations N PARAM number of parameters dimension If no calibration is available CALIB is set to 1 all values of calibration section are set to fill values Name Definition Comment PARAMETER char PARAMETER N PROF N CALIB Name of the calibrated parameter The list of PARAM STRING16 parameters is in reference table 3 PARAMET
21. 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 DOXY4 and so Argo data management User s manual Example If a float has one Optode and one SBE oxygen sensor e Use DOXY and TEMP DOXY for Optode 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 e 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 DOXY unit micromole kg DOXY ADJUSTED is the dissolved oxygen concentration corrected for any sensor drift and offset DOXY 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 The Argo oxygen data management is described at http www argodatamgt org Media Argo
22. for the redefined PROFILE PARAM QC variables 20 06 2005 New long name for TEMP DOXY in section 3 3 Claudia Schmid general update of trajectory file history section MEASUREMENT dimension removed Minor typo corrections Annie Wong 3 2 2 usage of PARAM ADJUSTED QC and PARAM QC Reference table 2 updated qc 3 and 4 Thierry Carval 82 2 4 82 3 4 accept adjusted parameters in real time files Thierry Carval 1 3 82 2 3 82 3 4 real time adjusted data Thierry Carval remove erroneous blanks ex Argo reference table 3 21 01 03 2006 Mark Ignaszewski 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 2 1 26 09 2006 Thierry Carval 82 4 3 TRANS SYSTEM ID use N A when not applicable eg Iridium or Orbcomm Argo data management User s manual 2 1 27 11 2006 Thierry Carva 52 4 8 highly desirable metadata PARKING PRESSURE may be empty for floats drifting along a selected density level Claudia Schmid 83 3 use 20 12 for floats equipped with 2 oxygen sensors 4 1 file convention multi profiles cycle EB E Thierry Carva 6 1 greylist file collection 82 2 2 move date creation and date update to general information on profile file section _ o 81 2 new graphic for float cycles de
23. 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 aoml 13857 13857_traj nc 1 25 0 267 16 032 18 5 0845 A0 20030214155117 aoml 13857 13857_traj nc 0 072 17 659 A 0845 AO 20030214155354 13857 13857 0 543 19 622 0845 0 20030214155619 jma 29051 29051 traj nc 32 280 30 280 143 238 140 238 846 A 20030212125117 29051 29051 traj nc 32 352 30 057 143 206 140 115 846 A 20030212125117 2 8 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 A table with a description of each file of the GDAC ftp site This table is a comma separated list Metadata directory format definition Argo data management User s manual 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 usgod
24. from 2 to 256 STRING64 STRING64 STRING32 STRING32 STRING16 STRING16 STRING8 STRING8 STRING4 STRING4 STRING2 STRING2 N_PARAM N_PARAM lt int Number of parameters measured or calculated for a pressure sample value gt Examples pressure temperature N PARAM 2 pressure temperature salinity N PARAM 3 pressure temperature conductivity salinity N PARAM 4 N CONF PARAM CONF PARAM i Number of configuration parameters nt value 64 32 16 8 Argo data management User s manual 2 5 2 General information on the meta data file This section contains information about the whole file Name DATA_TYPE FORMAT_VERSION HANDBOOK_VERSION DATE_CREATION DATE_UPDATE Argo data management Definition char DATA_TYPE STRING16 DATA_TYPE comment Data type DATA TYPE FillValue char FORMAT VERSION STRI NG4 FORMAT VERSI ON comment File format version FORMAT VERSION FillValue char HANDBOOK VERSI ON STRI NG4 HANDBOOK VERSI ON comment Data handbook version HANDBOOK VERSION FillValue char DATE CREATION DATE TIME DATE CREATION comment Date of file creation DATE CREATION 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 41 This field contains the type of data
25. is therefore regular only for later profiles and may be variable if the float is reprogrammed during its mission Argo data management User s manual nl 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 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 Tm 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 representin
26. 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 e Argo website http www argo net e 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 9 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 metadata trajectories and technical data are included in this standardization effort The Argo data formats are based on NetCDF because e 15 widely accepted data format by the user community e tisaself describing format for which tools are widely available e Itisareliable 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 e A descent from surface to a parking pressure e g 1500 decibars e Asubsurface drift at the parking pressure e g 10 days An ascent f
27. management double JULD DESCENT END N CYCLE JULD DESCENT END long name Descent end date of the cycle 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 ULD DESCENT END FillValue 999999 charJULD DESCENT END STATUS N CYCLE JULD DESCENT END STATUS conventions 0 Nominal 1 Estimated 2 Transmitted JULD DESCENT END STATUS FillValue double JULD START TRANSMISSION N CYCLE JULD START TRANSMISSION long name Start date of transmssion JULD START TRANSMISSI ON units days since 1950 01 01 00 00 00 UTC JULD START TRANSMISSI ON conventions Relative julian days with decimal part as part of day JULD START TRANSMISSION FillValue2999999 char JULD START TRANSMISSION STATUS N CYCLE JULD START TRANSMISSION STATUS conventio ns 0 Nominal 1 Estimated 2 Transmitted JULD START TRANSMISSION STATUS FillValue char GROUNDED N CYCLE GROUNDED long_name Did the profiler touch the ground for that cycle GROUNDED conventions Y N U GROUNDED FillValue int CONFIGURATION PHASE NUMBER CYCLE CONFIGURATION PHASE NUMBER long name Phase number of unique cycles performed by the float CONFIGURATION PHASE NUMBER FillValue int CYCLE NUMBER N CYCLEE CYCEE NUMBERedeng name Float eycle char DATA MODE N CYCLE DATA MODE long name Delaye
28. of file creation DATE CREATION 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 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 File format version Example 2 3 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 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 Date and time UTC of creation of this file Format YYYYMMDDHHMI SS 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 User s manual 2 7 3 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
29. s manual 2 2 2 General information on the profile file This section contains information about the whole file Name DATA_TYPE FORMAT_VERSION HANDBOOK_VERSION REFERENCE DATE TIME DATE CREATION DATE UPDATE Definition char DATA TYPE STRING16 DATA TYPE comment Data type DATA TYPE FillValue char FORMAT VERSION STRI NG4 FORMAT VERSI ON comment File format version FORMAT VERSION FillValue char HANDBOOK VERSION STRI NG4 HANDBOOK VERSION comment Data handbook version HANDBOOK VERSION FillValue char REFERENCE DATE TIME DATE TIME REFERENCE DATE TIME comment Date of reference for Julian days REFERENCE DATE TIME conventions YYYYMMDDHHMISS REFERENCE DATE TIME FillValue char DATE CREATION DATE TIME DATE CREATION comment Date of file creation DATE CREATION 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 2 3 General information for each profile 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 profile File format version Example 2 2 Version number of the data handbook This field indicates that the data contained in this file are managed
30. stage in the cycle for each measurement See reference table 15 for conventions on cycle progress within a cycle Example 200 this measurement was performed during the parking pressure stage lt PARAM gt contains the original values of a parameter listed in reference table 3 X this field is specified in the reference table 3 Quality flag applied on each lt PARAM gt values The flag scale is specified in table 2 PARAM ADJUSTED contains the adjusted values derived from the original values of the parameter X this field is specified in the reference table 3 lt PARAM gt _ADJ USTED is mandatory When no adjustment is performed the FillValue is inserted Quality flag applied on each lt PARAM gt _ADJ USTED values The flag scale is specified in reference table 2 PARAM ADJUSTED QC is mandatory When no adjustment is performed the FillValue is inserted PARAM ADJUSTED ERROR contains the error on the adjusted values of the parameter X this field is specified in the reference table 3 PARAM ADJUSTED ERROR is mandatory When no adjustment is performed the FillValue is inserted User s manual PARAM ADJUSTED ERROR FillValue X PARAM ADJUSTED ERROR units eX lt PARAM gt _ADJ USTED_ERROR comment Contains the error on the adjusted values as determined by the delayed mode QC process PARAM ADJUSTED ERROR C format eX PARAM ADJUSTED ERROR FOR
31. the configuration parameter Example 0 See note on floats with multiple configurations Comment on this configuration phase Example This phase follows a 1000 dbar meddie during parking User s manual M Note on floats with multiple configurations Usually an Argo float configuration is valid for the whole life of the float Each cycle is repeated with the same behaviour basic configuration However some floats may be configured to change their behaviour from cycle to cycle changing configuration For the basic configuration CONFIGURATION PHASE NUMBER is set to 1 all the cycles are programmed to be the same For changing configuration CONFIGURATION PHASE NUMBER is used to describe a configuration launch 1500 dbar 2000 dbar configuration phase number In the above example there are 3 configuration phases to record CONFIGURATION PARAMETER PRES ParkPressure dBAR CONFIGURATION PARAMETER VALUE 1500 CONFIGURATION PHASE NUMBER 1 CONFIGURATION PARAMETER NAME PRES ParkPressure dBAR CONFIGURATION PARAMETER VALUE 2000 CONFIGURATION PHASE NUMBER 2 CONFIGURATION PARAMETER NAME PRES ParkPressure dBAR CONFIGURATION PARAMETER VALUE 1700 CONFIGURATION PHASE NUMBER 3 Note for iridium floats where configuration can be changed any time When not available in real time the configuration may latter be reconstructed from the floats data The create a co
32. to represents the time of the measurement REFERENCE DATE TIME Date and time are in universal time coordinates JULD units days since 1950 01 01 The julian day is relative to REFERENCE DATE TIME 00 00 00 UTC Example JULD conventions Relative julian days with 18833 8013889885 July 25 2001 19 14 00 decimal part as parts of the day JULD FillValue 999999 JULD QC char JULD QC N MEASUREMENT Quality flag on JULD date and time JULD QC long name Quality on date and The flag scale is described in the reference table 2 time Example JULD QC conventions Argo reference table 1 the date and time seems correct 25 ULD QC FillValue LATITUDE double LATITUDE N MEASUREMENT Latitude of the location or measurement LATITUDE long name Latitude of each Unit degree north location Example 44 4991 for 44 29 56 76 N LATITUDE units degree north LATITUDE FillValue 99999 LATITUDE valid min 90 LATITUDE valid max 90 LONGITUDE double LONGITUDE N MEASUREMENT Longitude of the location or measurement LONGITUDE long name Longitude of each Unit degree east location Example 16 7222 for 16 43 19 92 E LONGITUDE units degree east Argo data management User s manual POSITION_ACCURA POSITION QC 5 lt PARAM gt lt PARAM gt _QC lt PARAM gt _ADJ USTE D lt PARAM gt _ADJ USTE D QC PARAM ADJUSTE D ERROR LONGITUDE
33. value are recorded as strings of 128 characters All parameter names are standardized and available in reference table 14 TECHNICAL_PARAMETER_NAME TECHNICAL_PARAMETER_VALUE CYCLE_NUMBER Argo data management Definition char TECHNICAL_PARAMETER_NAME N_TECH_PARAM STRING128 TECHNICAL PARAMETER NAME I ong name Name of technical parameter TECHNICAL PARAMETER NAME FillValue char TECHNICAL PARAMETER VALUE N TECH PARAM STRING128 TECHNICAL PARAMETER VALUE long_name Value of technical parameter TECHNICAL PARAMETER VALUE _ FillValue 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 Comment Name of the technical parameter Example CLOCK_FloatTime_HHMMSS See reference table 14 for standard technical parameter names Value of the technical parameter Example 125049 Cycle number of the technical parameter Example 157 User s manual 53 2 8 GDAC directory file format 2 8 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 da
34. 0 f 42 9 3F 99999 f F9 3 0 001f n S situ measurement degree Celsius 2 f 404 9 3f 99999 f F9 3 0 001f S CNDC tu measurement mhos m ELECTRICAL In si CONDUCTIVITY In situ measurement sea decibar PRES SEA PRESSURE surface 0 PSAL PRACTICAL SALINITY TEMP SEA TEMPERATURE IN SITU ITS 90 SCALE F9 3 0 001f TEMP_DOXY 5 TEMPERATURE n situ measurement degree_Celsius 2 f 404 9 3f 99999 f FROM DOXY SENSOR F9 3 ITS 90 SCALE 0 001f Y sensors such as SBE43 F5 2 0 01f OXY sensors such as SBE43 F5 2 0 01f A sensors such as SBE43 F5 2 0 01f BPHASE_DOXY BPHASE_DOXY Uncalibrated phase shift degree 10 f 70 f 8 2f 99999 f reported by sensors such F8 2 las Aandera Optode 0 01f DPHASE DOXY DPHASE DOXY Calibrated phase shift degree 10 f 704 8 2 99999 f reported by sensors such F8 2 las Aandera Optode 0 01f DOX CONCENT DOXY echnical value reported micromole litre 0 f 650 f 969 3f 99999 f Y by sensors such as F9 3 Aandera Optode 0 001f by the oxygen sensor F7 1 0 1f 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 chairman jcommops org for approval and inclusion 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
35. 004 02 nc 81900045 004 03 nc R1900045 004 04 81900045 005 Trajectory Data e lt FloatID gt _traj nc Example 1900045 traj nc Argo data management User s manual 73 Metadata e lt FloatID gt _meta nc Example 1900045_meta nc Technical Data e lt FloatID gt _tech nc Example 1900045 tech nc 4 2 Other data sources All 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 http www wmo ch web www DPS NewCodesTables WMO306vol I 1PartA pdf Argo data management User s manual ce 5 Using 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 T
36. 1 2 GREYLIST FILES COLLECTION 80 6 2 GDAC FILES REMOVAL 81 Argo data management User s manual 1 History of the document Version Date Comment 0 9 29 122011 Thierry Carval creation of the document 0 9a 18 01 2002 Bob Keeley general comments and updates S O 0 9a 24 01 2002 Harscoat general comments and updates Cd 0 9a 25 01 2002 Claudia Schmid general comments and updates O Z o y y 0 9c 1 0 1 0a 1 08 Update of measurements of each profile to handle corrected values 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 01 10 2004 Meta data section WMO INST TYPE added to history section INSTRUMENT TYPE renamed INST REFERENCE 10 11 2004 Updates in reference table 3 parameter codes table DOXY TEMP DOXY TEMP use ITS 90 scale 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 12 06 2005 Change conventions attribute and description of PROFILE lt gt QC in section 2 2 3 12 06 2005 Add reference table 2a
37. ATE 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 char INST REFERENCE N PROF STRING64 INST REFERENCE long name Instrument type INST REFERENCE conventions Brand type serial number INST REFERENCE FillValue char FIRMWARE VERSION N PROF STRING10 FIRMWARE VERSION long name Instrument version FIRMWARE VERSI ON conventions FIRMWARE VERSION FillValue char INST TYPE N PROF STRING4 WMO INST TYPE long name Coded instrument type WMO INST TYPE conventions Argo reference table 8 WMO INST TYPE FillValue double JULD N PROF JULD long name Julian day The parameter names are listed in reference table 3 Examples TEMP PSAL CNDC TEMP temperature PSAL practical salinity CNDC conductvit Float cycle number A profiling float performs cycles In 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 1 is the number of the first complete cycle Example 10 cycle number 10 Type of profile on which measurement o
38. Argo data management ar um 02 01 USER S MANUAL Version 2 3 July 13 2010 ad c E Q o M of the integrated global observation strategy F ARGO part of the integrated global abservation strategy Argo data management User s manual Ref ar um 02 01 Ref ifremer cor do dti mut 02 084 Version 2 3 Date 13 07 2010 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 s Table of contents HISTORY OF THE DOCUMENT 6 1 INTRODUCTION 8 1 1 NOTICE ON FILE FORMAT CHANGE TRANSITION 8 1 2 USER OBLIGATIONS 8 1 3 DISCLAIMER 8 1 4 FURTHER INFORMATION SOURCES AND CONTACT INFORMATION 8 1 5 ARGO PROGRAM DATA MANAGEMENT CONTEXT 9 1 6 ARGOFLOAT CYCLES 9 1 1 7 REAL TIME AND DELAYED MODE DATA 1 2 FORMATS DESCRIPTION 12 2 1 OVERVIEW OF THE FORMATS 12 2 2 PROFILE FORMAT 13 2 2 1 DIMENSIONS AND DEFINITIONS 13 2 2 2 GENERAL INFORMATION ON THE PROFILE FILE 14 2 2 3 GENERAL INFORMATION FOR EACH PROFILE 14 2 2 4 MEASUREMENTS FOR EACH PROFILE 17 2 2 5 CALIBRATION INFORMATION FOR EACH PROFILE 19 2 2 6 HISTORY INFORMATION FOR EACH PROFILE 20 2 3 TRAJECTORY FORMAT 22 2 3 1 DIMENSIONS AND DEFINITIONS 22 2 3 2 GENERAL INFORMATION ON THE TRAJECTORY
39. Data Management Argo Documentation General documentation Data format Argo Oxygen data management Remark on unit conversion of oxygen The unit of DOXY is micromole kg in Argo data and the oxygen measurements are sent from Argo floats in another unit such as micromole L for Optode and ml L for SBE Thus the unit conversion is carried out by DACS as follows e O2 micromole kg O2 micromole L p e O2 micromole L 44 6596 x O2 ml L Here p is the potential density of water kg L at zero pressure and at the potential temperature e g 1 0269 kg L e g UNESCO 1983 The value of 44 6596 is derived from the molar volume of the oxygen gas 22 3916 L mole at standard temperature and pressure 0 C 1 atmosphere e g Garc a and Gordon 1992 Argo data management User s manual r Garc a H E and L I Gordon 1992 Oxygen solubility in sea water better fitting equations Limnol Oceanogr 37 6 1307 1312 UNESCO 1983 Algorithms for computation of fundamental properties of seawater Unesco technical papers in marine science 44 53pp 3 4 Reference table 4 data centres and institutions codes Data centres and institutions BO jBODC UnitdKinpom GT GTS used for data coming from WMO GTS network JNCOSInda JA 1 MAJapn MEDSCaada 2 JPMELUSA 2 Spin 0 Research Institute of Vladivostock Russia WH__ Woods Hole Oceanographic Institution USA 3 5
40. ER long name List of Example PSAL parameters with calibration information PARAMETER conventions Argo reference table 3 PARAMETER FillValue SCIENTIFIC CALIB EQUATION Char Calibration equation applied to the SCIENTIFIC CALIB EQUATION N PROF parameter N CALIB N PARAM STRING256 Example SCIENTIFIC CALIB EQUATION long name Tc al T a0 Calibration equation for this parameter SCIENTIFIC CALIB EQUATION FillValue SCIENTIFIC CALIB COEFFICIENT Char Calibration coefficients for this equation SCIENTIFIC CALIB COEFFICIENT N PROF Example N CALIB N PARAM STRING256 1 0 99997 0 0 0021 SCIENTIFIC_CALIB_COEFFICIENT long_na me Calibration coefficients for this equation SCIENTIFIC CALIB COEFFICIENT FillValue SCIENTIFIC CALIB COMMENT Char Comment about this calibration SCIENTIFIC CALIB COMMENT N PROF Example CALIB PARAM STRING256 The sensor is not stable SCIENTIFIC CALIB COMMENT long name Comment applying to this parameter calibration SCIENTIFIC CALIB COMMENT FillValue CALIBRATION DATE Char CALIBRATION DATE N PROF Date of the calibration CALIB PARAM DATE TIME Example 20011217161700 CALIBRATION DATE FillValue Argo data management User s manual l 2 2 6 History information for each profile 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 num
41. FERENCE TABLES 58 3 1 REFERENCE TABLE 1 DATA TYPE 58 3 2 REFERENCE TABLE 2 ARGO QUALITY CONTROL FLAG SCALE 59 3 2 1 REFERENCE TABLE 2 MEASUREMENT FLAG SCALE 59 3 2 2 REFERENCE TABLE 2A PROFILE QUALITY FLAG 60 3 3 REFERENCE TABLE 3 PARAMETER CODE TABLE 61 3 3 1 PARAMETERS FROM DUPLICATE SENSORS 61 3 3 2 OXYGEN RELATED PARAMETERS 62 3 4 REFERENCE TABLE 4 DATA CENTRES AND INSTITUTIONS CODES 63 3 5 REFERENCE TABLE 5 LOCATION CLASSES ARGOS 63 3 6 REFERENCE TABLE 6 DATA STATE INDICATORS 64 3 7 REFERENCE TABLE 7 HISTORY ACTION CODES 65 3 8 REFERENCE TABLE 8 INSTRUMENT TYPES 66 3 9 REFERENCE TABLE 9 POSITIONING SYSTEM 66 3 10 REFERENCE TABLE 10 TRANSMISSION SYSTEM 67 3 11 REFERENCE TABLE 11 QC TEST BINARY IDs 67 3 12 REFERENCE TABLE 12 HISTORY STEPS CODES 68 3 13 REFERENCE TABLE 13 OCEAN CODES 69 3 14 REFERENCE TABLE 14 TECHNICAL PARAMETER NAMES 70 3 15 REFERENCE TABLE 15 CONVENTION FOR DESCRIBING PROGRESS WITHIN A CYCLE71 4 DATA ACCESS 72 41 FILE NAMING CONVENTION ON GDACS 72 4 2 OTHER DATA SOURCES 73 5 USING THE HISTORY SECTION OF THE ARGO NETCDF STRUCTURE 74 5 1 RECORDING INFORMATION ABOUT THE DELAYED MODE QC PROCESS 74 5 2 RECORDING PROCESSING STAGES 75 5 3 RECORDING QC TESTS PERFORMED AND FAILED 76 5 4 RECORDING CHANGES IN VALUES 77 Argo data management User s manual TTT OO 6 DAC GDAC DATA MANAGEMENT 79 6 1 GREYLIST FILES OPERATIONS 79 6 1 1 GREYLIST DEFINITION AND MANAGEMENT 79 6
42. FILE 23 2 3 3 GENERAL INFORMATION ON THE FLOAT 23 2 3 4 LOCATIONS AND MEASUREMENTS FROM THE FLOAT 25 2 3 5 CYCLEINFORMATION FROM THE FLOAT 27 2 3 6 HISTORY INFORMATION 29 2 4 META DATA FORMAT VERSION 2 2 31 2 4 1 DIMENSIONS AND DEFINITIONS 3l 2 4 2 GENERAL INFORMATION ON THE META DATA FILE 32 2 4 3 FLOAT CHARACTERISTICS 33 2 4 4 FLOAT DEPLOYMENT AND MISSION INFORMATION 35 2 4 5 FLOAT SENSOR INFORMATION 36 2 4 6 FLOAT CALIBRATION INFORMATION 36 2 4 7 FLOAT CYCLE INFORMATION 38 2 4 8 HIGHLY DESIRABLE META DATA PARAMETERS 39 2 5 META DATA FORMAT VERSION 2 3 40 2 5 1 DIMENSIONS AND DEFINITIONS 40 2 5 2 GENERAL INFORMATION ON THE META DATA FILE 41 2 5 3 FLOAT CHARACTERISTICS 42 2 5 4 CONFIGURATION PARAMETERS 43 2 5 5 FLOAT SENSOR INFORMATION 45 2 5 6 FLOAT CALIBRATION INFORMATION 45 Argo data management User s manual 1 2 5 7 HIGHLY DESIRABLE META DATA PARAMETERS 46 2 6 TECHNICAL INFORMATION FORMAT VERSION 2 2 47 2 6 1 DIMENSIONS AND DEFINITIONS 47 2 6 2 GENERAL INFORMATION ON THE TECHNICAL DATA FILE 48 2 6 3 TECHNICAL DATA 49 2 7 TECHNICAL INFORMATION FORMAT VERSION 2 3 50 2 7 1 DIMENSIONS AND DEFINITIONS 50 2 7 2 GENERAL INFORMATION ON THE TECHNICAL DATA FILE 51 2 7 3 TECHNICAL DATA 52 2 8 GDAC FTP DIRECTORY FILE FORMAT 53 2 8 1 PROFILE DIRECTORY FILE FORMAT 53 2 8 2 PROFILE DIRECTORY FILE FORMAT VERSION 2 1 54 2 8 3 TRAJECTORY DIRECTORY FORMAT 55 2 8 4 META DATA DIRECTORY FORMAT 56 3 RE
43. HISTORY ACTION FillValue char HISTORY PARAMETER N HISTORY N PROF STRING16 HISTORY PARAMETER long name Station parameter action is performed on HISTORY PARAMETER conventions Argo reference table 3 HISTORY PARAMETER FillValue 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 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 float HISTORY PREVIOUS VALUE N HISTORY N PROF HISTORY PREVIOUS VALUE long na me Parameter Flag previous value before action HISTORY PREVIOUS VALUE FillVal ue 99999 f 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 ACTI ONZQCP tests failed when ACTION QCF HISTORY QCTEST FillValue Name of the action The action codes are described in reference table 7 Example QCF for QC failed Name of the parameter on which the action is performed Example PSAL Start pressure the action is applied to Example 1500 0 Stop pressure the action is applied to This should be greater than START_PRES Example 1757 0
44. HISTORY SOFTWARE RELEASE Fill Value char HISTORY REFERENCE N HISTORY N PROF STRING64 HISTORY REFERENCE long name Reference of database HISTORY REFERENCE conventions Institution dependent HISTORY REFERENCE FillValue char HISTORY DATE N HISTORY N PROF DATE TIME HISTORY DATE long name Date the history record was created HISTORY DATE conventions Comment Institution that performed the action Institution codes are described in reference table 4 Example ME for MEDS 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 Name of the software that performed the acti This code is institution dependent Example WJO Version of the software This name is institution dependent Example 1 0 Code of the reference database used for quality control in conjunction with the software This code is institution dependent Example WOD2001 Date of the action Example 20011217160057 User s manual HISTORY_ACTION HISTORY_PARAMETER HISTORY START PRES HISTORY STOP PRES HISTORY PREVIOUS VALUE HISTORY QCTEST YYYYMMDDHHMISS HISTORY DATE FillValue char HISTORY ACTION N HISTORY PROF STRINGA HISTORY ACTION long name Action performed on data HISTORY ACTION conventions Argo reference table 7
45. IENT long name 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 1 0 99997 0 0 0021 User s manual Calibration coefficients for this equation PREDEPLOYMENT CALIB COEFFICIENT FillValue PREDEPLOYMENT CALIB char Comments applying to this parameter COMMENT PREDEPLOYMENT CALIB COMMENT N PARAM STRING2 calibration 56 Example PREDEPLOYMENT CALIB COMMENT long name The sensor is not stable Comment applying to this parameter calibration PREDEPLOYMENT CALIB COMMENT FillValue 2 5 7 Highly desirable meta data parameters A highly desirable meta data parameter should be correctly filled according to the following table Highly desirable meta mandatory format example data DATA_TYPE Argo meta data DATA_TYPE Argo meta data not empty 90 lt real lt 90 LAUNCH_LATITUDE 7 91400003433228 not empty 180 lt real lt 180 LAUNCH_LONGITUDE 179 828338623047 Argo data management User s manual 14 2 6 Technical information format version 2 2 An Argo technical file contains technical information from an Argo float This information is registered for each cycle performed by the float The n
46. ION Argo data management Definition char HISTORY INSTITUTION HISTORY STRING4 HISTORY INSTITUTION long name Institution which performed action HISTORY INSTITUTION conventions Argo reference table 4 HISTORY INSTITUTION FillValue char HISTORY STEP N HISTORY STRINGA HISTORY STEP long name Step in data processing HISTORY STEP conventions Argo reference table 12 HISTORY STEP FillValue Char HISTORY SOFTWARE N HISTORY STRING4 HISTORY SOFTWARE long name Name of software which performed action HISTORY SOFTWARE conventions Institution dependent HISTORY SOFTWARE FillValue Char HISTORY SOFTWARE RELEASE N HISTORY STRING4 HISTORY SOFTWARE RELEASE long name Version release of software which performed action HISTORY SOFTWARE RELEASE conv entions Institution dependent HISTORY SOFTWARE RELEASE Fill Value char HISTORY REFERENCE N HISTORY STRING64 HISTORY REFERENCE long name Reference of database HISTORY REFERENCE conventions Institution dependent HISTORY REFERENCE FillValue char HISTORY_DATE N_HISTORY DATE_TIME HISTORY_DATE long_name Date the history record was created HISTORY_DATE conventions YYYYMMDDHHMISS HISTORY DATE FillValue char HISTORY ACTION N HISTORY STRING64 HISTORY ACTION long name Action performed on data HISTORY ACTION conventions Argo reference table 7 HISTO
47. Parameter or flag of the previous value before action Example 2 probably good for a flag that was changed to 1 good 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 mnl 2 3 Trajectory format An Argo trajectory file contains all received locations of an Argo float There is one trajectory file per float In addition to locations a trajectory file may contain measurements such as temperature salinity or conductivity performed at some or all locations For file naming conventions see 4 1 2 3 1 Dimensions and definitions Name Definition 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 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 ST
48. QC conventions Argo reference table 2 JULD_QC _FillValue double J ULD_LOCATION N_PROF JULD long_name Julian day UTC of the location relative to REFERENCE_DATE_TIME JULD units days since 1950 01 01 00 00 00 UTC JULD conventions Relative julian days with decimal part as parts of day JULD FillValue 999999 double LATITUDE N PROF LATITUDE long name Latitude of the station best estimate LATITUDE units degree north LATITUDE FillValue 99999 LATITUDE valid min 90 LATITUDE valid max 90 double LONGITUDE N PROF LONGITUDE long name Longitude of the station best estimate LONGITUDE units degree east LONGITUDE FillValue 99999 LONGI TUDE valid min 180 LONGITUDE valid max 180 char POSITION QC N PROF POSITION QC long name Quality on position latitude and longitude POSITION QC conventions Argo reference table 2 POSITION QC FillValue char POSITIONING SYSTEM N PROF STRING8 POSITIONING SYSTEM long name Positioning system POSITIONING SYSTEM FillValue char PROFILE PARAM QC N PROF PROFILE PARAM QC long name Global quality flag of lt PARAM gt profile PROFILE PARAM QC conventions Argo reference table 2a PROFILE PARAM QC FillValue part represents the time of the profile Date and time are in universal time coordinates The julian day is relative to REFERENCE DATE
49. RING2 2 N_PARAM N_PARAM lt int Maximum number of parameters measured or calculated for a pressure value gt sample Examples pressure temperature N PARAM 2 pressure temperature salinity N PARAM 3 pressure temperature conductivity salinity PARAM 4 N MEASUREMENT MEASUREMENT This dimension is the number of recorded locations and measurements of the unlimited file N CYCLE N CYCLE int Number of cycles performed by the float value Example N CYCLE 100 N HISTORY N HISTORY int Maximum number of history records for a location This dimension depends value on the data set Exemple N HISTORY 10 Argo data management User s manual 2 3 2 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 char DATA TYPE STRING16 DATA TYPE comment Data type DATA TYPE FillValue char FORMAT VERSION STRI NG4 FORMAT VERSI ON comment File format version FORMAT VERSION FillValue char HANDBOOK VERSION STRI NG4 HANDBOOK VERSION comment Data handbook version HANDBOOK VERSION FillValue char REFERENCE DATE TIME DATE TIME REFERENCE DATE TIME comment Date of reference for Julian days REFERENCE DATE TIME conventions YYYYMMDDHHMISS REFERENCE DATE TIME FillValue
50. RY ACTION FillValue Comment Institution that performed the action Institution codes are described in reference table 4 Example ME for MEDS 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 Name of the software that performed the acti This code is institution dependent Example WJO Version of the software This name is institution dependent Example 1 0 Code of the reference database used for quality control in conjunction with the software This code is institution dependent Example WOD2001 Date of the action Example 20011217160057 Name of the action The action codes are described in reference table 7 Example QCF for QC failed User s manual 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 PREVIOUS VALUE long na me Parameter Flag previous value before action HISTORY PREVIOUS VALUE FillVal u
51. Repetition rate of the transmission system Unit second Example 40 for a repetition of messages every 40 seconds Position system from reference table 9 ARGOS or GPS are 2 positioning systems Example ARGOS Rate of drift of the float internal clock Unit decisecond day Example 1 57 Model of the float Example APEX SBE Name of the manufacturer Example Webb research References of the instrument brand type serial number Example APEX SBE 259 Instrument type from WMO code table 1770 A subset of WMO table 1770 is User s manual DIRECTION PROJECT NAME DATA CENTRE ANOMALY Argo data management WMO_INST_TYPE conventions Argo reference table 8 WMO INST TYPE FillValue char DIRECTION DIRECTION long name Direction of the profiles DI RECTI ON conventions A ascending profiles B descending and ascending profiles DIRECTION FillValue char PROJECT NAME STRING64 PROJECT NAME long name The program under which the float was deployed PROJECT NAME FillValue char DATA CENTRE STRI NG2 DATA CENTRE long name Data centre in charge of float real time processing DATA CENTRE conventions Argo reference table 4 DATA CENTRE FillValue char NAME STRING64 NAME comment Name of the principal investigator NAME FillValue char ANOMALY STRING256 ANOMALY long name Describe any anomalies o
52. SCII 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 e 55 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 PARAM 4 N_LEVELS N_LEVELS lt int Maximum number of pressure levels contained in a profile value This dimension depends on the data set Example N_LEVELS 100 N_CALIB lt int Maximum number of calibrations performed on a profile value This dimension depends on the data set Example N_CALIB 10 UNLIMITED Argo data management User
53. SION 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 R Retrieved END MISSION STATUS FillValue Date and time UTC of launch of the float Format YYYYMMDDHHMISS Example 20011230090500 December 307 2001 03 05 00 Latitude of the launch Unit degree north Example 44 4991 44 29 56 76 N 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 Date and time UTC of the first descent of the float Format YYYYMMDDHHMISS Example 20011230090500 December 30 2001 06 05 00 Quality flag on start date The flag scale is described in the reference table 2 Example 1 start date seems correct Identifier of the deployment platform Example L ATALANTE Identifier of the mission used to deploy the platform Example POMME2 Identifier of CTD or XBT stations used to verify the first profile Example 58776 58777 Date UTC of the end of mission of the float Format YYYYMMDDHHMISS Example 20011230090500 December 307 2001 03 05 00 Status of the end of mission of the float User s manual 2 4 5 Float sensor information This section contai
54. TA_CENTRE DATE_CREATION DATE_UPDATE Argo data management Definition char PLATFORM_NUMBER STRING8 PLATFORM NUMBER long name Float unique identifier PLATFORM NUMBER convention s WMO float identifier AQI PLATFORM NUMBER FillValue char DATA TYPE STRING32 DATA TYPE comment Data type DATA TYPE FillValue char FORMAT VERSI ON STRINGA FORMAT VERSION comment File format version FORMAT VERSION FillValue char HANDBOOK VERSI ON STRING4 HANDBOOK VERSION comment Data handbook version HANDBOOK VERSION 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 DATE CREATION DATE TIME DATE CREATION comment Date of file creation DATE CREATION 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 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 File format version Example 2 2 Version number of the data handbook Thi
55. TECHNICAL PARAMETER VALUE char Value of the technical parameter TECHNICAL PARAMETER VALUE Example N CYCLE N TECH PARAM 115 STRING32 TECHNICAL PARAMETER VALUE long_name Value of technical parameters for this cycle TECHNICAL PARAMETER VALUE FillValue All parameter names are standardized and available from reference table 14 Argo data management User s manual se 2 7 Technical information format version 2 3 The format version 2 3 of Argo technical data will replace version 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 2 3 format all its technical files must be provided in version 2 3 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 7 1 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
56. TRAN for mat X lt gt ADJUSTED ERROR resolution X 2 3 5 Cycle information from the float This section contains information on the cycles performed by the float Each field in this section has a N CYCLE dimension N CYCLE is the number of cycles performed by the float When a cycle is missing e g no data received all cycle informations are reported as fill values JULD ASCENT START JULD ASCENT START STATUS JULD ASCENT END JULD ASCENT END STATUS JULD DESCENT START JULD DESCENT START STATUS Argo data management Definition double JULD ASCENT START N CYCLE JULD ASCENT START long name Start date of the ascending profile 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 ASCENT START FillValue 999999 CharJULD ASCENT START STATUS N CYCLE JULD ASCENT START STATUS conventions 0 Nominal 1 Estimated 2 Transmitted JULD ASCENT START STATUS FillValue double JULD 5 END N CYCLE JULD ASCENT END long name End date of the ascending profile 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 day JULD ASCENT END FillValue 999999 CharJULD ASCENT END STATUS N CYCLE JULD ASCENT END STATUS conventions 0 Nominal 1 Estimate
57. YMMDDHHMISS Fill value blank latitude longitude location of the profile Argo data management User s manual ss Fill value 99999 e ocean code of the ocean of the profile as described in reference table 13 Fill value blank e profiler type type of profiling float as described in reference table 8 Fill value blank e institution institution of the profiling float described in reference table 4 Fill value blank e date update date of last update of the file YYYYMMDDHHMISS Fill value blank e profile temp qc profile psal qc profile qc global quality flag on temperature salinity and oxygene profile Fill value blank e 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 e gdac date creation cr ation date of the file on GDAC YYYYMMDDHHMISS e gdac date update update date of the on GDAC YYYYMMDDHHMISS n 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 Ar
58. ae 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 institution institution of the profiling float described in reference table 4 ill value blank te update date of last update of the file YYYYMMDDHHMISS ill value blank 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 3t Project ARGO Format version 2 0 3t 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 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 58 3 Reference tables 3 1 Reference table 1 data type This table contains the list of acceptable values for DATA_TYPE field Name Argo meta data Argo technical data Argo data management Us
59. are considered to be part of the geospatial and temporal referencing process 3 7 Reference table 7 history action codes Code Meaning IP This history group operates on the complete input record 0 Argo data management User s manual Time error Profile date time has been erroneously encoded Corrected if possible 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 Figure Instrument 831 840 841 842 843 845 846 847 850 851 852 855 856 857 858 859 860 Profiling Float NEMO SBE conductivity Sensor 3 9 Reference table 9 positioning system Code Description ARGOS ARGOS positioning system GPS positioning system RAFOS RAFOS positioning system Argo data management User s manual 3 10 Reference table 10 transmission system Code Description ARGOS 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
60. ata parameters A highly desirable meta data parameter should be correctly filled according to the following table Highly desirable meta mandatory format example data DATA_TYPE DATA Argo meta data FORMAT_VERSION FORMAT VERSION 22 HANDBOOK VERSION HANDBOOK VERSION 1 2 PTT 722978 DIRECTION A DATA CENTRE AO not empty 180 lt real lt LAUNCH LONGITUDE 180 179 828338623047 LAUNCH QC 1 see reference table 3 PARAMETER PRES TEMP PSAL Argo data management User s manual 1 2 5 Meta data format version 2 3 The format version 2 3 of Argo metadata will replace version 2 2 gradually During the transition period both formats will be valid However when a Data Assembly Center DAC produces metadata files with the new 2 3 format all its metadata files must be provided in version 2 3 An Argo meta data file contains information about an Argo float For file naming conventions see 4 1 2 5 1 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 2001 17 28 34 19971217000000 December 17 1997 00 00 00 STRING256 STRING256 256 String dimensions
61. aviour is recorded in the ANOMALY field of the meta data file Argo data management User s manual 80 6 1 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 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 greylist csv The whole file is rejected is the format check fails Floatid valid Argo float id the corresponding meta data file must exist Parameter PSAL TEMP PRES or DOXY Start date YYYYMMDD valid mandatory Enddate YYYYMMDD valid fill value Flag valid argo flag Comment free DAC valid DAC mandatory 3 Remove all the floats of the DAC from the GDAC grey list and add the content of the submitted greylist csv file Note after each submission a copy of the Argo greylist is stored in etc greylist ar greylist txt Y Y YYMMDD The global Argo greylist is sorted by DAC PLATFORM CODE and START DATE in alphabetical order Argo data management User s manual 6 2 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 fi
62. ber 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 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 HISTORY_INSTITUTION HISTORY_STEP HISTORY_SOFTWARE HISTORY_SOFTWARE_RELEASE HISTORY_REFERENCE HISTORY_DATE Argo data management Definition char HISTORY_INSTITUTION N_HISTORY N_PROF STRING4 HISTORY_INSTITUTION long_name Institution which performed action HISTORY_INSTITUTION conventions Argo reference table 4 HISTORY_INSTITUTION _ FillValue char HISTORY_STEP N_HISTORY N PROF STRINGA HISTORY STEP long name Step in data processing HISTORY STEP conventions Argo reference table 12 HISTORY STEP FillValue Char HISTORY SOFTWARE N HISTORY N PROF STRING4 HISTORY SOFTWARE long name Name of software which performed action HISTORY SOFTWARE conventions Institution dependent HISTORY SOFTWARE FillValue Char HISTORY SOFTWARE RELEASE HISTORY PROF STRING4 HISTORY SOFTWARE RELEASE long name Version release of software which performed action HISTORY SOFTWARE RELEASE conv entions Institution dependent
63. bration information Model of sensor Example SBE41 Serial number of the sensor Example 2646 036 073 Units of accuracy of the sensor Example psu Accuracy of the sensor Example 0 005 Resolution of the sensor Example 0 001 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 Argo data management 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 PARAM STRING2 56 PREDEPLOYMENT CALIB EQUATION long name Calibration equation for this parameter PREDEPLOYMENT CALIB EQUATION FillValue char PREDEPLOYMENT CALIB COEFFICIENT N PARAM STRIN G256 PREDEPLOYMENT CALIB COEFFICIENT long name 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 1 0 99997 0 0 0021
64. ccurs A ascending profile D descending profile 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 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 through 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 References of the instrument brand type serial number Example APEX SBE 259 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 846 Webb Research float Seabird sensor Julian day of the profile UTC of the The integer part represents the day the decimal User s manual JULD LOCATION LATITUDE POSITION QC POSITIONING SYSTEM PROFILE PARAM QC Argo data management station relative to REFERENCE DATE TIME JULD units days since 1950 01 01 00 00 00 UTC JULD conventions Relative julian days with decimal part as parts of day JULD FillValue 999999 charJULD QC N PROF JULD QC long name Quality on Date and Time JULD
65. cean code is not used in Argo NetCDF files Code Meaning __ Indian ocean area Pacific ocean area e The Pacific Atlantic boundary is 70 W e The Pacific Indian boundary is 145 E e The Atlantic Indian boundary is 20 E Argo data management User s manual m 3 14 Reference table 14 technical parameter names All technical parameter names are standardized The list of technical parameter names is available at 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 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 71 3 15 Reference table 15 convention for describing progress within cycle The lookup table allows matching the part of the cycle when a located event is performed It is used in the trajectory file as CYCLE STAGE variable Surface
66. cted from the list in reference table 7 HISTORY QCTEST FillValue This field does not apply database used for the delayed mode QC process PARAMETER Eran This field does not apply 1 HISTORY_START_PRES 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 Argo data management User s manual 75 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 one 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 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
67. d 2 Transmitted JULD ASCENT END STATUS FillValue double JULD DESCENT START N CYCLE JULD DESCENT START long name Descent start date of the cycle 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 day DESCENT START FillValue 999999 CharJULD DESCENT START STATUS N CYCLE JULD DESCENT START STATUS conventions 0 Nominal 1 Estimated 2 Transmitted JULD DESCENT START STATUS FillValue Comment Julian day UTC of the beginning of the ascending profile Example 18833 8013889885 July 25 2001 19 14 00 0 date comes from the float meta data 1 date is estimated 2 date is transmitted by the float 9 date is unknown Julian day UTC of the end of the ascending profile Example 18833 8013889885 July 25 2001 19 14 00 0 date comes from the float meta data 1 date is estimated 2 date is transmitted by the float 9 date is unknown Julian day UTC of the beginning of the descending profile Example 18833 8013889885 July 25 2001 19 14 00 0 date comes from the float meta data 1 date is estimated 2 date is transmitted by the float User s manual Pf 9 date is unknown JULD DESCENT END JULD DESCENT END STATUS JULD START TRANSMISSION JULD START TRANSMISSION STAT US GROUNDED CONFIGURATION PHASE NUMBER DATA MODE Argo data
68. d mode or real time data DATA MODE conventions R real time D delayed mode A real time with adjustment DATA MODE FillValue Julian day UTC of the end of the descending profile Example 18833 8013889885 July 25 2001 19 14 00 0 date comes from the float meta data 1 date is estimated 2 date is transmitted by the float 9 date is unknown Julian day UTC of the beginning of data transmission Example 18833 8013889885 July 25 2001 19 14 00 0 date comes from the float meta data 1 date is estimated 2 date is transmitted by the float 9 date is unknown GROUNDED indicates if the float touched the ground for that cycle Format Y N U Examples Y yes the float touched the ground N no U unknown Phase number of the configuration parameter Example 1 See 82 5 4 Configuration parameters the fleat Indicates if the profile contains real time or delayed mode data R real time data D delayed mode data A real time data with adjusted values User s manual 29 2 3 6 History information This section contains history information for each action performed on each measurement Each item of this section has a N MEASUREMENT number of locations or measurements N HISTORY number of history records dimension HISTORY INSTITUTION HISTORY STEP HISTORY SOFTWARE HISTORY SOFTWARE RELEASE HISTORY REFERENCE HISTORY DATE HISTORY ACT
69. e The units of accuracy and resolution of the sensor SENSOR UNITS FillValue float SENSOR ACCURACY N PARAM SENSOR ACCURACY long name The accuracy of the sensor SENSOR ACCURACY FillValue 99999 f float SENSOR RESOLUTION N PARAM SENSOR RESOLUTION long name The resolution of the sensor SENSOR RESOLUTION FillValue 99999 f 2 5 6 Float calibration information Model of sensor Example SBE41 Serial number of the sensor Example 2646 036 073 Units of accuracy of the sensor Example psu Accuracy of the sensor Example 0 005 Resolution of the sensor Example 0 001 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 Argo data management 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 PARAM STRING2 56 PREDEPLOYMENT CALIB EQUATION long name Calibration equation for this parameter PREDEPLOYMENT CALIB EQUATION FillValue char PREDEPLOYMENT CALIB COEFFICIENT N PARAM STRIN G256 PREDEPLOYMENT CALIB COEFFIC
70. e 99999 f HISTORY INDEX DIMENSION char Name of dimension to which HISTORY START INDEX HISTORY INDEX DIMENSION N HIS and HISORY STOP INDEX TORY Correspond C N CYCLE M N MEASUREMENT HISTORY START INDEX int HISTORY START INDEX Start index the action is applied to This index N HISTORY corresponds to N MEASUREMENT or N CYCLE HISTORY START INDEX long name depending on the corrected parameter Start index action applied on Example 100 HISTORY START INDEX FillValue 99999 HISTORY STOP INDEX int HISTORY STOP INDEX Stopt index the action is applied to This index N HISTORY corresponds to N MEASUREMENT or N CYCLE HISTORY STOP INDEX long name depending on the corrected parameter Stop index action applied on Example 150 HISTORY STOP INDEX FillValue 99999 HISTORY QCTEST char HISTORY QCTEST N HISTORY This field records the tests performed when ACTION STRING16 is set to QCP qc performed the test failed when HISTORY QCTEST long name ACTION is set to QCF qc failed Documentation of tests performed The QCTEST codes are describe in reference table 11 tests failed in hex form HISTORY QCTEST conventions Example 0A in hexadecimal form Write tests performed when ACTION QCP3 tests failed when ACTION QCF HISTORY QCTEST FillValue The usage of history section is described in 5 Using the History section of the Argo netCDF Structure Argo data management User s manual Ml
71. e This field does not apply E HISTORY REFERENCE FillValue This field does not apply HISTORY DATE 2003080500 The year month day hour minute second that 0000 the process ran HISTORY ACTION QCF Selected from the list in reference table 7 HISTORY PARAMETER FillValue This field does not apply Argo data management User s manual 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 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 positio
72. e at ftp usgodae org pub outgoing argo ar_greylist txt e 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 For each affected parameter the start end date of malfunction is recorded 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 beh
73. er s manual 1 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 http www argodatamgt org Media Argo Data Management Argo Documentation General documentation Argo Quality Control manual n Meaning Real time comment Delayed mode comment 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 Fe ree ul used in real time Probably good data data 3 Bad data that Test 15 or Test 16 or Test 17 failed and all adjustment has been applied but are potentially jother real time QC tests passed These data the value may still be bad correctable are not to be used without scientific correction A flag 3 may be assigned by an operator during additional visual QC for bad data that be corrected in delayed mode 4 data Data have failed one or more of the real time Bad data Not adjustable QC 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
74. ere considered Argo data management User s manual 78 correct after the analysis they are considered wrong The history entry to record this would look as follows Example Changed flags Field Sample Explanation Selected from the list in reference table 4 Selected from the list in reference table 12 This field does not apply HISTORY SOFTWARE_RELEAS FillValue This field does not apply HISTORY REFERENCE REFERENCE FillValue This field does not apply Ee 2003080500 The year month day hour minute second that 0000 the process ran Selected from the list in reference table 7 Selected from the list in reference table 3 Shallowest pressure of action 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 lt param gt field Argo data management User s manual 6 DAC GDAC data management This chapter describes the data management organization between Argo DACs and GDACS 6 1 Greylist files operations 6 1 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 sit
75. g 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 Ucar web site address http www ucar edu ucar e NetCDF documentation http www unidata ucar edu packages netcdf index html Argo formats are divided in 4 sections e Dimensions and definitions e General information e Data section e 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 UTC time universal time coordinates Argo data management User s manual qm 2 2 Profile format An Argo profile file contains a set of profiles The minimum number is one profile There is no defined maximum number of profiles A profile contains measurements performed at different pressures by an Argo float A profile contains typically 100 pressures from 0 decibar surface to 2000 decibars approximately 2000 meters depth For each pressure sample there are a fixed number of parameters measured or calculated such as temperature salinity or conductivity For file naming conventions see 4 1 2 2 1 Dimensions and definitions Name Definition DATE TIME DATE TIME 14 This dimension is the length of an A
76. go 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 20081025220004 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 psal 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 200508301 30800 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 8 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 e A header with a list of general informations title description project name format version date of update ftp root addresses GDAC node e A table with a description of each file of the GDAC ftp si
77. he GDAC ftp site This table is a comma separated list 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 MDS signature For each update of the directory file an MD5 signature is produced The MDS signature file allows user to check that the file he collected through FTP is identical to the original file Naming convention e etc argo profile detailled index txt gz e etc argo profile detailled index txt gz md5 Detailed profile directory format definition Title FTP FTP 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 GDAC node CORIOLIS file date latitude longitude ocean profiler_type institution date_update profile_temp_qc profile_psal_qc profile__doxy_qc ad_psal _adjustment_mean ad_psal_adjustment_deviation gdac_date_creation gdac_date_update n_levels Profile directory file of the Argo Global Data Assembly Center root number 1 ftp ftp ifremer fr ifremer argo dac root number 2 ftp usgodae usgodae org pub outgoing argo dac file 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 YYY
78. he 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 Selected from the list in reference table 4 HISTORY STEP ARSQ Selected from the list in reference table 12 HISTORY SOFTWARE This is a locally defined name for the delayed mode QC process employed SOFTWARE_RELEAS EE ee is a locally defined indicator that identifies 512 version of the QC software is being used roe d REFERENCE WOD2001 HISTORY DATE 2003080500 The year month day hour minute second that 0000 the process ran HISTORY STOP PRES FillValue This field does not apply HISTORY PREVIOUS VALUE FillValue This field does not apply This is a locally defined name for the reference HISTORY ACTION I P Sele
79. hexidecimal number An example is given on 5 3 The test number and the test name are listed in the Argo quality control manual 82 1 2 Real time quality control tests e http www argodatamgt org Media Argo Data Management Argo Documentation General documentation Argo Quality Control manual Test ele Test name number test Platform Identification test Impossible Date test Impossible Location test Position on Land test Impossible Speed test Global Range test Regional Global Parameter test Pressure Increasing test Spike test 10 Top and Bottom Spike test obsolete 11 Gradient test 12 Digit Rollover test 13 Stuck Value test 14 Density Inversion test 15 Grey List test 16 Gross Salinity or Temperature Sensor Drift test 17 Visual QC test 18 Frozen profile test 524288 Deepest pressure test Argo data management User s manual 3 12 Reference table 12 history steps codes Code Meaning 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 If individual centres wish to record other codes they may add to this list as they feel is appropriate Argo data management User s manual 3 13 Reference table 13 ocean codes The ocean codes are used in the GDAC ftp directory files The o
80. id 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 name Quality on launch date time and location LAUNCH QC conventions Argo reference table 2 LAUNCH QC FillValue char START DATE DATE TIME START DATE long name Date UTC of the 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 QC conventions Argo reference table 25 START DATE QC FillValue char DEPLOY PLATFORM STRING32 DEPLOY PLATFORM long name Identifier of the deployment platform DEPLOY PLATFORM FillValue char DEPLOY MISSION STRING32 DEPLOY MISSION long name Identifier of the mission used to deploy the float DEPLOY MISSION FillValue char DEPLOY AVAILABLE PROFILE ID STRING256 DEPLOY AVALAIBLE PROFILE ID long name Identifier of stations used to verify the first profile DEPLOY AVAILABLE PROFILE 10 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 MIS
81. ime More on GDACs organization 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 R 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 nce where the initial R 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 YY counts multiple ascending descending profiles separately Since floats can alternate between the two modes they may have file names following both conventions Examples 1900045 003 R1900045 003D nc 5 1900046 007 01 1900067 007 02 1900067 007 03 1900046 0070 01 R1900067 007 02 R1900067 007D 03 d R1900045 003 R1900045 004 Ol nc 1900045
82. 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 Selected from the list in reference table 4 Selected from the list in reference table 12 This field does not apply HISTORY_SOFTWARE_RELEAS FillValue This field does not apply E HISTORY_REFERENCE FillValue This field does not apply The year month day hour minute second that 0000 the process ran Selected from the list in reference table 7 This field does not apply This field does not apply This field does not apply This field does not apply This is the result of all tests with IDs from 2 to HISTORY_QCTEST 1BE 256 having been applied see reference table 11 Record 2 Documenting the tests that were failed Field Sample Explanation Selected from the list in reference table 4 Selected from the list in reference table 12 This field does not apply HISTORY SOFTWARE RELEAS FillValu
83. ized and evaluated against a defined and documented set of measures The process is often automated i e has no human intervention and the measures are published and widely available Data have been scrutinized fully including intra record and intra dataset comparison and consistency checks Scientists have been involved in the evaluation and brought latest knowledge to bear The procedures are published widely available and widely accepted Data state indicator recommended use Subclass Some reductions or subsampling has been performed but the original record is available Geospatial and temporal properties are checked Geophysical values are validated f not validated this is clearly indicated Measures are completely automated or documentation is not widely available The measures have been tested on independent data sets for completeness and robustness and are widely accepted Procedures are not published or widely available Procedures have not undergone full scrutiny and testing Data are fully quality controlled peer reviewed and are widely accepted as valid Documentation is complete and widely available 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 1 Data pass through a communications system and arrive at a processing centre
84. le 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 User s manual 2 4 3 Float characteristics This section contains the main characteristics of the float Definition PLATFORM_NUMBER char PLATFORM_NUMBER STRING8 PLATFORM NUMBER long name Float unique identifier PLATFORM NUMBER conventions WMO float identifier AOI PLATFORM NUMBER FillValue char PTT STRING256 PTT long name Transmission identifier ARGOS ORBCOMM etc PTT FillValue TRANS SYSTEM char TRANS SYSTEM STRING16 TRANS SYSTEM long name The telecommunications system used TRANS SYSTEM FillValue TRANS SYSTEM ID char TRANS SYSTEM ID STRING32 TRANS SYSTEM ID long name The program identifier used by the transmission system TRANS SYSTEM ID FillValue TRANS FREQUENCY char TRANS FREQUENCY STRING16 TRANS FREQUENCY long name The frequency of transmission from the float TRANS FREQUENCY units hertz TRANS FREQUENCY FillValue TRANS REPETITION float TRANS REPETITION TRANS REPETITION long name The repetition rate of transmission from the float TRANS REPETITION units second TRANS REPETITION FillValue 99999 f POSITIONING SYSTEM char POSITIONING_SYSTEM STRING8 POSITIONING SYSTEM long name Positioning system POSITIONING SYSTEM FillValue
85. le 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 o Check the format of xxx_removal txt The whole file is rejected is the format check fails File name valid Argo file name the corresponding meta data file must exist for this DAC Move all the named files from GDAC into a etc removed directory o The removed files are kept for 3 months in the etc removed directory and erased after that delay Argo data management User s manual
86. le in reference table 14b The phase is used to record information that changes from cycle to cycle The phase 0 contains the usefull meta data that should not change during the float lifetime CONFIGURATION_PARAMETER_N AME CONFIGURATION_PARAMETER_VA LUE CONFIGURATION_PHASE_NUMBE R CONFIGURATION_PHASE_COMME NT Argo data management Definition char CONFIGURATON_PARAMETER_N AME N_CONF_PARAM STRING128 CONFIGURATON_PARAMETER_N AME long_name Name of configuration parameter CONFIGURATON_PARAMETER_N AME FillValue char CONFIGURATON PARAMETER V ALUE N CONF PARAM STRING128 CONFIGURATON_PARAMETER_V ALUE long_name Value of configuraton parameter CONFIGURATON_PARAMETER_V ALUE _ FillValue int CONFIGURATION_PHASE_NUMBE R N_CONF_PARAM CONFIGURATION PHASE NUMBE R long name Phase number of unique cycles performed by the float CONFIGURATION PHASE NUMBE R conventions 0 N 0 launch phase if exists 1 first complete phase CONFIGURATION PHASE NUMBE R FillValue 99999 char CONFIGURATION PHASE COMM ENT CONF PARAM STRING128 CONFIGURATION_PHASE_COMM ENT long name Comment on configuration CONFIGURATION PHASE COMM ENT FillValue Comment Name of the configuration parameter Example CONFIG ParkPressure dBAR See reference table 14 for standard configuraton parameter names Value of the configuration parameter Example 1500 Phase number of
87. n The two history entries would look as follows Example Changed latitude Field Sample Explanation Selected from the list in reference table 4 Selected from the list in reference table 12 HISTORY_SOFTWARE FillValue This field does not apply HISTORY_SOFTWARE_RELEAS FillValue This field does not apply E HISTORY_REFERENCE FillValue This field does not apply HISTORY_DATE 2003080500 The year month day hour minute second that 0000 the process ran HISTORY_ACTION Selected from the list in reference table 7 HISTORY_PARAMETER new entry for reference table 3 created by institution Cl to indicate changes have been made in the latitude This field does not apply This field does not apply HISTORY PREVIOUS VALUE This is the value of the latitude before the Nd 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 Be sure 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 Be sure to record the previous value in history entries 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 w
88. nary ID and test number 83 14 table 14 technical parameter names revision links to naming convention and list of technical parameters added 6 1 1 Greylist definition chapter added 6 1 1 Who when how to add a float in the greylist 6 1 1 Who when how to remove floats from the greylist 6 1 1 How users should use the greylist 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 82 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 3 14 Reference table 14 technical parameter names How to require new technical parameters 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 Argo data management User s manual ees 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 gr
89. nfiguration phase where CONFIG PHASE COMMENT The configuration is not available in real time When the configuration is transmitted in real time by the float create a configuration phase where CONFIG PHASE COMMENT The changing configuration is available in technical file Argo data management User s manual 2 5 5 Float sensor information 45 This section contains information about the sensors of the profiler Name SENSOR SENSOR_MAKER Definition char SENSOR N PARAM STRINGI16 SENSOR long name List of sensors on the float SENSOR conventions Argo reference table 3 SENSOR FillValue char SENSOR MAKER N PARAM STRING256 SENSOR MAKER long name The name of the manufacturer SENSOR MAKER FillValue Parameters measured by sensors of the float The parameter names are listed in reference table 3 Examples TEMP PSAL CNDC TEMP temperature in celsius PSAL practical salinity in psu CNDC conductvity in mhos m Name of the manufacturer of the sensor Example SEABIRD SENSOR MODEL SENSOR SERIAL NO SENSOR UNITS SENSOR ACCURACY SENSOR RESOLUTION char SENSOR MODEL N PARAM STRING256 SENSOR MODEL long name Type of sensor SENSOR MODEL FillValue char SENSOR SERIAL NO N PARAM STRING16 SENSOR SERIAL NO long name The serial number of the sensor SENSOR SERIAL NO FillValue char SENSOR UNITS N PARAM STRING16 SENSOR UNITS long nam
90. ns information about the sensors of the profiler Name SENSOR SENSOR_MAKER Definition char SENSOR N PARAM STRINGI16 SENSOR long name List of sensors on the float SENSOR conventions Argo reference table 3 SENSOR FillValue char SENSOR MAKER N PARAM STRING256 SENSOR MAKER long name The name of the manufacturer SENSOR MAKER FillValue Parameters measured by sensors of the float The parameter names are listed in reference table 3 Examples TEMP PSAL CNDC TEMP temperature in celsius PSAL practical salinity in psu CNDC conductvity in mhos m Name of the manufacturer of the sensor Example SEABIRD SENSOR MODEL SENSOR SERIAL NO SENSOR UNITS SENSOR ACCURACY SENSOR RESOLUTION char SENSOR MODEL N PARAM STRING256 SENSOR MODEL long name Type of sensor SENSOR MODEL FillValue char SENSOR SERIAL NO N PARAM STRING16 SENSOR SERIAL NO long name The serial number of the sensor SENSOR SERIAL NO FillValue char SENSOR UNITS N PARAM STRING16 SENSOR UNITS long name The units of accuracy and resolution of the sensor SENSOR UNITS FillValue float SENSOR ACCURACY N PARAM SENSOR ACCURACY long name The accuracy of the sensor SENSOR ACCURACY FillValue 99999 f float SENSOR RESOLUTION N PARAM SENSOR RESOLUTION long name The resolution of the sensor SENSOR RESOLUTION FillValue 99999 f 2 4 6 Float cali
91. of good data in the profile as described in reference table 2a Example PROFILE TEMP QC A the temperature profile contains only good values PROFILE PSAL QC C the salinity profile contains 5096 to 7596 good values User s manual TT 2 2 4 Measurements for each profile This section contains information on each level of each profile Each variable in this section has a PROF number of profiles N LEVELS number of pressure levels dimension lt PARAM contains the raw values telemetered from the floats The values in lt gt should never be altered lt PARAM gt contains qc flags that pertain to the values in lt PARAM gt Values in lt PARAM gt set initially in R and modes 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 delayed mode but also in real time if appropriate In that case lt 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 gt ADJUSTED lt PARAM gt ADJUSTED QC and lt PARAM gt ADJUSTED ERROR The A
92. on 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 Notes 1 We need to have a pragmatic approach 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 10db resolution 2 The conversion 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 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
93. ory file of the Argo Global Data Assembly Center 3t Description The directory file describes all profile 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 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 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 AO 20030214155354 aoml 13857 profiles R13857_003 nc 199708201845 0 543 19 622 A 0845 AO 20030214155619 Argo data management User s manual 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 8 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 A table with a description of each file of t
94. owing 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 2 3 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 data were collected and made freely available by the international Argo project and the national programs that contribute 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
95. pecified in the reference table 3 PARAM ADJUSTED is mandatory When no adjustment is performed the FillValue is inserted PARAM ADJUSTED char PARAM ADJUSTED QC N PROF LEVELS QC lt PARAM gt _ADJ USTED FORTRAN_ format lt X gt lt PARAM gt _ADJ USTED resolution X Quality flag applied on each lt PARAM gt _ADJ USTED values The flag scale is specified in reference lt PARAM gt _ADJ USTED_QC long_name quality flag lt gt ADJUSTED QC conventions Argo Argo data management reference table 2 PARAM ADJUSTED QC FillValue table 2 PARAM ADJUSTED QC is mandatory When no adjustment is performed the FillValue is inserted User s manual PARAM ADJUSTED ERROR contains N LEVELS the error on the adjusted values of the lt gt ADJUSTED ERROR long name lt 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 PARAM gt _AD USTED_ERROR comment Contains the lt gt ADJUSTED ERROR is error on the adjusted values as determined by the mandatory When no adjustment is delayed mode QC process performed the FillValue is inserted PARAM ADJUSTED ERROR C format lt X gt lt gt ADJUSTED ERROR FORTRAN format lt gt lt PARAM gt _ADJ USTED_ERROR resolution X
96. r ocationproblems the float may have had ANOMALY FillValue documented in the reference table 8 Example 846 Webb Research float Seabird sensor Direction of the profiles of the float ascending profiles only descending and ascending profiles 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 User s manual 2 4 4 Float deployment and mission information Name LAUNCH DATE LAUNCH LATITUDE LAUNCH LONGITUDE LAUNCH QC START DATE START DATE QC DEPLOY PLATFORM DEPLOY MISSION DEPLOY AVAILABLE PRO FILE ID END MISSION DATE END MISSION STATUS Argo data management 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 val
97. rgo profile delayed mode QC is described in Argo quality control manual by Annie Wong et Al Name Definition lt PARAM gt float lt PARAM gt N_PROF N_LEVELS lt PARAM gt long_name lt X gt PARAM FillValue X PARAM units lt X gt PARAM valid min X PARAM valid max X lt PARAM gt comment lt X gt lt PARAM gt C_format lt X gt lt PARAM gt FORTRAN_format lt X gt lt PARAM gt resolution lt X gt 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 values lt PARAM gt _QC conventions Argo reference table 2 The flag scale is specified in table 2 lt PARAM gt QC FillValue float lt gt ADJUSTED N PROF N_LEVELS lt gt ADJUSTED long name lt X gt lt PARAM gt contains the original values of a parameter listed reference table 3 X this field is specified in the reference table 3 PARAM QC lt gt ADJUSTED PARAM ADJUSTED contains the adjusted values derived from the original lt gt ADJUSTED FillValue X PARAM ADJUSTED units lt X gt lt gt ADJUSTED valid min X lt gt ADJUSTED valid max X lt gt ADJUSTED comment X lt gt ADJUSTED C format lt gt values of the parameter X this field is s
98. rom a fixed pressure to surface e g 2000 decibars e Asurface 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 Argo data management User s manual launch surface drift 77 descent to profile depth 1500 dbar drift at parking depth 2000 dbar lt shorter cycle than nominal cycle 0 cycle 1 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 Cycle naming 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
99. s 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 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 Date and time UTC of creation of this file Format YYYYMMDDHHMI SS 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 User s manual 6 2 6 3 Technical data This section contains a set of technical data for each profile There are TECH PARAM eg 25 technical parameters recorded for each cycle 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 32 characters The naming convention for TECHNICAL PARAMETER NAME is e Upper case letters only e No space in the name use underscore Definition Comment TECHNICAL PARAMETER NAME char Name of the technical parameter TECHNICAL PARAMETER NAME Example N CYCLE N TECH PARAM BATTERY VOLTAGE STRING32 See reference table 14 for standard technical parameter TECHNICAL PARAMETER names ong name Name of technical parameters for this cycle TECHNICAL PARAMETER NAME FillValue
100. scription 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 2 6 technical data format 2 3 82 8 2 profile directory file format version 2 1 83 3 add BPHASE DOXY 83 3 remark on unit conversion of oxygen 6 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 27 11 2009 51 1 Notice on file format change chapter added 81 2 User Obligations chapter added 81 3 Disclaimer chapter added 81 4 Further information sources and contact information chapter added 52 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 82 8 2 Profile directory file format statement transition added 53 2 1 add a reference to quality control manual 83 11 add descripion of table11 Add a new column in the table to explain the link between QC test bi
101. sion MEASUREMENT is the number of locations or measurement received from the float When no parameter is measured along the trajectory N PARAM number of parameters and any field with a PARAM dimension are removed from the file PARAM PARAM QC PARAM ADJUSTED PARAM ADJUSTED QC PARAM ADJUSTED ERROR and TRAJECTORY PARAMETERS lt PARAM 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 PARAM gt Values in lt PARAM QC gt are set initially in R and A modes 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 PARAM gt ADJUSTED QC contains the QC flags set by the delayed mode process and lt PARAM gt ADJUSTED ERROR contains the adjustment uncertainties A file with no adjusted data contains adjusted sections with fill values lt gt ADJUSTED lt PARAM gt ADJUSTED QC and lt PARAM gt ADJUSTED ERROR Definition Comment double JULD N MEASUREMENT Julian day of the location or measurement JULD long_name Julian day UTC of each The integer part represents the day the decimal part measurement relative
102. ssing the data have passed through DATA STATE INDICATOR conventions Argo reference table 6 DATA STATE INDICATOR FillValue char INST REFERENCE STRING64 INST REFERENCE long name Instrument type INST REFERENCE conventions Brand type serial number INST REFERENCE FillValue char WMO INST TYPE STRING4A WMO INST TYPE long name Coded instrument type WMO INST TYPE conventions Argo reference table 8 WMO INST TYPE FillValue char POSITIONING_SYSTEM STRING8 POSITIONING SYSTEM long name Positioning system POSITIONING SYSTEM FillValue CNDC conductvity 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 Degree of processing the data has passed through The data state indicator is described in the reference table 6 Information about instrument brand type serial number Example APEX SBE 259 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 Examples ARGOS User s manual a 2 3 4 Locations and measurements from the float This section contains locations for one Argo float It may also contain measurements performed along the trajectory Each field in this section has a N MEASUREMENT dimen
103. te This table is a comma separated list Argo data management User s manual Trajectory directory format definition Title Trajectory directory file of the Argo Global Data Assembly Center 3t 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 YYYYMMDDHHMISS 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 e 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 3t 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 FTP root number 1 ftp ftp ifremer
104. te of update ftp root addresses GDAC node e A table with a description of each file of the GDAC ftp site This table is a comma separated list 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 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 e file 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 ate date of the profile YYYYMMDDHHMISS ill value blank itude longitude location of the profile ill value 99999 code of the ocean of the profile as described in reference table 13 ill value blank rofiler type type of profiling float as described in reference table 8 ill 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 Each line describes a file of the gdac ftp site Profile directory format example Title Profile direct
105. tifier A911111 PLATFORM NUMBER FillValue char PROJ ECT_NAME STRING64 PROJECT NAME comment Name of the project PROJECT NAME FillValue char NAME STRING64 NAME comment Name of the principal investigator FillValue char TRAJ ECTORY PARAMETERS N PARAM S TRING16 TRAJECTORY PARAMETERS long_name List of available parameters for the 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 TEMP PSAL CNDC TEMP temperature PSAL practical salinit User s manual DATA_CENTRE DATA_STATE_INDICATOR INST_REFERENCE WMO_INST_TYPE POSITIONING_SYSTEM Argo data management station TRAJ ECTORY_PARAMETERS conventions Argo reference table 3 TRAJECTORY PARAMETERS FillValue char DATA CENTRE STRI NG2 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 INDI CATOR STRING4 DATA STATE INDICATOR long name Degree of proce
106. umber 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 6 1 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 YY YYMMDDHHMISS YYYY year MM month DD day HH hour of the day MI minutes SS seconds Examples 20010105172834 January 57 2001 17 28 34 19971217000000 December 177 1997 00 00 00 STRING256 STRING256 256 String dimensions from 2 to 256 STRING128 STRING128 128 STRING64 STRING64 64 STRING32 STRING32 32 STRING16 STRING16 16 STRING8 STRING8 8 STRING4 STRING4 STRING2 STRING2 N_TECH_PARAM N_TECH_PARAM lt int Number of technical parameters value gt Example N_TECH_PARAM 25 Twenty five different parameters are recorded for each cycle N_CYCLE N_CYCLE UNLIMITED Number of cycles performed by the float Argo data management User s manual 2 6 2 General information on the technical data file This section contains information about the technical data file itself PLATFORM_NUMBER DATA_TYPE FORMAT_VERSION HANDBOOK_VERSION DA
107. ure PARKING TIME units decimal hour PARKING TIME FillValue 99999 f float DESCENDING PROFILING TIME N CYCLES DESCENDING PROFILING TIME long name The time spent sampling the descending profile DESCENDING PROFILING TIME units decimal hour DESCENDING PROFILING TIME FillValue 99999 f float ASCENDING PROFILING TIME N CYCLES ASCENDING PROFILING TIME long name The time spent sampling the ascending profile ASCENDING PROFILING TIME units decimal hour ASCENDING PROFILING TIME FillValue 99999 f float SURFACE TIME N CYCLES SURFACE TIME long name The time spent at the surface SURFACE TIME units decimal hour SURFACE TIME FillValue 99999 f float PARKING PRESSURE N CYCLES PARKING PRESSURE long name The pressure of subsurface drifts PARKING PRESSURE units decibar PARKING PRESSURE FillValue 99999 f float DEEPEST_PRESSURE N_CYCLES DEEPEST PRESSURE long name The deepest pressure sampled in the ascending profile DEEPEST_PRESSURE units decibar DEEPEST PRESSURE FillValue 99999 f float DEEPEST_PRESSURE_DESCENDING N_CYCLES DEEPEST PRESSURE DESCENDING long name The deepest pressure sampled in the descending profile DEEPEST PRESSURE DESCENDING units decibar DEEPEST PRESSURE DESCENDING FillValue 99999 f Comment Number of times this cycle repeats Usually REPETITION RATE and N CYCLE are set to 1 all the cycles are programmed to be the same

Download Pdf Manuals

Related Search

Related Contents

Targus VuComplete  Colocar a barra de som SB26  Documento PDF - Università degli Studi di Padova  Mode d`emploi  Cuisinart DGB900BCU coffee maker  IRTR203 Mk2.qxd    

Copyright © All rights reserved. Failed to retrieve file