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.

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

Additional bio-geochemical sequences for data from Argo profiling floats #5

Closed
efucile opened this issue Mar 30, 2020 · 14 comments
Closed

Comments

@efucile
Copy link
Member

efucile commented Mar 30, 2020

Branch

branch to be added later when target milestone is set

Proposal

Add entries:

in BUFR/CREX Table B,
Class 13 – Hydrographic and hydrological elements
Table reference Element name BUFR CREX
F XX YYY Unit Scale Ref. value Data width (bits) Units Scale Data width (characters)
0 13 161 pH scale Code table 0 0 3 Code table 0 1

Class 41 – Marine bio-geochemical data
Table reference Element name BUFR CREX
F XX YYY Unit Scale Ref. value Data width (bits) Units Scale Data width (characters)
0 41 006 Backscattering m-1 5 0 19 m-1 5 6

in BUFR Table D,
Sequence 3-06-044 for chlorophyll-A profile data

Table Reference Table References Element Name
F X Y
3 06 044 (Chlorophyll-A (fluorescence) profile data)
1 09 000 Delayed replication of 9 descriptors
0 31 002 Extended delayed descriptor replication factor Gives number of depths
0 07 062 Depth below sea / water surface Code as missing
0 08 080 Qualifier for quality class Code as missing
0 33 050 GTSPP quality class Code as missing
0 07 065 Water pressure
0 08 080 Qualifier for quality class (set to 10, indicates pressure at a level)
0 33 050 GTSPP quality class
0 41 002 Chlorophyll-A (fluorescence) In kg l-1 (= 109 mg m-3)
0 08 080 Qualifier for quality class (set to 21, chlorophyll-A at a level)
0 33 050 GTSPP quality class

Code depth related descriptors as missing as water pressure is used as the vertical axis
Chlorophyll-A specified in range 0 to 65.535 mg m-3 with a resolution of 0.001 mg m-3.

Sequence 3-06-045 for dissolved nitrate profile data

Table Reference Table References Element Name
F X Y
3 06 045 (Dissolved nitrate profile data)
1 09 000 Delayed replication of 9 descriptors
0 31 002 Extended delayed descriptor replication factor Gives number of depths
0 07 062 Depth below sea / water surface Code as missing
0 08 080 Qualifier for quality class Code as missing
0 33 050 GTSPP quality class Code as missing
0 07 065 Water pressure
0 08 080 Qualifier for quality class (set to 10, indicates pressure at a level)
0 33 050 GTSPP quality class
0 41 003 Dissolved nitrate In μmol kg-1
0 08 080 Qualifier for quality class (set to 22, nitrate at a level)
0 33 050 GTSPP quality class

Code depth related descriptors as missing as water pressure is used as the vertical axis.

Sequence 3-06-046 for pH profile data

Table Reference Table References Element Name
F X Y
3 06 046 (pH profile data)
1 09 000 Delayed replication of 9 descriptors
0 31 002 Extended delayed descriptor replication factor Gives number of depths
0 07 062 Depth below sea / water surface Code as missing
0 08 080 Qualifier for quality class Code as missing
0 33 050 GTSPP quality class Code as missing
0 07 065 Water pressure
0 08 080 Qualifier for quality class (set to 10, indicates pressure at a level)
0 33 050 GTSPP quality class
0 13 161 pH scale
0 13 080 pH dimensionless
0 08 080 Qualifier for quality class (set to 23, pH at a level)
0 33 050 GTSPP quality class

Code depth related descriptors as missing as water pressure is used as the vertical axis.

Sequence 3-06-047 for backscattering profile data
Table Reference Table References Element Name
F X Y
3 06 047 (Backscatter profile data)
0 02 071 (Spectrographic) wavelength m
1 09 000 Delayed replication of 9 descriptors
0 31 002 Extended delayed descriptor replication factor Gives number of depths
0 07 062 Depth below sea / water surface Code as missing
0 08 080 Qualifier for quality class Code as missing
0 33 050 GTSPP quality class Code as missing
0 07 065 Water pressure
0 08 080 Qualifier for quality class (set to 10, indicates pressure at a level)
0 33 050 GTSPP quality class
0 41 006 Backscattering m-1
0 08 080 Qualifier for quality class (set to 24, backscatter at a level)
0 33 050 GTSPP quality class
Code depth related descriptors as missing as water pressure is used as the vertical axis.

