Cruise: 49XK19940216 (dataset:GLODAPv2.NEW) Data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Synonyms (including errata!) for this cruise: pr24; 49XK19940216; pr24; PU name: pr24sv;
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 | |
---|---|---|---|
49XK19940216___Xresults.png | View |
- no files! -
Plot/Data files re. Parameter(s) (select parameter on left side to view!):
cruise:1
ctd_salinity:2
nitrate:7
oxygen:5
phosphate:9
salinity:5
silicate:7
- no files! -
Filename: | Comment: | Action | |
---|---|---|---|
Xover_1.png | [autogenerated from RC_Siv/salinity!] |
View | |
Xresults.png | [autogenerated from RC_Siv/salinity!] |
View | |
unadjusted_49XK19940212_49XK19940216_SAL.pdf | [autogenerated from RC_Steven/salinity!] |
View | |
unadjusted_49XK19940216_49XK19960617_SAL.pdf | [autogenerated from RC_Steven/salinity!] |
View | |
xover_sum_49XK19940216_SAL.pdf | [autogenerated from RC_Steven/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:15 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19940216/salinity: update slope+intercept
autogenerated: only BOTsal available (no CTDsal)
Posted by svheuven@gmail.com on 2014-12-18 16:52:54 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:45 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19940216/salinity: init slope+intercept
autogenerated: using BOTsal (no CTDsal)
Posted by svheuven@gmail.com on 2014-02-25 17:02:21 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 | |
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: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:15 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
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_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:45 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
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_20140611.xlsx): : maintain.
Posted by svheuven@gmail.com on 2014-06-16 15:50:45 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): : make 1.05, which makes it
match with 32MW19890206
Posted by svheuven@gmail.com on 2014-06-16 15:50:45 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19940216 - phosphate
49XK19940212 and 49XK19940216 are very likely the same cruise, same leg but
different sections.
They only crossover with themselves and with 49XK19960617
Analysis of beta version of GLODAP in preparation of the Bremen 2014 workshop
showed that
all three nutrients were consistent for the three cruises (with the PO4
correction of 1.03 decided at in Groningen Oct 2013
for the two 1994 cruises applied).
The 1996 cruise has crossovers with several other cruises, and nutrients are
clearly too
low on this. Notably when compared with 32MW19890206, which is good.
This could be related to a units conversion issue and at the Bremen workshop we
hence decided that nutrients at these three cruises should be adjusted by 1.025
to bring them into consistency with the 32MW19890206 cruise. This brings the
adjustment for phosphate up to 1.055
Posted by are.olsen@uib.no on 2014-02-20 14:50:26 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19940216 - phosphate
At the Groningen October 2012 meeting, we agreed to change adjustment from 1 to
1.03, based on analysis of preliminary product. See two crossovers that I have
uploaded.
Posted by are.olsen@uib.no on 2014-02-18 11:46:29 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Filename: | Comment: | Action | |
---|---|---|---|
PAIR4322___CRUISE328-49XK19940212___CRUISE329-49XK19940216___NO3.pdf | Beta version xover with 49XK19940212 cruise |
View | |
PAIR4324___CRUISE329-49XK19940216___CRUISE330-49XK19960617___NO3.pdf | beta version xover with 49XK19960617 cruise |
View | |
Xover_1.png | [autogenerated from RC_Siv/nitrate!] |
View | |
Xresults.png | [autogenerated from RC_Siv/nitrate!] |
View | |
unadjusted_49XK19940212_49XK19940216_NO3.pdf | [autogenerated from RC_Steven/nitrate!] |
View | |
unadjusted_49XK19940216_49XK19960617_NO3.pdf | [autogenerated from RC_Steven/nitrate!] |
View | |
xover_sum_49XK19940216_NO3.pdf | [autogenerated from RC_Steven/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): : Make 1. The units
conversion theory from an earlier comment doesn't add up.
Posted by svheuven@gmail.com on 2014-06-16 15:50:45 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19940216 - nitrate
49XK19940212 and 49XK19940216 are very likely the same cruise, same leg but
different sections.
They only crossover with themselves and with 49XK19960617
Analysis of beta version of GLODAP in preparation of the Bremen 2014 workshop
showed that
all three nutrients were consistent for the three cruises (with the PO4
correction of 1.03 decided at in Groningen Oct 2013
for the two 1994 cruises applied).
The 1996 cruise has crossovers with several other cruises, and nutrients are
clearly too
low on this. Notably when compared with 32MW19890206, which is good.
This could be related to a units conversion issue and at the Bremen workshop we
hence decided that nutrients from all of these three cruises should be adjusted
by 1.025
to bring them into consistency with the 32MW19890206 cruise.
Posted by are.olsen@uib.no on 2014-02-20 14:48:21 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Filename: | Comment: | Action | |
---|---|---|---|
PAIR380___CRUISE35-49XK19940212___CRUISE36-49XK19940216___PO4.pdf | View | ||
PAIR383___CRUISE36-49XK19940216___CRUISE45-49XK19960617___PO4.pdf | View | ||
PAIR4322___CRUISE328-49XK19940212___CRUISE329-49XK19940216___PO4.pdf | Beta version xover with 49XK19940212 cruise |
View | |
PAIR4324___CRUISE329-49XK19940216___CRUISE330-49XK19960617___PO4.pdf | Beta version xover with 49XK19960617 cruise |
View | |
Xover_1.png | [autogenerated from RC_Siv/phosphate!] |
View | |
Xresults.png | [autogenerated from RC_Siv/phosphate!] |
View | |
unadjusted_49XK19940212_49XK19940216_PO4.pdf | [autogenerated from RC_Steven/phosphate!] |
View | |
unadjusted_49XK19940216_49XK19960617_PO4.pdf | [autogenerated from RC_Steven/phosphate!] |
View | |
xover_sum_49XK19940216_PO4.pdf | [autogenerated from RC_Steven/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_20140611.xlsx): : make 1.05, which makes it
match with 32MW19890206
Posted by svheuven@gmail.com on 2014-06-16 15:50:45 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19940216 - phosphate
49XK19940212 and 49XK19940216 are very likely the same cruise, same leg but
different sections.
They only crossover with themselves and with 49XK19960617
Analysis of beta version of GLODAP in preparation of the Bremen 2014 workshop
showed that
all three nutrients were consistent for the three cruises (with the PO4
correction of 1.03 decided at in Groningen Oct 2013
for the two 1994 cruises applied).
The 1996 cruise has crossovers with several other cruises, and nutrients are
clearly too
low on this. Notably when compared with 32MW19890206, which is good.
This could be related to a units conversion issue and at the Bremen workshop we
hence decided that nutrients at these three cruises should be adjusted by 1.025
to bring them into consistency with the 32MW19890206 cruise. This brings the
adjustment for phosphate up to 1.055
Posted by are.olsen@uib.no on 2014-02-20 14:50:26 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19940216 - phosphate
At the Groningen October 2012 meeting, we agreed to change adjustment from 1 to
1.03, based on analysis of preliminary product. See two crossovers that I have
uploaded.
Posted by are.olsen@uib.no on 2014-02-18 11:46:29 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Filename: | Comment: | Action | |
---|---|---|---|
PAIR4322___CRUISE328-49XK19940212___CRUISE329-49XK19940216___SIL.pdf | Beta version xover with 49XK19940216 cruise |
View | |
PAIR4324___CRUISE329-49XK19940216___CRUISE330-49XK19960617___SIL.pdf | Beta version xover with 49XK19960617 cruise |
View | |
Xover_1.png | [autogenerated from RC_Siv/silicate!] |
View | |
Xresults.png | [autogenerated from RC_Siv/silicate!] |
View | |
unadjusted_49XK19940212_49XK19940216_SIL.pdf | [autogenerated from RC_Steven/silicate!] |
View | |
unadjusted_49XK19940216_49XK19960617_SIL.pdf | [autogenerated from RC_Steven/silicate!] |
View | |
xover_sum_49XK19940216_SIL.pdf | [autogenerated from RC_Steven/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_20140611.xlsx): : make 1. After
pre-adjustments (JPN+1%, US-1%) are applied, perfect match with 32MW19890206,
which itself is very good (total adjustment will thus be 1.01, counting the
pre-adjustment). Listed adjustment for SIL for this cruise additionally contains
a pre-adjustment of +1% (default for all Japanese Pacific SIL data).
Posted by svheuven@gmail.com on 2014-06-16 15:50:46 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19940216 - silicate
49XK19940212 and 49XK19940216 are very likely the same cruise, same leg but
different sections.
They only crossover with themselves and with 49XK19960617
Analysis of beta version of GLODAP in preparation of the Bremen 2014 workshop
showed that
all three nutrients were consistent among the three cruises (with the PO4
correction of 1.03 decided at in Groningen Oct 2013
for the two 1994 cruises applied).
The 1996 cruise has crossovers with several other cruises, and nutrients are
clearly too
low on this. Notably when compared with 32MW19890206, which is good.
This could be related to a units conversion issue and at the Bremen workshop we
hence decided that nutrients at all of these cruises should be adjusted by 1.025
to bring them into consistency with the 32MW19890206 cruise.
Posted by are.olsen@uib.no on 2014-02-20 14:56:03 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/oxygen!] |
View | |
Xresults.png | [autogenerated from RC_Siv/oxygen!] |
View | |
unadjusted_49XK19940212_49XK19940216_O2.pdf | [autogenerated from RC_Steven/oxygen!] |
View | |
unadjusted_49XK19940216_49XK19960617_O2.pdf | [autogenerated from RC_Steven/oxygen!] |
View | |
xover_sum_49XK19940216_O2.pdf | [autogenerated from RC_Steven/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:15 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19940216/oxygen: update slope+intercept
autogenerated: only BOToxy available (no CTDoxy)
Posted by svheuven@gmail.com on 2014-12-18 16:52:54 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:46 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19940216/oxygen: init slope+intercept
autogenerated: using BOToxy (no CTDoxy)
Posted by svheuven@gmail.com on 2014-02-25 17:02:21 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:15 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View 17 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:15 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19940216/oxygen: update slope+intercept
autogenerated: only BOToxy available (no CTDoxy)
Posted by svheuven@gmail.com on 2014-12-18 16:52:54 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19940216/salinity: update slope+intercept
autogenerated: only BOTsal available (no CTDsal)
Posted by svheuven@gmail.com on 2014-12-18 16:52:54 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:46 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): : make 1. After
pre-adjustments (JPN+1%, US-1%) are applied, perfect match with 32MW19890206,
which itself is very good (total adjustment will thus be 1.01, counting the
pre-adjustment). Listed adjustment for SIL for this cruise additionally contains
a pre-adjustment of +1% (default for all Japanese Pacific SIL data).
Posted by svheuven@gmail.com on 2014-06-16 15:50:46 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): : make 1.05, which makes it
match with 32MW19890206
Posted by svheuven@gmail.com on 2014-06-16 15:50:45 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): : Make 1. The units
conversion theory from an earlier comment doesn't add up.
Posted by svheuven@gmail.com on 2014-06-16 15:50:45 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:45 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:45 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:45 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19940216/oxygen: init slope+intercept
autogenerated: using BOToxy (no CTDoxy)
Posted by svheuven@gmail.com on 2014-02-25 17:02:21 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19940216/salinity: init slope+intercept
autogenerated: using BOTsal (no CTDsal)
Posted by svheuven@gmail.com on 2014-02-25 17:02:21 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19940216 - silicate
49XK19940212 and 49XK19940216 are very likely the same cruise, same leg but
different sections.
They only crossover with themselves and with 49XK19960617
Analysis of beta version of GLODAP in preparation of the Bremen 2014 workshop
showed that
all three nutrients were consistent among the three cruises (with the PO4
correction of 1.03 decided at in Groningen Oct 2013
for the two 1994 cruises applied).
The 1996 cruise has crossovers with several other cruises, and nutrients are
clearly too
low on this. Notably when compared with 32MW19890206, which is good.
This could be related to a units conversion issue and at the Bremen workshop we
hence decided that nutrients at all of these cruises should be adjusted by 1.025
to bring them into consistency with the 32MW19890206 cruise.
Posted by are.olsen@uib.no on 2014-02-20 14:56:03 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19940216 - phosphate
49XK19940212 and 49XK19940216 are very likely the same cruise, same leg but
different sections.
They only crossover with themselves and with 49XK19960617
Analysis of beta version of GLODAP in preparation of the Bremen 2014 workshop
showed that
all three nutrients were consistent for the three cruises (with the PO4
correction of 1.03 decided at in Groningen Oct 2013
for the two 1994 cruises applied).
The 1996 cruise has crossovers with several other cruises, and nutrients are
clearly too
low on this. Notably when compared with 32MW19890206, which is good.
This could be related to a units conversion issue and at the Bremen workshop we
hence decided that nutrients at these three cruises should be adjusted by 1.025
to bring them into consistency with the 32MW19890206 cruise. This brings the
adjustment for phosphate up to 1.055
Posted by are.olsen@uib.no on 2014-02-20 14:50:26 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19940216 - nitrate
49XK19940212 and 49XK19940216 are very likely the same cruise, same leg but
different sections.
They only crossover with themselves and with 49XK19960617
Analysis of beta version of GLODAP in preparation of the Bremen 2014 workshop
showed that
all three nutrients were consistent for the three cruises (with the PO4
correction of 1.03 decided at in Groningen Oct 2013
for the two 1994 cruises applied).
The 1996 cruise has crossovers with several other cruises, and nutrients are
clearly too
low on this. Notably when compared with 32MW19890206, which is good.
This could be related to a units conversion issue and at the Bremen workshop we
hence decided that nutrients from all of these three cruises should be adjusted
by 1.025
to bring them into consistency with the 32MW19890206 cruise.
Posted by are.olsen@uib.no on 2014-02-20 14:48:21 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19940216 - phosphate
At the Groningen October 2012 meeting, we agreed to change adjustment from 1 to
1.03, based on analysis of preliminary product. See two crossovers that I have
uploaded.
Posted by are.olsen@uib.no on 2014-02-18 11:46:29 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19940216 - general
Only one xover. No offset. Also consistent with leg 1 (49XK19940212).
Posted by siv.lauvset@uib.no on 2014-01-09 16:10:53 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Hide comments