Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

RBR CTD sensor on Deep Apex float #105

Closed
matdon17 opened this issue Mar 18, 2021 · 4 comments
Closed

RBR CTD sensor on Deep Apex float #105

matdon17 opened this issue Mar 18, 2021 · 4 comments
Assignees
@vturpin
Labels
avtt Argo Vocabulary Task Team

Comments

@matdon17
Copy link

The UK has deployed what I think is the first Deep Apex float equipped with an RBR sensors, see:
https://www.ocean-ops.org/board/wa/Platform?ref=6903755

As a result none of the existing WMO instrument type codes are appropriate:

  • 877 is for an APEX with RBR CTD
  • 849 is for an APEX-D (Deep) with SBE CTD

Could a new code be created for APEX-D with an RBR CTD?
@vpaba vpaba added the avtt Argo Vocabulary Task Team label Jun 3, 2021
@tcarval
Copy link
Contributor

tcarval commented Dec 6, 2022

Hi @vturpin , can you (should you?) require a wmo plaform code for APEX_D RBR ?

@vturpin vturpin mentioned this issue Dec 6, 2022
Closed
@vturpin
Copy link

vturpin commented Dec 6, 2022

Submitted here : wmo-im/CCT#115

@vturpin
Copy link

vturpin commented Jun 6, 2023

New id: 883 "APEX_D RBR"

tcarval referenced this issue in OneArgo/ArgoFormatChecker Oct 19, 2023
@tcarval
R08: 883 APEX_D
8fe35ad 
More on https://github.com/nvs-vocabs/R08/issues/2
@tcarval
Copy link
Contributor

tcarval commented Oct 19, 2023

Done on checker, nvs and github

@tcarval tcarval closed this as completed Oct 19, 2023
@tcarval tcarval transferred this issue from nvs-vocabs/R08 Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vturpin vturpin

Labels
avtt Argo Vocabulary Task Team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@tcarval @matdon17 @vpaba @vturpin