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:18 UTC for data product: GLODAPv2

Autogenerated comment - salinity

Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2_ATL_for_Carsten.xls / 2015-01-08): : maintain 0

Posted by svheuven@gmail.com on 2015-01-08 16:41:00 UTC for data product: GLODAPv2

316N19810619/salinity: update slope+intercept

autogenerated: only BOTsal available (no CTDsal)

Posted by svheuven@gmail.com on 2014-12-18 16:52:40 UTC for data product: GLODAPv2

316N19810619 - salinity

The inversion suggest a correction of -0.27. No adjustment is recommended.

Posted by are.olsen@uib.no on 2012-08-31 13:17:41 UTC for data product: GLODAPv2

Hide 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:18 UTC for data product: GLODAPv2

Hide comments

316N19810619 - tco2

Negating any previous comments, for TTONAS, GLODAPv2 uses the reanalyzed TCO2
and TALK data published by Tanhua and Wallace (2005), without any subsequent
adjustments. Data quality is considered good. "QC'ed yes/no" flags are set to
"NO", because QC performed by T&W2005 is distinct and different from GLODAPv2's
methodology.

Posted by svheuven@gmail.com on 2015-07-06 22:03:59 UTC for data product: GLODAPv2

Autogenerated comment - tCO2

Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2_ATL_for_Carsten.xls / 2015-01-08): : maintain 0. TTONAS has excellent
DIC (likely because we use Toste's revised version (Tanhua Wallace 2005).

Posted by svheuven@gmail.com on 2015-01-08 16:41:00 UTC for data product: GLODAPv2

316N19810619 - tco2

The adjusted data from Tanhua and Wallace (2006, GRL, doi:10.1029/2006GB002695)
is used already for the GLODAPv2 product, hence no further adjustment required.

Posted by ttanhua@geomar.de on 2014-02-12 14:03:13 UTC for data product: GLODAPv2

316N19810619 - tco2

For now, for purpose of GLODAPv1.2, do not adjust. We need to look more closely
at these data, in particular whether these are the original or Brewer revised
(CDIAC NDP 004) total carbon data. Will be done for GLODAPv2. Plan is to follow
the Tanhua and Wallace (2005) suggested correction.

Posted by are.olsen@uib.no on 2013-01-22 11:20:46 UTC for data product: GLODAPv2

316N19810619 - tco2

Mean offset with 10 cruises: -1.2
Inversion suggests insignificant +1.4
Many of these cruises have good x-overs with 316N19810619.
Therefore, NO adjustment

Posted by mario.hoppema@awi.de on 2012-11-19 14:53:34 UTC for data product: GLODAPv2

Hide comments

316N19810619 - alkalinity

Negating any previous comments, for TTONAS, GLODAPv2 uses the reanalyzed TCO2
and TALK data published by Tanhua and Wallace (2005), without any subsequent
adjustments. Data quality is considered good. "QC'ed yes/no" flags are set to
"NO", because QC performed by T&W2005 is distinct and different from GLODAPv2's
methodology.

Posted by svheuven@gmail.com on 2015-07-06 22:04:03 UTC for data product: GLODAPv2

Autogenerated comment - alkalinity

Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2_ATL_for_Carsten.xls / 2015-01-08): : Maintain 0. This is the suggestion
by the split-cruises inversion. See accompanying explanatory document
(Atlantic_Alkalinity.pdf or similar)

Posted by svheuven@gmail.com on 2015-01-08 16:41:00 UTC for data product: GLODAPv2

316N19810619 - alkalinity

The adjusted data from Tanhua and Wallace (2006, GRL, doi:10.1029/2006GB002695)
is used already for the GLODAPv2 product, hence no further adjustment required.

Posted by ttanhua@geomar.de on 2014-02-12 14:03:20 UTC for data product: GLODAPv2

316N19810619 - alkalinity

For now, with time constraints, and for the purpose of GLODAPv1.2 these are not
corrected. Consider more closely later, taking account of Tanhua and Wallace
(2005) later (for GLODAPv2).

Posted by are.olsen@uib.no on 2013-01-22 11:32:40 UTC for data product: GLODAPv2

316N19810619 - alkalinity

Mean offset with 8 cruises -10.2 , but this is strongly biased by some very low
cruises. There are some 5 cruises with reliable x-overs which show an
insignificant offset and thus warrant no adjustment.
Because of this, I suggest NO adjustment

Posted by mario.hoppema@awi.de on 2012-12-11 16:35:11 UTC for data product: GLODAPv2

Hide comments

Autogenerated comment - phosphate

Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2_ATL_for_Carsten.xls / 2015-01-08): : maintain 1.00

