Best practices for Core Argo floats - Part 2: physical handling, deployment and metadata considerations
| Type | Article | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Date | 2024-04-03 | ||||||||
| Language | English | ||||||||
| Author(s) | Morris Tamaryn1, 2, Scanderbeg Megan3, West-Mack Deborah4, Gourcuff Claire5, Poffa Noe6, Udaya Bhaskar Tata V. S.7, Hanstein Craig8, Diggs Steve3, Talley Lynne3, Turpin Victor9, Liu Zenghong10, Owens Breck4 | ||||||||
| Affiliation(s) | 1 : Egagasini Node, South African Environmental Observation Network (SAEON), Cape Town, South Africa 2 : Marine Unit, South African Weather Service (SAWS), Cape Town, South Africa 3 : Climate, Atmospheric Sciences and Physical Oceanography Department, Scripps Institution of Oceanography (SIO), San Diego, CA, United States 4 : Physical Oceanography Department, Woods Hole Oceanographic Institute (WHOI), Falmouth, MA, United States 5 : Euro-Argo European Research Infrastructure Consortium (ERIC), Plouzané, France 6 : Institut Français de Recherche pour l'Exploitation de la Mer (Ifremer), Plouzané, France 7 : Indian National Centre for Ocean Information Services (INCOIS), MoES, Hyderabad, India 8 : Commonwealth Scientific and Industrial Research Organisation (CSIRO), Hobart, TAS, Australia 9 : OceanOPS, Brest, France 10 : Second Institute of Oceanography, Ministry of Natural Resources, Hangzhou, Zhejiang, China |
||||||||
| Source | Frontiers in Marine Science (2296-7745) (Frontiers Media SA), 2024-04-03 , Vol. 11 , P. 1358048 (9p.) | ||||||||
| DOI | 10.3389/fmars.2024.1358048 | ||||||||
| Keyword(s) | Core Argo float, best practice, physical handling, deployment, metadata | ||||||||
| Abstract | Following on from Part 1: Best Practices for Core Argo floats - Getting started and data considerations, we present Part 2: Best Practices for Core Argo floats in terms of physical handling and deployments and recommended metadata parameters. The objective is to encourage new and developing scientists, research teams and institutions to contribute to the OneArgo Program through increased deployments regionally, specifically to the Core Argo mission. Only by leveraging sustained contributions of current Core Argo float groups with new and emerging Argo teams and users, can the OneArgo initiative be realized. This paper makes involvement with the Core Argo mission smoother by providing a framework endorsed by a wide community for these observations. |
||||||||
| Full Text |
|