in BUFR/CREX code tables,
0 02 149
Type of data buoy

Code figure Meaning
31 Coastal sub-surface float
32 Deep sub-surface float

0 08 080
Qualifier for GTSPP Quality Flag

Code figure Meaning
21 Chlorophyll-A at a level
22 Nitrate at a level
23 pH at a level
24 Backscattering at a level

0 22 067 (FT2017-2)
Instrument type for water temperature/salinity profile measurement

Code figure Meaning
835 PROVOR IV
836 PROVOR III
870 HM2000
871 COPEX
872 S2X
869 DOVA (no longer required)
870 NAMI (no longer required)
871 HM2000

Add a code table:
0 13 161
pH scale

Code figure Meaning
0 Seawater scale
1 Freescale
2 Total scale
3-6 Reserved
7 missing

@david-i-berry
Copy link
Member

Validation still waiting input / testing by Argo team.

@efucile efucile added this to the FT-2020-2 milestone May 7, 2020
@david-i-berry david-i-berry modified the milestones: FT-2020-2, FT-2021-1 May 7, 2020
@david-i-berry
Copy link
Member

I've moved to FT-2021-1 but doubt it will be done by then.

@amilan17
Copy link
Member

This issue needs a branch.

@amilan17
Copy link
Member

amilan17 commented Nov 5, 2020

Who is responsible for validation?

@marijanacrepulja
Copy link
Contributor

The branch is not updated with proposed BUFR entries.
I am happy to help with validation once the branch is ready.

@david-i-berry
Copy link
Member

The last time I checked (September / October of this year) there was still no progress to report. There may still be some changes to make so I would propose moving this back to in progress rather than in validation and changing the FT aimed for.

@amilan17
Copy link
Member

@jitsukoh @DavidBerryNOC 

Change target FT to 2021-2?

@jitsukoh
Copy link

@amilan17 I would prefer to set target FT when we know the validation process really starts. So if there is no update, I'd suggest not to add a target FT right now. It would be good if we can document this process (when and who add the target FT) to the Github status management document...

@amilan17 amilan17 removed this from the FT-2021-1 milestone Jan 22, 2021
@amilan17 amilan17 added this to the noTargetMilestone milestone Dec 9, 2021
@amilan17 amilan17 removed the branch label Apr 4, 2022
@amilan17
Copy link
Member

re: https://github.com/wmo-im/CCT/wiki/Teleconference-26-and-28.4.2022

Delayed by issue #16  (Glider template).

@JonTurton
Copy link

We recently resurrected this discussion at the Argo Data Management Team (ADMT) meeting on 6th December 2022. There is an action on ADMT-BGC team to advise on the range and precision required for the various BGC variables. This will then allow us to define the BUFR descriptors. The BGC profile sequences can then follow that already approved for dissolved oxygen. We should be able to define and test the new sequences during spring 2023. Several ADMT-BGC members have offered to participate in the validation process. ADMT will also consider whether only 'adjusted' values should be distributed on GTS in real-time, or whether all values with QC flags may be distributed.

@amilan17
Copy link
Member

@JonTurton, Can you please open a new issue with the updated proposal when it's ready? That new issue will then supersede this one. If you do this by March timeframe, it can be included in the FT2023-2 proposals that will be developed late spring/early summer of 2023.  Thanks!

@JonTurton
Copy link

@amilan17 , Hi Anna- I've just contacted colleagues in the ADMT to check on progress and when they anticipate providing us with the information required (units, range and precision) for each BGC variable. Once we have that putting together the sequences should be relatively straightforward if we follow that already used for dissolved oxygen (as its basically just changing the descriptor for the variable). Once we have that, I can open as a new issue, but we may not have all the info needed by March.

@JonTurton
Copy link

JonTurton commented Apr 12, 2023 via email

@amilan17
Copy link
Member

closing because issue is replaced by #155

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants