Cruise: 35MF19860401 (dataset:CARBOOCEAN) Data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Synonyms (including errata!) for this cruise: INDIGO-2; 35MF19860401; INDIGO-2;
IMPORTANT information for GLODAP Reference Group Editors: This adjustment is a published version for GLODAPv2!
Please wait while loading list of related files
Filename: | Comment: | Action | |
---|---|---|---|
offsets.png | [autogenerated from RC_Toste/adjustments!] |
View |
- no files! -
Plot/Data files re. Parameter(s) (select parameter on left side to view!):
alkalinity:3
cruise:1
nitrate:5
oxygen:2
phosphate:3
salinity:2
silicate:2
tco2:5
- no files! -
Filename: | Comment: | Action | |
---|---|---|---|
Xover.png | [Copy of salinity plot for crossover: 35MF19850401 / 318M19771216!]; [autogenerated from running_cluster_toste/salinity!] |
View | |
Xover.png | [Copy of salinity plot for crossover: 316N19951230 / 35MF19850401!]; [autogenerated from running_cluster_toste/salinity!] |
View |
View comment(s) (filtered by salinity in subject)
Autogenerated CTD salinity and CTD oxygen update
Automated update! This overwrites adjustment values (and flags) of CTDoxy and
CTDsal with the values from BOTsal and BOToxy for every cruise, unless CTDsal
(or CTDoxy) is not present or bad.
Salinity action ID:3; no CTD salinity data. Setting CTD salinity offset to -999,
QC flag removed.
Oxygen action ID:3; no CTD oxygen data. Setting CTD oxygen offset to -999, QC
flag removed.
Posted by svheuven@gmail.com on 2015-02-19 09:22:26 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19860401/salinity: update slope+intercept
autogenerated: only BOTsal available (no CTDsal)
Posted by svheuven@gmail.com on 2014-12-18 16:52:44 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - salinity
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2 Adjustment IND and PAC_SvH_extra_legs_20140704): : maintain
Posted by svheuven@gmail.com on 2014-07-04 14:42:25 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19850401 - salinity
Offset with 3 cruises: +0.5 ppm
Inversion suggests: -0.7 ppm
Orig. GLODAP applied: -1 ppm
We suggest NO adjustment
Posted by mario.hoppema@awi.de on 2012-07-24 14:12:26 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View comment(s) (filtered by ctd_salinity in subject)
Autogenerated CTD salinity and CTD oxygen update
Automated update! This overwrites adjustment values (and flags) of CTDoxy and
CTDsal with the values from BOTsal and BOToxy for every cruise, unless CTDsal
(or CTDoxy) is not present or bad.
Salinity action ID:3; no CTD salinity data. Setting CTD salinity offset to -999,
QC flag removed.
Oxygen action ID:3; no CTD oxygen data. Setting CTD oxygen offset to -999, QC
flag removed.
Posted by svheuven@gmail.com on 2015-02-19 09:22:26 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Filename: | Comment: | Action | |
---|---|---|---|
Xover.png | [Copy of tco2 plot for crossover: 35MF19850401 / 318M19771216!]; [autogenerated from running_cluster_toste/tco2!] |
View | |
Xover.png | [Copy of tco2 plot for crossover: 316N19951230 / 35MF19850401!]; [autogenerated from running_cluster_toste/tco2!] |
View | |
Xover.png | [Copy of tco2 plot for crossover: 316N19950715 / 35MF19850401!]; [autogenerated from running_cluster_toste/tco2!] |
View | |
Xover.png | [Copy of tco2 plot for crossover: 316N19950611 / 35MF19850401!]; [autogenerated from running_cluster_toste/tco2!] |
View | |
Xover.png | [Copy of tco2 plot for crossover: 316N19950423 / 35MF19850401!]; [autogenerated from running_cluster_toste/tco2!] |
View |
View comment(s) (filtered by tco2 in subject)
Autogenerated comment - tCO2
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2 Adjustment IND and PAC_SvH_extra_legs_20140704): : maintain earlier
adjustments suggested by Mario
Posted by svheuven@gmail.com on 2014-07-04 14:42:25 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19850401 - tco2
This cruise is consistently too high in TCO2. GLODAP suggested -9.4; CARINA
suggested 0. The evidence from this set of data support the adjustment applied
to GLODAP.
We suggest to apply an adjustment of -10, similar to INDIGO-1
Posted by ttanhua@geomar.de on 2012-08-01 14:44:43 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Filename: | Comment: | Action | |
---|---|---|---|
Xover.png | [Copy of alkalinity plot for crossover: 316N19950715 / 35MF19850401!]; [autogenerated from running_cluster_toste/alkalinity!] |
View | |
Xover.png | [Copy of alkalinity plot for crossover: 316N19951230 / 35MF19850401!]; [autogenerated from running_cluster_toste/alkalinity!] |
View | |
Xover.png | [Copy of alkalinity plot for crossover: 35MF19850401 / 318M19771216!]; [autogenerated from running_cluster_toste/alkalinity!] |
View |
View comment(s) (filtered by alkalinity in subject)
Autogenerated comment - alkalinity
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2 Adjustment IND and PAC_SvH_extra_legs_20140704): : Make +10. Clearly is
8-12 too low, make +10
Posted by svheuven@gmail.com on 2014-07-04 14:42:25 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19850401 - alkalinity
Offset with 3 cruises: -9.2
Inversion suggests: +7.5
Orig GLODAP applied +6.8
CARINA suggested: +7
We suggest an adjustment of +7, ageeing with all analyses.
Posted by mario.hoppema@awi.de on 2012-07-24 14:35:10 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View comment(s) (filtered by ph in subject)
Autogenerated comment - phosphate
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2 Adjustment IND and PAC_SvH_extra_legs_20140704): : Maintain Mario's
0.98. I didn't split this cruise into its three constituent legs, so Mario's
analysis likely was more appropriate
Posted by svheuven@gmail.com on 2014-07-04 14:42:25 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19850401 - phosphate
Offset with 3 cruises: 1.03
Inversion suggests: 0.987
No data from orig. GLODAP and CARINA.
The xovers are consistently high which clearly justifies a correction. We thus
suggest an adjustment of: 0.98
Posted by mario.hoppema@awi.de on 2012-07-24 14:47:41 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Filename: | Comment: | Action | |
---|---|---|---|
Xover.png | [Copy of nitrate plot for crossover: 316N19950715 / 35MF19850401!]; [autogenerated from running_cluster_toste/nitrate!] |
View | |
Xover.png | [Copy of nitrate plot for crossover: 316N19950611 / 35MF19850401!]; [autogenerated from running_cluster_toste/nitrate!] |
View | |
Xover.png | [Copy of nitrate plot for crossover: 316N19950423 / 35MF19850401!]; [autogenerated from running_cluster_toste/nitrate!] |
View | |
Xover.png | [Copy of nitrate plot for crossover: 316N19951230 / 35MF19850401!]; [autogenerated from running_cluster_toste/nitrate!] |
View | |
Xover.png | [Copy of nitrate plot for crossover: 35MF19850401 / 318M19771216!]; [autogenerated from running_cluster_toste/nitrate!] |
View |
View comment(s) (filtered by nitrate in subject)
Autogenerated comment - nitrate
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2 Adjustment IND and PAC_SvH_extra_legs_20140704): : Maintain Mario's
1.02. I didn't split this cruise into its three constituent legs, so Mario's
analysis likely was more appropriate
Posted by svheuven@gmail.com on 2014-07-04 14:42:25 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19850401 - nitrate
Offset with 3 cruises: 0.979
Inversion suggests: 1.025
No data from orig GLODAp or CARINA.
This cruise appears to be consistently low, also compared to other cruises,
which do not have enough stations for calculating a number for the xover.
We suggest an adjustment of 1.02
Posted by mario.hoppema@awi.de on 2012-07-24 14:40:49 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Filename: | Comment: | Action | |
---|---|---|---|
Xover.png | [Copy of phosphate plot for crossover: 316N19950715 / 35MF19850401!]; [autogenerated from running_cluster_toste/phosphate!] |
View | |
Xover.png | [Copy of phosphate plot for crossover: 316N19951230 / 35MF19850401!]; [autogenerated from running_cluster_toste/phosphate!] |
View | |
Xover.png | [Copy of phosphate plot for crossover: 35MF19850401 / 318M19771216!]; [autogenerated from running_cluster_toste/phosphate!] |
View |
View comment(s) (filtered by phosphate in subject)
Autogenerated comment - phosphate
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2 Adjustment IND and PAC_SvH_extra_legs_20140704): : Maintain Mario's
0.98. I didn't split this cruise into its three constituent legs, so Mario's
analysis likely was more appropriate
Posted by svheuven@gmail.com on 2014-07-04 14:42:25 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19850401 - phosphate
Offset with 3 cruises: 1.03
Inversion suggests: 0.987
No data from orig. GLODAP and CARINA.
The xovers are consistently high which clearly justifies a correction. We thus
suggest an adjustment of: 0.98
Posted by mario.hoppema@awi.de on 2012-07-24 14:47:41 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Filename: | Comment: | Action | |
---|---|---|---|
Xover.png | [Copy of silicate plot for crossover: 316N19951230 / 35MF19850401!]; [autogenerated from running_cluster_toste/silicate!] |
View | |
Xover.png | [Copy of silicate plot for crossover: 35MF19850401 / 318M19771216!]; [autogenerated from running_cluster_toste/silicate!] |
View |
View comment(s) (filtered by silicate in subject)
Autogenerated comment - silicate
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2 Adjustment IND and PAC_SvH_extra_legs_20140704): : Maintain 1.00
Posted by svheuven@gmail.com on 2014-07-04 14:42:25 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19850401 - silicate
Offset with 3 cruises: 1.009
Inversion suggests: 0.984
No data from orig. GLODAP and CARINA.
The only small offset does not justify an adjustment, i.e., we suggest NO
adjustment.
Posted by mario.hoppema@awi.de on 2012-07-24 14:51:51 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Filename: | Comment: | Action | |
---|---|---|---|
Xover.png | [Copy of oxygen plot for crossover: 35MF19850401 / 318M19771216!]; [autogenerated from running_cluster_toste/oxygen!] |
View | |
Xover.png | [Copy of oxygen plot for crossover: 316N19950715 / 35MF19850401!]; [autogenerated from running_cluster_toste/oxygen!] |
View |
View comment(s) (filtered by oxygen in subject)
Autogenerated CTD salinity and CTD oxygen update
Automated update! This overwrites adjustment values (and flags) of CTDoxy and
CTDsal with the values from BOTsal and BOToxy for every cruise, unless CTDsal
(or CTDoxy) is not present or bad.
Salinity action ID:3; no CTD salinity data. Setting CTD salinity offset to -999,
QC flag removed.
Oxygen action ID:3; no CTD oxygen data. Setting CTD oxygen offset to -999, QC
flag removed.
Posted by svheuven@gmail.com on 2015-02-19 09:22:26 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19860401/oxygen: update slope+intercept
autogenerated: only BOToxy available (no CTDoxy)
Posted by svheuven@gmail.com on 2014-12-18 16:52:44 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - oxygen
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2 Adjustment IND and PAC_SvH_extra_legs_20140704): : maintain
Posted by svheuven@gmail.com on 2014-07-04 14:42:25 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19850401 - oxygen
Offset with 3 cruises: 1.005
Inversion suggests: 0.999
Orig. GLODAP applied small +0.018 (additive; which is much smaller than 1%).
We suggests NO adjustment
Posted by mario.hoppema@awi.de on 2012-07-24 14:54:33 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View comment(s) (filtered by ctd_oxygen in subject)
Autogenerated CTD salinity and CTD oxygen update
Automated update! This overwrites adjustment values (and flags) of CTDoxy and
CTDsal with the values from BOTsal and BOToxy for every cruise, unless CTDsal
(or CTDoxy) is not present or bad.
Salinity action ID:3; no CTD salinity data. Setting CTD salinity offset to -999,
QC flag removed.
Oxygen action ID:3; no CTD oxygen data. Setting CTD oxygen offset to -999, QC
flag removed.
Posted by svheuven@gmail.com on 2015-02-19 09:22:26 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View comment(s) (filtered by cfc12 in subject)
35MF19860401 - cfc12
The concentrations are very low, which may be due to the location, around
Africa's horn (upwelling?). There is no obvious deviation from the CFC11-CFC12
relationship, but this may be difficult to observe due to the low values. The
surface saturations, however, are highly inconsistent: for CFC12 ~80% and for
CFC11 ~105%, implying too high CFC11 or too low CFC12. In addition the deep
water concentrations are close to zero. To increase consistency we recommend an
adjustment of CFC12 of 1.1 (and CFC11 with 0.9). This should be evaluated
further in the final analysis. (And experts on the area should be consulted
before final adjustments are applied.)
Posted by emje@norceresearch.no on 2013-01-08 17:19:12 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View comment(s) (filtered by cfc11 in subject)
35MF19860401 - cfc11
The concentrations are very low, which may be due to the location, around
Africa's horn (upwelling?). There is no obvious deviation from the CFC11-CFC12
relationship, but this may be difficult to observe due to the low values. The
surface saturations, however, are highly inconsistent: for CFC12 ~80% and for
CFC11 ~105%, implying too high CFC11 or too low CFC12. In addition the deep
water concentrations are close to zero. To increase consistency we recommend an
adjustment of CFC12 of 1.1 (and CFC11 with 0.9). This should be evaluated
further in the final analysis. (And experts on the area should be consulted
before final adjustments are applied.)
Posted by emje@norceresearch.no on 2013-01-08 17:19:21 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View 19 comment(s) (Lists all comments)
Autogenerated CTD salinity and CTD oxygen update
Automated update! This overwrites adjustment values (and flags) of CTDoxy and
CTDsal with the values from BOTsal and BOToxy for every cruise, unless CTDsal
(or CTDoxy) is not present or bad.
Salinity action ID:3; no CTD salinity data. Setting CTD salinity offset to -999,
QC flag removed.
Oxygen action ID:3; no CTD oxygen data. Setting CTD oxygen offset to -999, QC
flag removed.
Posted by svheuven@gmail.com on 2015-02-19 09:22:26 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19860401/oxygen: update slope+intercept
autogenerated: only BOToxy available (no CTDoxy)
Posted by svheuven@gmail.com on 2014-12-18 16:52:44 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19860401/salinity: update slope+intercept
autogenerated: only BOTsal available (no CTDsal)
Posted by svheuven@gmail.com on 2014-12-18 16:52:44 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - oxygen
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2 Adjustment IND and PAC_SvH_extra_legs_20140704): : maintain
Posted by svheuven@gmail.com on 2014-07-04 14:42:25 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - silicate
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2 Adjustment IND and PAC_SvH_extra_legs_20140704): : Maintain 1.00
Posted by svheuven@gmail.com on 2014-07-04 14:42:25 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - phosphate
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2 Adjustment IND and PAC_SvH_extra_legs_20140704): : Maintain Mario's
0.98. I didn't split this cruise into its three constituent legs, so Mario's
analysis likely was more appropriate
Posted by svheuven@gmail.com on 2014-07-04 14:42:25 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - nitrate
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2 Adjustment IND and PAC_SvH_extra_legs_20140704): : Maintain Mario's
1.02. I didn't split this cruise into its three constituent legs, so Mario's
analysis likely was more appropriate
Posted by svheuven@gmail.com on 2014-07-04 14:42:25 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - alkalinity
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2 Adjustment IND and PAC_SvH_extra_legs_20140704): : Make +10. Clearly is
8-12 too low, make +10
Posted by svheuven@gmail.com on 2014-07-04 14:42:25 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - tCO2
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2 Adjustment IND and PAC_SvH_extra_legs_20140704): : maintain earlier
adjustments suggested by Mario
Posted by svheuven@gmail.com on 2014-07-04 14:42:25 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - salinity
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2 Adjustment IND and PAC_SvH_extra_legs_20140704): : maintain
Posted by svheuven@gmail.com on 2014-07-04 14:42:25 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19860401 - cfc11
The concentrations are very low, which may be due to the location, around
Africa's horn (upwelling?). There is no obvious deviation from the CFC11-CFC12
relationship, but this may be difficult to observe due to the low values. The
surface saturations, however, are highly inconsistent: for CFC12 ~80% and for
CFC11 ~105%, implying too high CFC11 or too low CFC12. In addition the deep
water concentrations are close to zero. To increase consistency we recommend an
adjustment of CFC12 of 1.1 (and CFC11 with 0.9). This should be evaluated
further in the final analysis. (And experts on the area should be consulted
before final adjustments are applied.)
Posted by emje@norceresearch.no on 2013-01-08 17:19:21 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19860401 - cfc12
The concentrations are very low, which may be due to the location, around
Africa's horn (upwelling?). There is no obvious deviation from the CFC11-CFC12
relationship, but this may be difficult to observe due to the low values. The
surface saturations, however, are highly inconsistent: for CFC12 ~80% and for
CFC11 ~105%, implying too high CFC11 or too low CFC12. In addition the deep
water concentrations are close to zero. To increase consistency we recommend an
adjustment of CFC12 of 1.1 (and CFC11 with 0.9). This should be evaluated
further in the final analysis. (And experts on the area should be consulted
before final adjustments are applied.)
Posted by emje@norceresearch.no on 2013-01-08 17:19:12 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19850401 - tco2
This cruise is consistently too high in TCO2. GLODAP suggested -9.4; CARINA
suggested 0. The evidence from this set of data support the adjustment applied
to GLODAP.
We suggest to apply an adjustment of -10, similar to INDIGO-1
Posted by ttanhua@geomar.de on 2012-08-01 14:44:43 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19850401 - oxygen
Offset with 3 cruises: 1.005
Inversion suggests: 0.999
Orig. GLODAP applied small +0.018 (additive; which is much smaller than 1%).
We suggests NO adjustment
Posted by mario.hoppema@awi.de on 2012-07-24 14:54:33 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19850401 - silicate
Offset with 3 cruises: 1.009
Inversion suggests: 0.984
No data from orig. GLODAP and CARINA.
The only small offset does not justify an adjustment, i.e., we suggest NO
adjustment.
Posted by mario.hoppema@awi.de on 2012-07-24 14:51:51 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19850401 - phosphate
Offset with 3 cruises: 1.03
Inversion suggests: 0.987
No data from orig. GLODAP and CARINA.
The xovers are consistently high which clearly justifies a correction. We thus
suggest an adjustment of: 0.98
Posted by mario.hoppema@awi.de on 2012-07-24 14:47:41 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19850401 - nitrate
Offset with 3 cruises: 0.979
Inversion suggests: 1.025
No data from orig GLODAp or CARINA.
This cruise appears to be consistently low, also compared to other cruises,
which do not have enough stations for calculating a number for the xover.
We suggest an adjustment of 1.02
Posted by mario.hoppema@awi.de on 2012-07-24 14:40:49 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19850401 - alkalinity
Offset with 3 cruises: -9.2
Inversion suggests: +7.5
Orig GLODAP applied +6.8
CARINA suggested: +7
We suggest an adjustment of +7, ageeing with all analyses.
Posted by mario.hoppema@awi.de on 2012-07-24 14:35:10 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19850401 - salinity
Offset with 3 cruises: +0.5 ppm
Inversion suggests: -0.7 ppm
Orig. GLODAP applied: -1 ppm
We suggest NO adjustment
Posted by mario.hoppema@awi.de on 2012-07-24 14:12:26 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Hide comments