Cruise: 35MF20050111 (dataset:GLODAPv2.NEW) Data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Synonyms (including errata!) for this cruise: OISO12; 35MF20050111; OISO12; PU name: oiso12
IMPORTANT information for GLODAP Reference Group Editors: This adjustment is a published version for GLODAPv2!
Please wait while loading list of related files
- no files! -
Plot/Data files re. Parameter(s) (select parameter on left side to view!):
alkalinity:1
ctd_oxygen:1
ctd_salinity:3
nitrate:3
oxygen:1
phosphate:1
salinity:2
silicate:2
tco2:1
- no files! -
Filename: | Comment: | Action | |
---|---|---|---|
Xover_1.png | [autogenerated from RC_Siv/salinity!] |
View | |
Xresults.png | [autogenerated from RC_Siv/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: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: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - salinity
Automated update setting data quality flag from BAD to GOOD in order to retain
these non-QCed data in final product. SvH/GLODAPv2 / 2015-01-19)
Posted by svheuven@gmail.com on 2015-01-20 14:46:42 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20050111/salinity: update slope+intercept
autogenerated: BOTsal is compatible with CALIBRATED CTDsal
Posted by svheuven@gmail.com on 2014-12-18 16:52:45 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20050111 - salinity
Manually set CTDsal calibration for this cruise, to avoid CTDsal data being
lost.
Posted by svheuven@gmail.com on 2014-12-15 21:14:04 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_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20050111/salinity: init slope+intercept
autogenerated: using BOTsal because bad fit of CTDsal
Posted by svheuven@gmail.com on 2014-02-25 17:02:15 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Filename: | Comment: | Action | |
---|---|---|---|
Xover_1.png | [autogenerated from RC_Siv/ctd_salinity!] |
View | |
Xover_2.png | [autogenerated from RC_Siv/ctd_salinity!] |
View | |
Xresults.png | [autogenerated from RC_Siv/ctd_salinity!] |
View |
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: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: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Filename: | Comment: | Action | |
---|---|---|---|
Xresults.png | [autogenerated from RC_Siv/tco2!] |
View |
View comment(s) (filtered by tco2 in subject)
Autogenerated comment - tco2
Automated update setting data quality flag from BAD to GOOD in order to retain
these non-QCed data in final product. SvH/GLODAPv2 / 2015-01-19)
Posted by svheuven@gmail.com on 2015-01-20 14:46:42 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_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Filename: | Comment: | Action | |
---|---|---|---|
Xresults.png | [autogenerated from RC_Siv/alkalinity!] |
View |
View comment(s) (filtered by alkalinity in subject)
Autogenerated comment - alkalinity
Automated update setting data quality flag from BAD to GOOD in order to retain
these non-QCed data in final product. SvH/GLODAPv2 / 2015-01-19)
Posted by svheuven@gmail.com on 2015-01-20 14:46:42 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_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 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_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20050111 - phosphate
Flag bad following Bob's analysis, Bob's comment:
Final large scale data exploration results looking for "major" problems.
Procedure used:
Southern Ocean sector of the Indian Ocean (south of 35S)
Unadjusted data from Feb. 2014 compilation
Plot nitrate vs phosphate for all depths; fit with linear; segregate residuals
by cruise
Compare findings to current adjustment table
The 3 most anomalous cruises are # 47, 49 and 52. All 3 are OISO cruises and
consequently have only limited deep data.
#47 is 35MF20030123 and it has tabulated adjustments that will correct. No
further action.
#49 is 35MF20050111 has -888 for both nitrate and phosphate adjustment.
Stronglhy suggest setting flags to discard both. The scatter alone is enough to
justify this decision.
#52 is 35MF20110114 has -888 for both nitrate and phosphate adjustment.
Crossover plots shown are inconclusive, but incomplete. Recommend applying
adjustments similar to those of #47.
Posted by are.olsen@uib.no on 2014-03-18 08:02:43 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Filename: | Comment: | Action | |
---|---|---|---|
SO.Ind.Sec.No3vsPO4.pdf | Bob's analysis |
View | |
Xover_1.png | [autogenerated from RC_Siv/nitrate!] |
View | |
Xresults.png | [autogenerated from RC_Siv/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_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20050111 - nitrate
Flagged bad following Bob's analysis
Comment from Bob:
Final large scale data exploration results looking for "major" problems.
Procedure used:
Southern Ocean sector of the Indian Ocean (south of 35S)
Unadjusted data from Feb. 2014 compilation
Plot nitrate vs phosphate for all depths; fit with linear; segregate residuals
by cruise
Compare findings to current adjustment table
The 3 most anomalous cruises are # 47, 49 and 52. All 3 are OISO cruises and
consequently have only limited deep data.
#47 is 35MF20030123 and it has tabulated adjustments that will correct. No
further action.
#49 is 35MF20050111 has -888 for both nitrate and phosphate adjustment. Strongly
suggest setting flags to discard both. The scatter alone is enough to justify
this decision.
#52 is 35MF20110114 has -888 for both nitrate and phosphate adjustment.
Crossover plots shown are inconclusive, but incomplete. Recommend applying
adjustments similar to those of #47.
Posted by are.olsen@uib.no on 2014-03-18 08:01:26 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Filename: | Comment: | Action | |
---|---|---|---|
SO.Ind.Sec.No3vsPO4.pdf | Bobs analysis |
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_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20050111 - phosphate
Flag bad following Bob's analysis, Bob's comment:
Final large scale data exploration results looking for "major" problems.
Procedure used:
Southern Ocean sector of the Indian Ocean (south of 35S)
Unadjusted data from Feb. 2014 compilation
Plot nitrate vs phosphate for all depths; fit with linear; segregate residuals
by cruise
Compare findings to current adjustment table
The 3 most anomalous cruises are # 47, 49 and 52. All 3 are OISO cruises and
consequently have only limited deep data.
#47 is 35MF20030123 and it has tabulated adjustments that will correct. No
further action.
#49 is 35MF20050111 has -888 for both nitrate and phosphate adjustment.
Stronglhy suggest setting flags to discard both. The scatter alone is enough to
justify this decision.
#52 is 35MF20110114 has -888 for both nitrate and phosphate adjustment.
Crossover plots shown are inconclusive, but incomplete. Recommend applying
adjustments similar to those of #47.
Posted by are.olsen@uib.no on 2014-03-18 08:02:43 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Filename: | Comment: | Action | |
---|---|---|---|
Xover_1.png | [autogenerated from RC_Siv/silicate!] |
View | |
Xresults.png | [autogenerated from RC_Siv/silicate!] |
View |
View comment(s) (filtered by silicate in subject)
Autogenerated comment - silicate
Automated update setting data quality flag from BAD to GOOD in order to retain
these non-QCed data in final product. SvH/GLODAPv2 / 2015-01-19)
Posted by svheuven@gmail.com on 2015-01-20 14:46:42 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_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: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Filename: | Comment: | Action | |
---|---|---|---|
Xresults.png | [autogenerated from RC_Siv/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: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: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - oxygen
Automated update setting data quality flag from BAD to GOOD in order to retain
these non-QCed data in final product. SvH/GLODAPv2 / 2015-01-19)
Posted by svheuven@gmail.com on 2015-01-20 14:46:42 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20050111/oxygen: update slope+intercept
autogenerated: BOToxy is compatible with unchanged CTDoxy
Posted by svheuven@gmail.com on 2014-12-18 16:52:45 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_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20050111/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: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20050111 - ctd_oxygen
There is no ctdoxy on this cruise
Posted by siv.lauvset@uib.no on 2013-04-15 07:44:26 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Filename: | Comment: | Action | |
---|---|---|---|
Xresults.png | [autogenerated from RC_Siv/ctd_oxygen!] |
View |
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: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: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20050111 - ctd_oxygen
There is no ctdoxy on this cruise
Posted by siv.lauvset@uib.no on 2013-04-15 07:44:26 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View 22 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: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: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - oxygen
Automated update setting data quality flag from BAD to GOOD in order to retain
these non-QCed data in final product. SvH/GLODAPv2 / 2015-01-19)
Posted by svheuven@gmail.com on 2015-01-20 14:46:42 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - silicate
Automated update setting data quality flag from BAD to GOOD in order to retain
these non-QCed data in final product. SvH/GLODAPv2 / 2015-01-19)
Posted by svheuven@gmail.com on 2015-01-20 14:46:42 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - alkalinity
Automated update setting data quality flag from BAD to GOOD in order to retain
these non-QCed data in final product. SvH/GLODAPv2 / 2015-01-19)
Posted by svheuven@gmail.com on 2015-01-20 14:46:42 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - tco2
Automated update setting data quality flag from BAD to GOOD in order to retain
these non-QCed data in final product. SvH/GLODAPv2 / 2015-01-19)
Posted by svheuven@gmail.com on 2015-01-20 14:46:42 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - salinity
Automated update setting data quality flag from BAD to GOOD in order to retain
these non-QCed data in final product. SvH/GLODAPv2 / 2015-01-19)
Posted by svheuven@gmail.com on 2015-01-20 14:46:42 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20050111/oxygen: update slope+intercept
autogenerated: BOToxy is compatible with unchanged CTDoxy
Posted by svheuven@gmail.com on 2014-12-18 16:52:45 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20050111/salinity: update slope+intercept
autogenerated: BOTsal is compatible with CALIBRATED CTDsal
Posted by svheuven@gmail.com on 2014-12-18 16:52:45 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20050111 - salinity
Manually set CTDsal calibration for this cruise, to avoid CTDsal data being
lost.
Posted by svheuven@gmail.com on 2014-12-15 21:14:04 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_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 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_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: 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: 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
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 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_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 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_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 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_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20050111 - phosphate
Flag bad following Bob's analysis, Bob's comment:
Final large scale data exploration results looking for "major" problems.
Procedure used:
Southern Ocean sector of the Indian Ocean (south of 35S)
Unadjusted data from Feb. 2014 compilation
Plot nitrate vs phosphate for all depths; fit with linear; segregate residuals
by cruise
Compare findings to current adjustment table
The 3 most anomalous cruises are # 47, 49 and 52. All 3 are OISO cruises and
consequently have only limited deep data.
#47 is 35MF20030123 and it has tabulated adjustments that will correct. No
further action.
#49 is 35MF20050111 has -888 for both nitrate and phosphate adjustment.
Stronglhy suggest setting flags to discard both. The scatter alone is enough to
justify this decision.
#52 is 35MF20110114 has -888 for both nitrate and phosphate adjustment.
Crossover plots shown are inconclusive, but incomplete. Recommend applying
adjustments similar to those of #47.
Posted by are.olsen@uib.no on 2014-03-18 08:02:43 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20050111 - nitrate
Flagged bad following Bob's analysis
Comment from Bob:
Final large scale data exploration results looking for "major" problems.
Procedure used:
Southern Ocean sector of the Indian Ocean (south of 35S)
Unadjusted data from Feb. 2014 compilation
Plot nitrate vs phosphate for all depths; fit with linear; segregate residuals
by cruise
Compare findings to current adjustment table
The 3 most anomalous cruises are # 47, 49 and 52. All 3 are OISO cruises and
consequently have only limited deep data.
#47 is 35MF20030123 and it has tabulated adjustments that will correct. No
further action.
#49 is 35MF20050111 has -888 for both nitrate and phosphate adjustment. Strongly
suggest setting flags to discard both. The scatter alone is enough to justify
this decision.
#52 is 35MF20110114 has -888 for both nitrate and phosphate adjustment.
Crossover plots shown are inconclusive, but incomplete. Recommend applying
adjustments similar to those of #47.
Posted by are.olsen@uib.no on 2014-03-18 08:01:26 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20050111/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: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20050111/salinity: init slope+intercept
autogenerated: using BOTsal because bad fit of CTDsal
Posted by svheuven@gmail.com on 2014-02-25 17:02:15 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20050111 - ctd_oxygen
There is no ctdoxy on this cruise
Posted by siv.lauvset@uib.no on 2013-04-15 07:44:26 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF20050111 - general
There are no xovers for this cruise
Posted by siv.lauvset@uib.no on 2013-03-21 15:51:02 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Hide comments