Cruise: 49HH20011127 (dataset:PACIFICA) Data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Synonyms (including errata!) for this cruise: KH01-3_L1; 49HH20011127; KH01-3_L1; Project/Section: MRI-ORI; erratum:49HH20011208 in CARINA!
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!):
nitrate:12
oxygen:12
phosphate:11
salinity:12
silicate:12
- no files! -
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:7; CTD oxygen data are bad, setting CTD oxygen offset to -777
and remove QC flag.
Posted by svheuven@gmail.com on 2015-02-19 09:22:23 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49HH20011127/salinity: update slope+intercept
autogenerated: BOTsal is compatible with CALIBRATED CTDsal
Posted by svheuven@gmail.com on 2014-12-18 16:52:50 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. Suggestion of
-0.007 appears to be spurious, resulting from two southerly stations at western
appear which appear low due to being on continental slope.
Posted by svheuven@gmail.com on 2014-06-16 15:50:39 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49HH20011127/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:18 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:7; CTD oxygen data are bad, setting CTD oxygen offset to -777
and remove QC flag.
Posted by svheuven@gmail.com on 2015-02-19 09:22:23 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): : make 0
Posted by svheuven@gmail.com on 2014-06-16 15:50:39 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:39 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. Adjustment ill
constrained due to wavey, scattered profiles, but clearly requires upward
adjustment. Two sections, far apart (one 140E, one 160W(!)). Can't assess
Pacific data due to sparseness (1 deep profile, scattery). Indian data may be of
some use. Not sure if sections share calibration perfectly. I'd say split or
discard Pacific section, keep Indian one.
Posted by svheuven@gmail.com on 2014-06-16 15:50:39 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
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:39 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
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. Adjustment ill
constrained due to wavey, scattered profiles, but clearly requires upward
adjustment. Two sections, far apart (one 140E, one 160W(!)). Can't assess
Pacific data due to sparseness (1 deep profile, scattery). Indian data may be of
some use. Not sure if sections share calibration perfectly. I'd say split or
discard Pacific section, keep Indian one.
Posted by svheuven@gmail.com on 2014-06-16 15:50:39 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
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:44 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 -888. Two sections,
far apart (one 140E, one 160W(!)). Can't assess Pacific data due to sparseness
(1 deep profile, scattery). Indian data may be of some use. Not sure if sections
share calibration perfectly. I'd say split or discard Pacific section, keep
Indian one. 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:39 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
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:7; CTD oxygen data are bad, setting CTD oxygen offset to -777
and remove QC flag.
Posted by svheuven@gmail.com on 2015-02-19 09:22:23 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49HH20011127/oxygen: update slope+intercept
autogenerated: CTDoxy is NOT compatible with BOToxy and no (simple) calibration
is possible
Posted by svheuven@gmail.com on 2014-12-18 16:52:50 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. This brings it
quite close to 09AR20041223 (after that gets corrected 0.985).
Posted by svheuven@gmail.com on 2014-06-16 15:50:39 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49HH20011127/oxygen: init slope+intercept
autogenerated: using BOToxy (few or no CTDoxy or BOToxy>80%).
Posted by svheuven@gmail.com on 2014-02-25 17:02:18 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:7; CTD oxygen data are bad, setting CTD oxygen offset to -777
and remove QC flag.
Posted by svheuven@gmail.com on 2015-02-19 09:22:23 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View 14 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:7; CTD oxygen data are bad, setting CTD oxygen offset to -777
and remove QC flag.
Posted by svheuven@gmail.com on 2015-02-19 09:22:23 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:44 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49HH20011127/oxygen: update slope+intercept
autogenerated: CTDoxy is NOT compatible with BOToxy and no (simple) calibration
is possible
Posted by svheuven@gmail.com on 2014-12-18 16:52:50 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49HH20011127/salinity: update slope+intercept
autogenerated: BOTsal is compatible with CALIBRATED CTDsal
Posted by svheuven@gmail.com on 2014-12-18 16:52:50 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. This brings it
quite close to 09AR20041223 (after that gets corrected 0.985).
Posted by svheuven@gmail.com on 2014-06-16 15:50:39 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 -888. Two sections,
far apart (one 140E, one 160W(!)). Can't assess Pacific data due to sparseness
(1 deep profile, scattery). Indian data may be of some use. Not sure if sections
share calibration perfectly. I'd say split or discard Pacific section, keep
Indian one. 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:39 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. Adjustment ill
constrained due to wavey, scattered profiles, but clearly requires upward
adjustment. Two sections, far apart (one 140E, one 160W(!)). Can't assess
Pacific data due to sparseness (1 deep profile, scattery). Indian data may be of
some use. Not sure if sections share calibration perfectly. I'd say split or
discard Pacific section, keep Indian one.
Posted by svheuven@gmail.com on 2014-06-16 15:50:39 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: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:39 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): : make 0
Posted by svheuven@gmail.com on 2014-06-16 15:50:39 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. Suggestion of
-0.007 appears to be spurious, resulting from two southerly stations at western
appear which appear low due to being on continental slope.
Posted by svheuven@gmail.com on 2014-06-16 15:50:39 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49HH20011127/oxygen: init slope+intercept
autogenerated: using BOToxy (few or no CTDoxy or BOToxy>80%).
Posted by svheuven@gmail.com on 2014-02-25 17:02:18 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
49HH20011127/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:18 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
No subject
This cruise was included in PACIFICA and CARINA. The CARINA name was
49HH20011208. CARINA included leg 1 and 2, while PACIFICA only leg 1. No
adjustments derived for this cruise in PACIFICA, while adjustments were derived
in CARINA. We will use the CARINA adjustments, all preliminary product files
were prepared with these adjustments applied, and data showed not significant
offset.
Posted by are.olsen@uib.no on 2014-02-18 08:04:06 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Hide comments