Cruise: 49XK19960617 (dataset:PACIFICA) Data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023 Predecessor: GLODAPv1.2 - IGNORED
Synonyms (including errata!) for this cruise: 49XK9605; 49XK19960617; 49XK9605; P08S
IMPORTANT information for GLODAP Reference Group Editors: This is the published adjustment version (GLODAPv2) from CARINA! Click here to view previous (immutable) version (CARINA)
Please wait while loading list of related files
- no files! -
Plot/Data files re. Parameter(s) (select parameter on left side to view!):
nitrate:7
oxygen:4
phosphate:7
salinity:4
silicate:7
- no files! -
Filename: | Comment: | Action | |
---|---|---|---|
unadjusted_32MW19890206_49XK19960617_SAL.pdf | [autogenerated from RC_Steven/salinity!] |
View | |
unadjusted_49XK19940212_49XK19960617_SAL.pdf | [autogenerated from RC_Steven/salinity!] |
View | |
unadjusted_49XK19940216_49XK19960617_SAL.pdf | [autogenerated from RC_Steven/salinity!] |
View | |
xover_sum_49XK19960617_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:6; CTD salinity data good, setting CTD salinity offset and QC
flag to bottle values.
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:20 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19960617/salinity: update slope+intercept
autogenerated: BOTsal is compatible with CALIBRATED 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:46 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19960617/salinity: init slope+intercept
autogenerated: using BOTsal (few or no CTDsal or BOTsal>80%).
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_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: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:20 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): : revert +11 to 0. Only
reasonable evidence is xover with 49HG19971110. Perhaps +2 is justified, but +11
is nonsense
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
View comment(s) (filtered by alkalinity in subject)
alkalinity
There were 69 measured samples in original file. I've removed them as we can
compute significantly more values from pH and TCO2. Flag set to -888
accordingly.
Posted by avelo@iim.csic.es on 2015-08-20 10:17:31 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:39 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:46 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View comment(s) (filtered by ph in subject)
Autogenerated update by AV for pH
Bulk update requested by Anton Velo on 2015-06-04 including comments with
reasoning (src: ph_adjustments_g2_sent_carsten_20150604.xlsx / 2015-06-04): Only
1 xover for comparing calculated TALK. High offset (this cruise up in about:
0.051) against 49HG19971110
Posted by avelo@iim.csic.es on 2015-06-10 08:17:15 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated update by AV for pH
Bulk update of pH requested by Anton Velo on 2015-05-28. Comments with reasoning
will follow. (src: ph_adjustments_g2_sent_carsten_20150527.xlsx / 2015-05-28)
Posted by avelo@iim.csic.es on 2015-05-28 13:37:16 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.02
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
49XK19960617 - 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 among the three cruises (with the PO4
correction of 1.03
for the two 1994 crusies 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 unit conversion issue, and at the Bremen workshop we
hence decided that all nutrients 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:11:09 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Filename: | Comment: | Action | |
---|---|---|---|
PAIR4323___CRUISE328-49XK19940212___CRUISE330-49XK19960617___NO3.pdf | Beta version xover with 49XK19940212 cruise |
View | |
PAIR4324___CRUISE329-49XK19940216___CRUISE330-49XK19960617___NO3.pdf | Beta version xover with 49XK19940216 cruise |
View | |
PAIR840___CRUISE112-32MW19890206___CRUISE330-49XK19960617___NO3.pdf | Beta version xover with 32MW19890206 cruise |
View | |
unadjusted_32MW19890206_49XK19960617_NO3.pdf | [autogenerated from RC_Steven/nitrate!] |
View | |
unadjusted_49XK19940212_49XK19960617_NO3.pdf | [autogenerated from RC_Steven/nitrate!] |
View | |
unadjusted_49XK19940216_49XK19960617_NO3.pdf | [autogenerated from RC_Steven/nitrate!] |
View | |
xover_sum_49XK19960617_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:46 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19960617 - 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 GLODAPv2 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 suggested at 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 unit conversion issue, and at the Bremen workshop we
hence decided that all nutrients 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:03:02 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Filename: | Comment: | Action | |
---|---|---|---|
PAIR4323___CRUISE328-49XK19940212___CRUISE330-49XK19960617___PO4.pdf | Beta version xover with the 49XK19940212 cruise |
View | |
PAIR4324___CRUISE329-49XK19940216___CRUISE330-49XK19960617___PO4.pdf | beta version xover with the 49XK19940216 cruise |
View | |
PAIR840___CRUISE112-32MW19890206___CRUISE330-49XK19960617___PO4.pdf | Beta version xover with 32MW19890206 cruise |
View | |
unadjusted_32MW19890206_49XK19960617_PO4.pdf | [autogenerated from RC_Steven/phosphate!] |
View | |
unadjusted_49XK19940212_49XK19960617_PO4.pdf | [autogenerated from RC_Steven/phosphate!] |
View | |
unadjusted_49XK19940216_49XK19960617_PO4.pdf | [autogenerated from RC_Steven/phosphate!] |
View | |
xover_sum_49XK19960617_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.02
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
49XK19960617 - 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 among the three cruises (with the PO4
correction of 1.03
for the two 1994 crusies 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 unit conversion issue, and at the Bremen workshop we
hence decided that all nutrients 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:11:09 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Filename: | Comment: | Action | |
---|---|---|---|
PAIR4323___CRUISE328-49XK19940212___CRUISE330-49XK19960617___SIL.pdf | Beta version xover with the 49XK19940212 cruise |
View | |
PAIR4324___CRUISE329-49XK19940216___CRUISE330-49XK19960617___SIL.pdf | beta version xover with the 49XK19940216 cruise |
View | |
PAIR840___CRUISE112-32MW19890206___CRUISE330-49XK19960617___SIL.pdf | Beta version xover with 32MW19890206 cruise |
View | |
unadjusted_32MW19890206_49XK19960617_SIL.pdf | [autogenerated from RC_Steven/silicate!] |
View | |
unadjusted_49XK19940212_49XK19960617_SIL.pdf | [autogenerated from RC_Steven/silicate!] |
View | |
unadjusted_49XK19940216_49XK19960617_SIL.pdf | [autogenerated from RC_Steven/silicate!] |
View | |
xover_sum_49XK19960617_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.01. One very good
xover, with 32MW19890206, shows this cruise to be 3% too low. However, after
applying precorrections of +1% and -1% to JPN and US cruises respectively, it's
only 1% too low. 32MW is very accuracte, so I opt to increase 49XK19960617 by
that residual 1% (for a total adjustment of 2%, counting that 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
49XK19960617 - 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 over the three cruises (with the PO4
correction of 1.03
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 unit conversion issue, and at the Bremen workshop we
hence decided that all nutrients 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:20:40 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Filename: | Comment: | Action | |
---|---|---|---|
unadjusted_32MW19890206_49XK19960617_O2.pdf | [autogenerated from RC_Steven/oxygen!] |
View | |
unadjusted_49XK19940212_49XK19960617_O2.pdf | [autogenerated from RC_Steven/oxygen!] |
View | |
unadjusted_49XK19940216_49XK19960617_O2.pdf | [autogenerated from RC_Steven/oxygen!] |
View | |
xover_sum_49XK19960617_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:6; CTD salinity data good, setting CTD salinity offset and QC
flag to bottle values.
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:20 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19960617/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): : make 1.00
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
49XK19960617/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:6; CTD salinity data good, setting CTD salinity offset and QC
flag to bottle values.
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:20 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View 20 comment(s) (Lists all comments)
alkalinity
There were 69 measured samples in original file. I've removed them as we can
compute significantly more values from pH and TCO2. Flag set to -888
accordingly.
Posted by avelo@iim.csic.es on 2015-08-20 10:17:31 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated update by AV for pH
Bulk update requested by Anton Velo on 2015-06-04 including comments with
reasoning (src: ph_adjustments_g2_sent_carsten_20150604.xlsx / 2015-06-04): Only
1 xover for comparing calculated TALK. High offset (this cruise up in about:
0.051) against 49HG19971110
Posted by avelo@iim.csic.es on 2015-06-10 08:17:15 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated update by AV for pH
Bulk update of pH requested by Anton Velo on 2015-05-28. Comments with reasoning
will follow. (src: ph_adjustments_g2_sent_carsten_20150527.xlsx / 2015-05-28)
Posted by avelo@iim.csic.es on 2015-05-28 13:37:16 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
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: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:20 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:39 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19960617/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
49XK19960617/salinity: update slope+intercept
autogenerated: BOTsal is compatible with CALIBRATED 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): : make 1.00
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.01. One very good
xover, with 32MW19890206, shows this cruise to be 3% too low. However, after
applying precorrections of +1% and -1% to JPN and US cruises respectively, it's
only 1% too low. 32MW is very accuracte, so I opt to increase 49XK19960617 by
that residual 1% (for a total adjustment of 2%, counting that 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.02
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 - 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:46 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:46 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): : revert +11 to 0. Only
reasonable evidence is xover with 49HG19971110. Perhaps +2 is justified, but +11
is nonsense
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 - 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:46 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19960617/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
49XK19960617/salinity: init slope+intercept
autogenerated: using BOTsal (few or no CTDsal or BOTsal>80%).
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
49XK19960617 - 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 over the three cruises (with the PO4
correction of 1.03
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 unit conversion issue, and at the Bremen workshop we
hence decided that all nutrients 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:20:40 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19960617 - 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 among the three cruises (with the PO4
correction of 1.03
for the two 1994 crusies 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 unit conversion issue, and at the Bremen workshop we
hence decided that all nutrients 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:11:09 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49XK19960617 - 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 GLODAPv2 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 suggested at 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 unit conversion issue, and at the Bremen workshop we
hence decided that all nutrients 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:03:02 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
adjustements from PACIFICA
Posted by ttanhua@geomar.de on 2012-07-12 10:54:33 UTC for data product: GLODAPv1.2 - IGNORED
Hide comments