Cruise: 35MF20000117 (dataset:CARINA) Data product: GLODAPv3 Predecessor: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Synonyms (including errata!) for this cruise: OISO-4; 35MF20000117; OISO-4;
IMPORTANT information for GLODAP Reference Group Editors: This is the updated adjustment version (GLODAPv3) from GLODAPv2.2023! Click here to view previous (immutable) version (GLODAPv2.2023)
Please wait while loading list of related files


Plot/Data files re. Parameter(s) (select parameter on left side to view!):
nitrate:4
oxygen:4
salinity:4
tco2:4


| Filename: | Comment: | Action | |
|---|---|---|---|
| 35MF19981205_35MF20000117_salinity__Xover_SAL.png | [GLODAPv3 release: autogenerated from RC_Nico/salinity for: 35MF20000117[1-last] |
View | |
| 35MF20000117_35MF20000719_salinity__Xover_SAL.png | [GLODAPv3 release: autogenerated from RC_Nico/salinity for: 35MF20000117[1-last] |
View | |
| 35MF20000117_35MF20010103_salinity__Xover_SAL.png | [GLODAPv3 release: autogenerated from RC_Nico/salinity for: 35MF20000117[1-last] |
View | |
| 35MF20000117_35MF20020104_salinity__Xover_SAL.png | [GLODAPv3 release: autogenerated from RC_Nico/salinity for: 35MF20000117[1-last] |
View | |

View annotation(s) (filtered by salinity in subject)
GLODAPv3 release: autogenerated salinity update for 35MF20000117
GLODAPv3 release: salinity update of 35MF20000117 based on salinity_offset:
-888.0000; inversion: NaN; inversion_full: NaN; preadjustment: NaN; offsets_raw:
NaN; offsets_preadj: NaN; offsets_preadj_u: NaN; offsets_post: NaN;
offsets_post_u: NaN; offsets_post_rt: NaN; numberofxovers: NaN; trends_pre: NaN;
trends_adj: NaN.
Posted by nlange@geomar.de on 2026-08-04 17:11:43 UTC for data product: GLODAPv3
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:6; CTD salinity data good, setting CTD salinity offset and QC
flag to bottle values.
Oxygen action ID:5; CTD oxygen data good, setting CTD oxygen offset and QC flag
to bottle values.
Posted by svheuven@gmail.com on 2015-02-19 09:22:19 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20000117/salinity: update slope+intercept
autogenerated: BOTsal is compatible with CALIBRATED CTDsal
Posted by svheuven@gmail.com on 2014-12-18 16:52:44 UTC for data product: CARINA, 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_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20000117/salinity: init slope+intercept
autogenerated: using mean of BOTsal and UNCHANGED CTDsal
Posted by svheuven@gmail.com on 2014-02-25 17:02:15 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20000117 - salinity
OISO4: two deep profiles (at 30°S and 56°S).
Note: these 2 stations are treated as different cross overs in the analysis
below.
INTERNAL OISO CONSISTENCY:
11 cross overs were analyzed. The average of all cross overs is -4.0 (+/-9.2)
ppm.
7 cross overs show no significant differences (<5 ppm) and involve cruises that
are thought to have no significant offset in salinity. When the offsets
suggested for the other cruises are taken into account the average of all cross
overs is -0.9 (+/-1.9) ppm. This suggests that no adjustment would be required.
OTHER CROSS OVERS:
The cross overs with cruises INDIGO1 (30°S) and INDIGO3 (56°S) show offsets of
-3 (+/-9) ppm and -4 (+/-2) ppm, respectively, which supports no adjustment.
CONCLUSION:
Based on the regional analyses above I suggest no adjustment for salinity.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-08 23:49:11 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023


View annotation(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:6; CTD salinity data good, setting CTD salinity offset and QC
flag to bottle values.
Oxygen action ID:5; CTD oxygen data good, setting CTD oxygen offset and QC flag
to bottle values.
Posted by svheuven@gmail.com on 2015-02-19 09:22:19 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

| Filename: | Comment: | Action | |
|---|---|---|---|
| 35MF19981205_35MF20000117_tco2__Xover_DIC.png | [GLODAPv3 release: autogenerated from RC_Nico/tco2 for: 35MF20000117[1-last] |
View | |
| 35MF20000117_35MF20000719_tco2__Xover_DIC.png | [GLODAPv3 release: autogenerated from RC_Nico/tco2 for: 35MF20000117[1-last] |
View | |
| 35MF20000117_35MF20010103_tco2__Xover_DIC.png | [GLODAPv3 release: autogenerated from RC_Nico/tco2 for: 35MF20000117[1-last] |
View | |
| 35MF20000117_35MF20020104_tco2__Xover_DIC.png | [GLODAPv3 release: autogenerated from RC_Nico/tco2 for: 35MF20000117[1-last] |
View | |

View annotation(s) (filtered by tco2 in subject)
GLODAPv3 release: autogenerated tco2 update for 35MF20000117
GLODAPv3 release: tco2 update of 35MF20000117 based on tco2_offset: -888.0;
inversion: NaN; inversion_full: NaN; preadjustment: NaN; offsets_raw: NaN;
offsets_preadj: NaN; offsets_preadj_u: NaN; offsets_post: NaN; offsets_post_u:
NaN; offsets_post_rt: NaN; numberofxovers: NaN; trends_pre: NaN; trends_adj:
NaN.
Posted by nlange@geomar.de on 2026-08-04 17:12:14 UTC for data product: GLODAPv3
Autogenerated comment - tCO2
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2 Adjustment IND and PAC_SvH_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20000117 - tco2
OISO4: two deep profiles (at 30°S and 56°S).
Note: these 2 stations are treated as different cross overs in the analysis
below.
INTERNAL OISO CONSISTENCY:
11 cross overs were analyzed. The average of all cross overs is +1.6 (+/-3.5)
umol/kg.
8 cross overs show no significant differences (<4 umol/kg) and involve cruises
that are thought to have no offset in TCO2. When the offsets suggested for the
other cruises are taken into account the average of all cross overs is +0.5
(+/-1.6) umol/kg. This suggests that no adjustment would be required.
OTHER CROSS OVERS:
The cross overs with cruises INDIGO1 (30°S) and INDIGO3 (56°S) show offsets of
-9.7 (+/-5.5) umol/kg and -4.4 (+/-3.9) umol/kg, respectively. But since the
cruises INDIGO1 and INDIGO3 are known to have high TCO2 values by about 10
umol/kg and 6 umol/kg, respectively (according to this study and GLODAP), the
differences translate into no significant offsets. This supports no adjustment.
CONCLUSION:
Based on the regional analyses above I suggest no adjustment for TCO2.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-08 23:49:31 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023


View annotation(s) (filtered by alkalinity in subject)
GLODAPv3 release: autogenerated alkalinity update for 35MF20000117
GLODAPv3 release: alkalinity update of 35MF20000117 based on alkalinity_offset:
-999.0; inversion: NaN; inversion_full: NaN; preadjustment: NaN; offsets_raw:
NaN; offsets_preadj: NaN; offsets_preadj_u: NaN; offsets_post: NaN;
offsets_post_u: NaN; offsets_post_rt: NaN; numberofxovers: NaN; trends_pre: NaN;
trends_adj: NaN.
Posted by nlange@geomar.de on 2026-08-04 13:46:27 UTC for data product: GLODAPv3
Autogenerated comment - alkalinity
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2 Adjustment IND and PAC_SvH_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

| Filename: | Comment: | Action | |
|---|---|---|---|
| 35MF19981205_35MF20000117_nitrate__Xover_NO3.png | [GLODAPv3 release: autogenerated from RC_Nico/nitrate for: 35MF20000117[1-last] |
View | |
| 35MF20000117_35MF20000719_nitrate__Xover_NO3.png | [GLODAPv3 release: autogenerated from RC_Nico/nitrate for: 35MF20000117[1-last] |
View | |
| 35MF20000117_35MF20010103_nitrate__Xover_NO3.png | [GLODAPv3 release: autogenerated from RC_Nico/nitrate for: 35MF20000117[1-last] |
View | |
| 35MF20000117_35MF20020104_nitrate__Xover_NO3.png | [GLODAPv3 release: autogenerated from RC_Nico/nitrate for: 35MF20000117[1-last] |
View | |

View annotation(s) (filtered by nitrate in subject)
GLODAPv3 release: converted value for nitrate_offset from percent to factor for 35MF20000117[1-last]
GLODAPv3 release: CORRIGENDUM - converted value for nitrate_offset from percent
to factor: -888.0.
Posted by nlange@geomar.de on 2026-08-05 16:37:19 UTC for data product: GLODAPv3
GLODAPv3 release: autogenerated nitrate update for 35MF20000117
GLODAPv3 release: nitrate update of 35MF20000117 based on nitrate_offset:
-888.0; inversion: NaN; inversion_full: NaN; preadjustment: NaN; offsets_raw:
NaN; offsets_preadj: NaN; offsets_preadj_u: NaN; offsets_post: NaN;
offsets_post_u: NaN; offsets_post_rt: NaN; numberofxovers: NaN; trends_pre: NaN;
trends_adj: NaN.
Posted by nlange@geomar.de on 2026-08-04 17:11:03 UTC for data product: GLODAPv3
Autogenerated comment - nitrate
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2 Adjustment IND and PAC_SvH_20140611.xlsx): : Maintain. My figures are
not very clear about this one. Clair's suggestion of 0.97 is fair, I'd say.
Maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20000117 - nitrate
OISO4: two deep profiles (at 30°S and 56°S).
Note: these 2 stations are treated as different cross overs in the analysis
below.
INTERNAL OISO CONSISTENCY:
11 cross overs were analyzed. The average of all cross overs is 1.023 (+/-0.50).
All cross overs but 1 show significant differences (>2%). When the suggested
offsets are taken into account as well as the suggested natural variability at
56°S, the average of all cross overs is 1.028 (+/-0.008). Note that cross overs
found at 30°S show a slightly larger average (1.032 +/-0.007) than those found
at 56°S (1.025 +/-0.008). This suggests that an adjustment of 0.97 could be
required.
OTHER CROSS OVERS:
The cross over with the cruise INDIGO1 (30°S) shows a ratio of 1.047 (+/-0.013)
and since INDIGO1 is thought to have no offset in nitrate, this supports the
result of the analysis above.
The cross over with the cruise INDIGO3 (56°S) shows a ratio of 1.062 (+/-0.016),
but INDIGO3 is thought to have low nitrate values. When the suggested offset is
taken into account as well as the suggested natural variability, a good
agreement is found with the analysis above (1.026).
CONCLUSION:
Based on the regional analyses above I suggest an adjustment of 0.97 for
nitrate.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-21 13:15:34 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023


View annotation(s) (filtered by phosphate in subject)
GLODAPv3 release: converted value for phosphate_offset from percent to factor for 35MF20000117[1-last]
GLODAPv3 release: CORRIGENDUM - converted value for phosphate_offset from
percent to factor: -999.0.
Posted by nlange@geomar.de on 2026-08-05 16:37:44 UTC for data product: GLODAPv3
GLODAPv3 release: autogenerated phosphate update for 35MF20000117
GLODAPv3 release: phosphate update of 35MF20000117 based on phosphate_offset:
-999.0; inversion: NaN; inversion_full: NaN; preadjustment: NaN; offsets_raw:
NaN; offsets_preadj: NaN; offsets_preadj_u: NaN; offsets_post: NaN;
offsets_post_u: NaN; offsets_post_rt: NaN; numberofxovers: NaN; trends_pre: NaN;
trends_adj: NaN.
Posted by nlange@geomar.de on 2026-08-04 17:11:29 UTC for data product: GLODAPv3
Autogenerated comment - phosphate
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2 Adjustment IND and PAC_SvH_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023


View annotation(s) (filtered by silicate in subject)
GLODAPv3 release: converted value for silicate_offset from percent to factor for 35MF20000117[1-last]
GLODAPv3 release: CORRIGENDUM - converted value for silicate_offset from percent
to factor: -888.0.
Posted by nlange@geomar.de on 2026-08-05 16:37:58 UTC for data product: GLODAPv3
GLODAPv3 release: autogenerated silicate update for 35MF20000117[1-last]
GLODAPv3 release: CORRIGENDUM - silicate update of 35MF20000117[1-last] based on
silicate_offset: -888.0; inversion: NaN; inversion_full: NaN; preadjustment:
NaN; offsets_raw: NaN; offsets_preadj: NaN; offsets_preadj_u: NaN; offsets_post:
NaN; offsets_post_u: NaN; offsets_post_rt: NaN; numberofxovers: NaN; trends_pre:
NaN; trends_adj: NaN.
Posted by nlange@geomar.de on 2026-08-05 14:17:27 UTC for data product: GLODAPv3
Autogenerated comment - silicate
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2 Adjustment IND and PAC_SvH_20140611.xlsx): : maintain. I cannot solve
these 35MF cruises for Silicate, and by this stage will happily just accept
anything Clair suggested for them.
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20000117 - silicate
OISO4: two deep profiles (at 30°S and 56°S).
Note: these 2 stations are treated as different cross overs in the analysis
below.
INTERNAL OISO CONSISTENCY:
11 cross overs were analyzed. The average of all cross overs is 0.980
(+/-0.055).
Only one cross overs found at 30°S show no significant differences (<2%) but it
involves a cruise that is thought to have slightly high silicate. When the
suggested offsets are taken into account the average of the 5 cross overs found
at 30°S is 1.012 (+/-0.002). This suggests that no adjustment would be required.
At 56°S, however, 1 reliable cross over which involves a cruise that is thought
to have no offset in silicate suggests an offset of 1.065 (+/-0.023). When the
offsets suggested for the other cruises as well as the suggested natural
variability are taken into account the average of the 6 cross overs found at
56°S is 0.942 (+/-0.004). This suggests that an adjustment of 1.06 would be
required, but it is not warranted since Antarctic deep waters are entitled to
natural variability which could play a role in the differences observed at 56°S.
OTHER CROSS OVERS:
The cross over with the cruise INDIGO1 (30°S) shows a ratio of 1.038 (+/-0.038),
which is in relatively good agreement with the analysis above (given that
INDIGO1 is thought to have slightly low silicate).
The cross over with the cruise INDIGO3 (56°S) shows a ratio of 0.878 (+/-0.024),
but INDIGO3 is thought to have high silicate values. When the suggested offset
is taken into account as well as the suggested natural variability, a good
agreement is found with the OISO analysis above (0.944).
CONCLUSION:
The different results obtained at 30°S and 56°S are probably due to natural
changes that would have operate in Antarctic deep waters as suggested by the
analysis of other parameters including salinity.
Based on this I suggest no adjustment for silicate.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-21 13:17:34 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

| Filename: | Comment: | Action | |
|---|---|---|---|
| 35MF19981205_35MF20000117_oxygen__Xover_O2.png | [GLODAPv3 release: autogenerated from RC_Nico/oxygen for: 35MF20000117[1-last] |
View | |
| 35MF20000117_35MF20000719_oxygen__Xover_O2.png | [GLODAPv3 release: autogenerated from RC_Nico/oxygen for: 35MF20000117[1-last] |
View | |
| 35MF20000117_35MF20010103_oxygen__Xover_O2.png | [GLODAPv3 release: autogenerated from RC_Nico/oxygen for: 35MF20000117[1-last] |
View | |
| 35MF20000117_35MF20020104_oxygen__Xover_O2.png | [GLODAPv3 release: autogenerated from RC_Nico/oxygen for: 35MF20000117[1-last] |
View | |

View annotation(s) (filtered by oxygen in subject)
GLODAPv3 release: converted value for oxygen_offset from percent to factor for 35MF20000117[1-last]
GLODAPv3 release: CORRIGENDUM - converted value for oxygen_offset from percent
to factor: 1.07.
Posted by nlange@geomar.de on 2026-08-05 16:37:32 UTC for data product: GLODAPv3
GLODAPv3 release: autogenerated oxygen update for 35MF20000117
GLODAPv3 release: oxygen update of 35MF20000117 based on oxygen_offset: 7.0;
inversion: NaN; inversion_full: NaN; preadjustment: NaN; offsets_raw: NaN;
offsets_preadj: NaN; offsets_preadj_u: NaN; offsets_post: NaN; offsets_post_u:
NaN; offsets_post_rt: NaN; numberofxovers: NaN; trends_pre: NaN; trends_adj:
NaN.
Posted by nlange@geomar.de on 2026-08-04 17:11:16 UTC for data product: GLODAPv3
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:6; CTD salinity data good, setting CTD salinity offset and QC
flag to bottle values.
Oxygen action ID:5; CTD oxygen data good, setting CTD oxygen offset and QC flag
to bottle values.
Posted by svheuven@gmail.com on 2015-02-19 09:22:19 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20000117/oxygen: update slope+intercept
autogenerated: BOToxy is compatible with unchanged CTDoxy
Posted by svheuven@gmail.com on 2014-12-18 16:52:44 UTC for data product: CARINA, 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_20140611.xlsx): : make 1.07, which is the
approx. the mean of the offsets, and also the inv.sugg
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20000117/oxygen: init slope+intercept
autogenerated: using BOToxy because bad fit of CTDoxy.
Posted by svheuven@gmail.com on 2014-02-25 17:02:15 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20000117 - oxygen
OISO4: only one deep profiles (at 56°S).
INTERNAL OISO CONSISTENCY:
6 cross overs were analyzed. The average of all cross overs is 0.937 (+/-0.008).
All cross overs show significant differences ranging from 0.93 to 0.95 and 4 of
them involve cruises that are thought to have no offset in oxygen. When the
offsets suggested for the other cruises are taken into account the average of
all cross overs is 0.937 (+/-0.003). This suggests that an adjustment of 1.06
could be required.
OTHER CROSS OVERS:
The cross over with the cruise INDIGO3 shows a ratio of 0.944 (+/-0.006), which
supports the analysis above.
CONCLUSION:
Based on the regional analyses above I suggest an adjustment of 1.06 for oxygen.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-21 13:18:01 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023


View annotation(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:6; CTD salinity data good, setting CTD salinity offset and QC
flag to bottle values.
Oxygen action ID:5; CTD oxygen data good, setting CTD oxygen offset and QC flag
to bottle values.
Posted by svheuven@gmail.com on 2015-02-19 09:22:19 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023


View annotation(s) (filtered by temperature in subject)
GLODAPv3 release: temperature added as NEW adjustment parameter to 35MF20000117[1-last]
Automated addition of temperature as NEW parameter to 35MF20000117[1-last] based
on temperature_offset: -888.
Posted by nlange@geomar.de on 2026-08-05 14:17:14 UTC for data product: GLODAPv3












View 37 annotation(s) (Lists all annotations)
GLODAPv3 release: converted value for silicate_offset from percent to factor for 35MF20000117[1-last]
GLODAPv3 release: CORRIGENDUM - converted value for silicate_offset from percent
to factor: -888.0.
Posted by nlange@geomar.de on 2026-08-05 16:37:58 UTC for data product: GLODAPv3
GLODAPv3 release: converted value for phosphate_offset from percent to factor for 35MF20000117[1-last]
GLODAPv3 release: CORRIGENDUM - converted value for phosphate_offset from
percent to factor: -999.0.
Posted by nlange@geomar.de on 2026-08-05 16:37:44 UTC for data product: GLODAPv3
GLODAPv3 release: converted value for oxygen_offset from percent to factor for 35MF20000117[1-last]
GLODAPv3 release: CORRIGENDUM - converted value for oxygen_offset from percent
to factor: 1.07.
Posted by nlange@geomar.de on 2026-08-05 16:37:32 UTC for data product: GLODAPv3
GLODAPv3 release: converted value for nitrate_offset from percent to factor for 35MF20000117[1-last]
GLODAPv3 release: CORRIGENDUM - converted value for nitrate_offset from percent
to factor: -888.0.
Posted by nlange@geomar.de on 2026-08-05 16:37:19 UTC for data product: GLODAPv3
GLODAPv3 release: autogenerated silicate update for 35MF20000117[1-last]
GLODAPv3 release: CORRIGENDUM - silicate update of 35MF20000117[1-last] based on
silicate_offset: -888.0; inversion: NaN; inversion_full: NaN; preadjustment:
NaN; offsets_raw: NaN; offsets_preadj: NaN; offsets_preadj_u: NaN; offsets_post:
NaN; offsets_post_u: NaN; offsets_post_rt: NaN; numberofxovers: NaN; trends_pre:
NaN; trends_adj: NaN.
Posted by nlange@geomar.de on 2026-08-05 14:17:27 UTC for data product: GLODAPv3
35MF20000117[1-last] GLODAPv3 release
GLODAPv3 release: silicate autogenerated adjustment parameter update for
35MF20000117 - select parameter to view annotation with specific details.
Posted by nlange@geomar.de on 2026-08-05 14:17:27 UTC for data product: GLODAPv3
GLODAPv3 release: temperature added as NEW adjustment parameter to 35MF20000117[1-last]
Automated addition of temperature as NEW parameter to 35MF20000117[1-last] based
on temperature_offset: -888.
Posted by nlange@geomar.de on 2026-08-05 14:17:14 UTC for data product: GLODAPv3
35MF20000117[1-last] GLODAPv3 release
Automated addition of temperature as NEW adjustment parameter in GLODAPv3 to
35MF20000117[1-last] - select parameter to view annotation with specific
details.
Posted by nlange@geomar.de on 2026-08-05 14:17:14 UTC for data product: GLODAPv3
GLODAPv3 release: autogenerated tco2 update for 35MF20000117
GLODAPv3 release: tco2 update of 35MF20000117 based on tco2_offset: -888.0;
inversion: NaN; inversion_full: NaN; preadjustment: NaN; offsets_raw: NaN;
offsets_preadj: NaN; offsets_preadj_u: NaN; offsets_post: NaN; offsets_post_u:
NaN; offsets_post_rt: NaN; numberofxovers: NaN; trends_pre: NaN; trends_adj:
NaN.
Posted by nlange@geomar.de on 2026-08-04 17:12:14 UTC for data product: GLODAPv3
35MF20000117 GLODAPv3 release
GLODAPv3 release: tco2 autogenerated adjustment parameter update for
35MF20000117 - select parameter to view annotation with specific details.
Posted by nlange@geomar.de on 2026-08-04 17:12:14 UTC for data product: GLODAPv3
GLODAPv3 release: autogenerated salinity update for 35MF20000117
GLODAPv3 release: salinity update of 35MF20000117 based on salinity_offset:
-888.0000; inversion: NaN; inversion_full: NaN; preadjustment: NaN; offsets_raw:
NaN; offsets_preadj: NaN; offsets_preadj_u: NaN; offsets_post: NaN;
offsets_post_u: NaN; offsets_post_rt: NaN; numberofxovers: NaN; trends_pre: NaN;
trends_adj: NaN.
Posted by nlange@geomar.de on 2026-08-04 17:11:43 UTC for data product: GLODAPv3
35MF20000117 GLODAPv3 release
GLODAPv3 release: salinity autogenerated adjustment parameter update for
35MF20000117 - select parameter to view annotation with specific details.
Posted by nlange@geomar.de on 2026-08-04 17:11:43 UTC for data product: GLODAPv3
GLODAPv3 release: autogenerated phosphate update for 35MF20000117
GLODAPv3 release: phosphate update of 35MF20000117 based on phosphate_offset:
-999.0; inversion: NaN; inversion_full: NaN; preadjustment: NaN; offsets_raw:
NaN; offsets_preadj: NaN; offsets_preadj_u: NaN; offsets_post: NaN;
offsets_post_u: NaN; offsets_post_rt: NaN; numberofxovers: NaN; trends_pre: NaN;
trends_adj: NaN.
Posted by nlange@geomar.de on 2026-08-04 17:11:29 UTC for data product: GLODAPv3
35MF20000117 GLODAPv3 release
GLODAPv3 release: phosphate autogenerated adjustment parameter update for
35MF20000117 - select parameter to view annotation with specific details.
Posted by nlange@geomar.de on 2026-08-04 17:11:29 UTC for data product: GLODAPv3
GLODAPv3 release: autogenerated oxygen update for 35MF20000117
GLODAPv3 release: oxygen update of 35MF20000117 based on oxygen_offset: 7.0;
inversion: NaN; inversion_full: NaN; preadjustment: NaN; offsets_raw: NaN;
offsets_preadj: NaN; offsets_preadj_u: NaN; offsets_post: NaN; offsets_post_u:
NaN; offsets_post_rt: NaN; numberofxovers: NaN; trends_pre: NaN; trends_adj:
NaN.
Posted by nlange@geomar.de on 2026-08-04 17:11:16 UTC for data product: GLODAPv3
35MF20000117 GLODAPv3 release
GLODAPv3 release: oxygen autogenerated adjustment parameter update for
35MF20000117 - select parameter to view annotation with specific details.
Posted by nlange@geomar.de on 2026-08-04 17:11:16 UTC for data product: GLODAPv3
GLODAPv3 release: autogenerated nitrate update for 35MF20000117
GLODAPv3 release: nitrate update of 35MF20000117 based on nitrate_offset:
-888.0; inversion: NaN; inversion_full: NaN; preadjustment: NaN; offsets_raw:
NaN; offsets_preadj: NaN; offsets_preadj_u: NaN; offsets_post: NaN;
offsets_post_u: NaN; offsets_post_rt: NaN; numberofxovers: NaN; trends_pre: NaN;
trends_adj: NaN.
Posted by nlange@geomar.de on 2026-08-04 17:11:03 UTC for data product: GLODAPv3
35MF20000117 GLODAPv3 release
GLODAPv3 release: nitrate autogenerated adjustment parameter update for
35MF20000117 - select parameter to view annotation with specific details.
Posted by nlange@geomar.de on 2026-08-04 17:11:03 UTC for data product: GLODAPv3
GLODAPv3 release: autogenerated alkalinity update for 35MF20000117
GLODAPv3 release: alkalinity update of 35MF20000117 based on alkalinity_offset:
-999.0; inversion: NaN; inversion_full: NaN; preadjustment: NaN; offsets_raw:
NaN; offsets_preadj: NaN; offsets_preadj_u: NaN; offsets_post: NaN;
offsets_post_u: NaN; offsets_post_rt: NaN; numberofxovers: NaN; trends_pre: NaN;
trends_adj: NaN.
Posted by nlange@geomar.de on 2026-08-04 13:46:27 UTC for data product: GLODAPv3
35MF20000117 GLODAPv3 release
GLODAPv3 release: alkalinity autogenerated adjustment parameter update for
35MF20000117 - select parameter to view annotation with specific details.
Posted by nlange@geomar.de on 2026-08-04 13:46:27 UTC for data product: GLODAPv3
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:6; CTD salinity data good, setting CTD salinity offset and QC
flag to bottle values.
Oxygen action ID:5; CTD oxygen data good, setting CTD oxygen offset and QC flag
to bottle values.
Posted by svheuven@gmail.com on 2015-02-19 09:22:19 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20000117/oxygen: update slope+intercept
autogenerated: BOToxy is compatible with unchanged CTDoxy
Posted by svheuven@gmail.com on 2014-12-18 16:52:44 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20000117/salinity: update slope+intercept
autogenerated: BOTsal is compatible with CALIBRATED CTDsal
Posted by svheuven@gmail.com on 2014-12-18 16:52:44 UTC for data product: CARINA, 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_20140611.xlsx): : make 1.07, which is the
approx. the mean of the offsets, and also the inv.sugg
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, 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_20140611.xlsx): : maintain. I cannot solve
these 35MF cruises for Silicate, and by this stage will happily just accept
anything Clair suggested for them.
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, 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_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, 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_20140611.xlsx): : Maintain. My figures are
not very clear about this one. Clair's suggestion of 0.97 is fair, I'd say.
Maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, 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_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, 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_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, 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_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20000117/oxygen: init slope+intercept
autogenerated: using BOToxy because bad fit of CTDoxy.
Posted by svheuven@gmail.com on 2014-02-25 17:02:15 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20000117/salinity: init slope+intercept
autogenerated: using mean of BOTsal and UNCHANGED CTDsal
Posted by svheuven@gmail.com on 2014-02-25 17:02:15 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20000117 - oxygen
OISO4: only one deep profiles (at 56°S).
INTERNAL OISO CONSISTENCY:
6 cross overs were analyzed. The average of all cross overs is 0.937 (+/-0.008).
All cross overs show significant differences ranging from 0.93 to 0.95 and 4 of
them involve cruises that are thought to have no offset in oxygen. When the
offsets suggested for the other cruises are taken into account the average of
all cross overs is 0.937 (+/-0.003). This suggests that an adjustment of 1.06
could be required.
OTHER CROSS OVERS:
The cross over with the cruise INDIGO3 shows a ratio of 0.944 (+/-0.006), which
supports the analysis above.
CONCLUSION:
Based on the regional analyses above I suggest an adjustment of 1.06 for oxygen.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-21 13:18:01 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20000117 - silicate
OISO4: two deep profiles (at 30°S and 56°S).
Note: these 2 stations are treated as different cross overs in the analysis
below.
INTERNAL OISO CONSISTENCY:
11 cross overs were analyzed. The average of all cross overs is 0.980
(+/-0.055).
Only one cross overs found at 30°S show no significant differences (<2%) but it
involves a cruise that is thought to have slightly high silicate. When the
suggested offsets are taken into account the average of the 5 cross overs found
at 30°S is 1.012 (+/-0.002). This suggests that no adjustment would be required.
At 56°S, however, 1 reliable cross over which involves a cruise that is thought
to have no offset in silicate suggests an offset of 1.065 (+/-0.023). When the
offsets suggested for the other cruises as well as the suggested natural
variability are taken into account the average of the 6 cross overs found at
56°S is 0.942 (+/-0.004). This suggests that an adjustment of 1.06 would be
required, but it is not warranted since Antarctic deep waters are entitled to
natural variability which could play a role in the differences observed at 56°S.
OTHER CROSS OVERS:
The cross over with the cruise INDIGO1 (30°S) shows a ratio of 1.038 (+/-0.038),
which is in relatively good agreement with the analysis above (given that
INDIGO1 is thought to have slightly low silicate).
The cross over with the cruise INDIGO3 (56°S) shows a ratio of 0.878 (+/-0.024),
but INDIGO3 is thought to have high silicate values. When the suggested offset
is taken into account as well as the suggested natural variability, a good
agreement is found with the OISO analysis above (0.944).
CONCLUSION:
The different results obtained at 30°S and 56°S are probably due to natural
changes that would have operate in Antarctic deep waters as suggested by the
analysis of other parameters including salinity.
Based on this I suggest no adjustment for silicate.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-21 13:17:34 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20000117 - nitrate
OISO4: two deep profiles (at 30°S and 56°S).
Note: these 2 stations are treated as different cross overs in the analysis
below.
INTERNAL OISO CONSISTENCY:
11 cross overs were analyzed. The average of all cross overs is 1.023 (+/-0.50).
All cross overs but 1 show significant differences (>2%). When the suggested
offsets are taken into account as well as the suggested natural variability at
56°S, the average of all cross overs is 1.028 (+/-0.008). Note that cross overs
found at 30°S show a slightly larger average (1.032 +/-0.007) than those found
at 56°S (1.025 +/-0.008). This suggests that an adjustment of 0.97 could be
required.
OTHER CROSS OVERS:
The cross over with the cruise INDIGO1 (30°S) shows a ratio of 1.047 (+/-0.013)
and since INDIGO1 is thought to have no offset in nitrate, this supports the
result of the analysis above.
The cross over with the cruise INDIGO3 (56°S) shows a ratio of 1.062 (+/-0.016),
but INDIGO3 is thought to have low nitrate values. When the suggested offset is
taken into account as well as the suggested natural variability, a good
agreement is found with the analysis above (1.026).
CONCLUSION:
Based on the regional analyses above I suggest an adjustment of 0.97 for
nitrate.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-21 13:15:34 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20000117 - tco2
OISO4: two deep profiles (at 30°S and 56°S).
Note: these 2 stations are treated as different cross overs in the analysis
below.
INTERNAL OISO CONSISTENCY:
11 cross overs were analyzed. The average of all cross overs is +1.6 (+/-3.5)
umol/kg.
8 cross overs show no significant differences (<4 umol/kg) and involve cruises
that are thought to have no offset in TCO2. When the offsets suggested for the
other cruises are taken into account the average of all cross overs is +0.5
(+/-1.6) umol/kg. This suggests that no adjustment would be required.
OTHER CROSS OVERS:
The cross overs with cruises INDIGO1 (30°S) and INDIGO3 (56°S) show offsets of
-9.7 (+/-5.5) umol/kg and -4.4 (+/-3.9) umol/kg, respectively. But since the
cruises INDIGO1 and INDIGO3 are known to have high TCO2 values by about 10
umol/kg and 6 umol/kg, respectively (according to this study and GLODAP), the
differences translate into no significant offsets. This supports no adjustment.
CONCLUSION:
Based on the regional analyses above I suggest no adjustment for TCO2.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-08 23:49:31 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20000117 - salinity
OISO4: two deep profiles (at 30°S and 56°S).
Note: these 2 stations are treated as different cross overs in the analysis
below.
INTERNAL OISO CONSISTENCY:
11 cross overs were analyzed. The average of all cross overs is -4.0 (+/-9.2)
ppm.
7 cross overs show no significant differences (<5 ppm) and involve cruises that
are thought to have no significant offset in salinity. When the offsets
suggested for the other cruises are taken into account the average of all cross
overs is -0.9 (+/-1.9) ppm. This suggests that no adjustment would be required.
OTHER CROSS OVERS:
The cross overs with cruises INDIGO1 (30°S) and INDIGO3 (56°S) show offsets of
-3 (+/-9) ppm and -4 (+/-2) ppm, respectively, which supports no adjustment.
CONCLUSION:
Based on the regional analyses above I suggest no adjustment for salinity.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-08 23:49:11 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Hide annotations