Posted by svheuven@gmail.com on 2015-01-08 16:41:00 UTC for data product: GLODAPv2

316N19810619 - phosphate

New inversion for phosphate in the Atlantic with 10 core cruises assigned
suggests no significant adjustment. Therefore the previous assessement is
confirmed, i.e., no adjustment.

Posted by mario.hoppema@awi.de on 2012-11-24 21:19:25 UTC for data product: GLODAPv2

316N19810619 - phosphate

Bergen workshop. Now that the adjustment of 06MT19910902 has been revised up,
the argument does not hold. Do not adjust.

Posted by are.olsen@uib.no on 2012-11-12 15:47:57 UTC for data product: GLODAPv2

316N19810619 - phosphate

Suggested correction is 0.9635, and mean offset is 0.993. These data are from
eastern NO. Compared to 06MT19970611, and also (corrected) 06MT19910902 data,
these data appears clearly high. I recommend that they are adjusted using the
same factor as the previous leg, 0.97.

Posted by are.olsen@uib.no on 2012-09-12 10:01:06 UTC for data product: GLODAPv2

Hide comments

Hide comments

Autogenerated comment - nitrate

Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2_ATL_for_Carsten.xls / 2015-01-08): : maintain 1.00.

Posted by svheuven@gmail.com on 2015-01-08 16:41:00 UTC for data product: GLODAPv2

316N19810619 - nitrate

Suggested correction was 0.98. Mean offset is 1. Appears fine and do not
adjust.

Posted by are.olsen@uib.no on 2012-09-03 21:49:38 UTC for data product: GLODAPv2

Hide comments

Autogenerated comment - phosphate

Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2_ATL_for_Carsten.xls / 2015-01-08): : maintain 1.00

Posted by svheuven@gmail.com on 2015-01-08 16:41:00 UTC for data product: GLODAPv2

316N19810619 - phosphate

New inversion for phosphate in the Atlantic with 10 core cruises assigned
suggests no significant adjustment. Therefore the previous assessement is
confirmed, i.e., no adjustment.

Posted by mario.hoppema@awi.de on 2012-11-24 21:19:25 UTC for data product: GLODAPv2

316N19810619 - phosphate

Bergen workshop. Now that the adjustment of 06MT19910902 has been revised up,
the argument does not hold. Do not adjust.

Posted by are.olsen@uib.no on 2012-11-12 15:47:57 UTC for data product: GLODAPv2

316N19810619 - phosphate

Suggested correction is 0.9635, and mean offset is 0.993. These data are from
eastern NO. Compared to 06MT19970611, and also (corrected) 06MT19910902 data,
these data appears clearly high. I recommend that they are adjusted using the
same factor as the previous leg, 0.97.

Posted by are.olsen@uib.no on 2012-09-12 10:01:06 UTC for data product: GLODAPv2

Hide comments

Autogenerated comment - silicate

Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2_ATL_for_Carsten.xls / 2015-01-08): : maintain 1.00 (not re-inspected
for GLODAPv2)

Posted by svheuven@gmail.com on 2015-01-08 16:41:00 UTC for data product: GLODAPv2

316N19810619 - silicate

Inversion suggest a 0.9839 correction based on 13 crossovers with mean offset of
1.019. Based on age and no adjustments for the other legs, no adjustments
recommended.

Posted by are.olsen@uib.no on 2012-09-15 13:49:14 UTC for data product: GLODAPv2

Hide 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:18 UTC for data product: GLODAPv2

Autogenerated comment - oxygen

Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2_ATL_for_Carsten.xls / 2015-01-08): : maintain 1.00

Posted by svheuven@gmail.com on 2015-01-08 16:41:00 UTC for data product: GLODAPv2

316N19810619/oxygen: update slope+intercept

autogenerated: only BOToxy available (no CTDoxy)

Posted by svheuven@gmail.com on 2014-12-18 16:52:40 UTC for data product: GLODAPv2

316N19810619 - oxygen

The inversion suggest that these data should be corrected using a factor of
1.0021 based on 13 crossovers with a mean offset of 1.001. Do not adjust.

Posted by are.olsen@uib.no on 2012-09-18 09:21:19 UTC for data product: GLODAPv2

Hide 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:18 UTC for data product: GLODAPv2

Hide comments

Hide comments

Hide comments

Hide comments

Hide comments

316N19810619 - c13

Becker et al. 2016:
The inversion does not suggest any correction for the TTO-NAS dataset.

Posted by nlange@geomar.de on 2018-09-06 09:39:37 UTC for data product: GLODAPv2.2019, v2.2020, v2.2021, v2.2022, v2.2023

Hide comments

Hide comments