Cruise: 316N19720718.1 (dataset:GLODAPv1.2) Data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Synonyms (including errata!) for this cruise: GEOSECS_1; 316N19720718.1; GEOSECS_1; GEOSECS_leg1; geoatl
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 | |
---|---|---|---|
offsets.png | [autogenerated from RC_Are/adjustments!] |
View |
- no files! -
Plot/Data files re. Parameter(s) (select parameter on left side to view!):
alkalinity:31
cruise:1
nitrate:76
oxygen:83
phosphate:69
salinity:82
silicate:77
tco2:39
- 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: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:23 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_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, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1/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, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1/salinity: init slope+intercept
autogenerated: using BOTsal (no CTDsal)
Posted by svheuven@gmail.com on 2014-02-25 17:02:12 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - salinity
First AO GEOSECS leg. The inversion suggest a correction of -26.6 ppm based on 8
crossovers with a mean offset of 33.975. But this is a Irminger and Lab Sea
cruise with potentially huge changes since the 70s. DO not adjust.
Posted by are.olsen@uib.no on 2012-08-31 12:01:09 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: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: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_ATL_for_Carsten.xls / 2015-01-08): : make -999. No DIC data for leg 1
of GEOSECS
Posted by svheuven@gmail.com on 2015-01-08 16:41:00 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - tco2
For now, for the purpose of preparing GLODAPv1.2, this is set to 0. Will be
revised later, based on Peng & Wanninkhof 2010 results. GEOSECS will not be used
as reference for CLIVAR anyway.
Posted by are.olsen@uib.no on 2013-01-21 12:42:05 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - tco2
Adjustments are based on results in Peng and Wanninkhof (2010). Peng and
Wanninkhof (2010) does not include this leg in their analysis. I do not know
whether this is because there are no carbon data or for some other reason.
Posted by siv.lauvset@uib.no on 2013-01-09 17:09:24 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_ATL_for_Carsten.xls / 2015-01-08): : make -999. No ALK data for leg 1
of GEOSECS
Posted by svheuven@gmail.com on 2015-01-08 16:41:00 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - alkalinity
For now, for the purpose of preparing GLODAPv1.2, this is set to 0. Will be
revised later, based on Peng & Wanninkhof 2010 results. GEOSECS will not be used
as reference for CLIVAR anyway.
Posted by are.olsen@uib.no on 2013-01-21 12:42:19 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_ATL_for_Carsten.xls / 2015-01-08): : maintain 1.00. Hard to tell
because of temporal changes, but all later cruises are comparable to GEOSECS leg
1 (0.5±6%, n=19), with no clear temporal trend.
Posted by svheuven@gmail.com on 2015-01-08 16:41:00 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - phosphate
This is set to 1, based on Peng & Wanninkhof (2010) suggesting insignificant
nutrient offsets in Atlantic GEOSECS.
Posted by are.olsen@uib.no on 2013-01-21 13:01:07 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - phosphate
New inversion for phosphate in the Atlantic with 10 core cruises assigned
confirms that NO adjustment should be applied.
Posted by mario.hoppema@awi.de on 2013-01-10 09:48:50 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - phosphate
Suggested correction is 0.9543 and mean offset is 0.978.
Data from Irminger Basin, 20 years before next and 30 years before most, and
next few legs look fine if not high. Do not adjust.
Posted by are.olsen@uib.no on 2012-09-12 08:56:19 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_ATL_for_Carsten.xls / 2015-01-08): : make 0.97. Hard to tell because of
temporal changes, but all later cruises are lower than GEOSECS leg 1 (-3.4±2.8%,
n=20), with no clear temporal trend.
Posted by svheuven@gmail.com on 2015-01-08 16:41:00 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - nitrate
This is set to 1, based on Peng & Wanninkhof (2010) suggesting insignificant
nutrient offsets in Atlantic GEOSECS.
Posted by are.olsen@uib.no on 2013-01-21 13:01:00 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - nitrate
Suggested correction is 0.946 and mean offset is 1.03.
But these are data from the Irminger Basin, 20 years before next and 30 years
before most cruises, and next few legs look fine. No adjustment can be
recommended based on this.
Posted by are.olsen@uib.no on 2012-09-03 10:10:52 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_ATL_for_Carsten.xls / 2015-01-08): : maintain 1.00. Hard to tell
because of temporal changes, but all later cruises are comparable to GEOSECS leg
1 (0.5±6%, n=19), with no clear temporal trend.
Posted by svheuven@gmail.com on 2015-01-08 16:41:00 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - phosphate
This is set to 1, based on Peng & Wanninkhof (2010) suggesting insignificant
nutrient offsets in Atlantic GEOSECS.
Posted by are.olsen@uib.no on 2013-01-21 13:01:07 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - phosphate
New inversion for phosphate in the Atlantic with 10 core cruises assigned
confirms that NO adjustment should be applied.
Posted by mario.hoppema@awi.de on 2013-01-10 09:48:50 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - phosphate
Suggested correction is 0.9543 and mean offset is 0.978.
Data from Irminger Basin, 20 years before next and 30 years before most, and
next few legs look fine if not high. Do not adjust.
Posted by are.olsen@uib.no on 2012-09-12 08:56:19 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
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, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - silicate
This is set to 1, based on Peng & Wanninkhof (2010) suggesting insignificant
nutrient offsets in Atlantic GEOSECS.
Posted by are.olsen@uib.no on 2013-01-21 13:01:14 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - silicate
The inversion suggest a correction of 0.94 and the mean offset is 1.06 and the
data clearly appears high. These are Irminger Sea, NASPG, DWBC data. Anything
might have happened in the decades that separate this cruise from the others in
the collection. Do not adjust.
Posted by are.olsen@uib.no on 2012-09-15 13:21:17 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: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:23 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_ATL_for_Carsten.xls / 2015-01-08): : maintain 0.99
Posted by svheuven@gmail.com on 2015-01-08 16:41:00 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1/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, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1/oxygen: init slope+intercept
autogenerated: using BOToxy (no CTDoxy)
Posted by svheuven@gmail.com on 2014-02-25 17:02:12 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - oxygen
This is set to 0.99, following Peng & Wanninkhof finding 3.5 umol/kg bias in
Atlantic GEOSECS.
Posted by are.olsen@uib.no on 2013-01-21 13:17:54 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - oxygen
The inversion suggest that these data should be corrected using a factor. 1.01
based on 4 crossovers with a mean offset of 0.98. Old NASPG cruise. Do not
adjust.
Posted by are.olsen@uib.no on 2012-09-17 14:54:57 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:23 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View 25 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:23 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_ATL_for_Carsten.xls / 2015-01-08): : maintain 0.99
Posted by svheuven@gmail.com on 2015-01-08 16:41:00 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_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, 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_ATL_for_Carsten.xls / 2015-01-08): : maintain 1.00. Hard to tell
because of temporal changes, but all later cruises are comparable to GEOSECS leg
1 (0.5±6%, n=19), with no clear temporal trend.
Posted by svheuven@gmail.com on 2015-01-08 16:41:00 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_ATL_for_Carsten.xls / 2015-01-08): : make 0.97. Hard to tell because of
temporal changes, but all later cruises are lower than GEOSECS leg 1 (-3.4±2.8%,
n=20), with no clear temporal trend.
Posted by svheuven@gmail.com on 2015-01-08 16:41:00 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_ATL_for_Carsten.xls / 2015-01-08): : make -999. No ALK data for leg 1
of GEOSECS
Posted by svheuven@gmail.com on 2015-01-08 16:41:00 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_ATL_for_Carsten.xls / 2015-01-08): : make -999. No DIC data for leg 1
of GEOSECS
Posted by svheuven@gmail.com on 2015-01-08 16:41:00 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_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, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1/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, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1/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, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1/oxygen: init slope+intercept
autogenerated: using BOToxy (no CTDoxy)
Posted by svheuven@gmail.com on 2014-02-25 17:02:12 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1/salinity: init slope+intercept
autogenerated: using BOTsal (no CTDsal)
Posted by svheuven@gmail.com on 2014-02-25 17:02:12 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - oxygen
This is set to 0.99, following Peng & Wanninkhof finding 3.5 umol/kg bias in
Atlantic GEOSECS.
Posted by are.olsen@uib.no on 2013-01-21 13:17:54 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - silicate
This is set to 1, based on Peng & Wanninkhof (2010) suggesting insignificant
nutrient offsets in Atlantic GEOSECS.
Posted by are.olsen@uib.no on 2013-01-21 13:01:14 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - phosphate
This is set to 1, based on Peng & Wanninkhof (2010) suggesting insignificant
nutrient offsets in Atlantic GEOSECS.
Posted by are.olsen@uib.no on 2013-01-21 13:01:07 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - nitrate
This is set to 1, based on Peng & Wanninkhof (2010) suggesting insignificant
nutrient offsets in Atlantic GEOSECS.
Posted by are.olsen@uib.no on 2013-01-21 13:01:00 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - alkalinity
For now, for the purpose of preparing GLODAPv1.2, this is set to 0. Will be
revised later, based on Peng & Wanninkhof 2010 results. GEOSECS will not be used
as reference for CLIVAR anyway.
Posted by are.olsen@uib.no on 2013-01-21 12:42:19 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - tco2
For now, for the purpose of preparing GLODAPv1.2, this is set to 0. Will be
revised later, based on Peng & Wanninkhof 2010 results. GEOSECS will not be used
as reference for CLIVAR anyway.
Posted by are.olsen@uib.no on 2013-01-21 12:42:05 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - phosphate
New inversion for phosphate in the Atlantic with 10 core cruises assigned
confirms that NO adjustment should be applied.
Posted by mario.hoppema@awi.de on 2013-01-10 09:48:50 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - tco2
Adjustments are based on results in Peng and Wanninkhof (2010). Peng and
Wanninkhof (2010) does not include this leg in their analysis. I do not know
whether this is because there are no carbon data or for some other reason.
Posted by siv.lauvset@uib.no on 2013-01-09 17:09:24 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - oxygen
The inversion suggest that these data should be corrected using a factor. 1.01
based on 4 crossovers with a mean offset of 0.98. Old NASPG cruise. Do not
adjust.
Posted by are.olsen@uib.no on 2012-09-17 14:54:57 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - silicate
The inversion suggest a correction of 0.94 and the mean offset is 1.06 and the
data clearly appears high. These are Irminger Sea, NASPG, DWBC data. Anything
might have happened in the decades that separate this cruise from the others in
the collection. Do not adjust.
Posted by are.olsen@uib.no on 2012-09-15 13:21:17 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - phosphate
Suggested correction is 0.9543 and mean offset is 0.978.
Data from Irminger Basin, 20 years before next and 30 years before most, and
next few legs look fine if not high. Do not adjust.
Posted by are.olsen@uib.no on 2012-09-12 08:56:19 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - nitrate
Suggested correction is 0.946 and mean offset is 1.03.
But these are data from the Irminger Basin, 20 years before next and 30 years
before most cruises, and next few legs look fine. No adjustment can be
recommended based on this.
Posted by are.olsen@uib.no on 2012-09-03 10:10:52 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
316N19720718.1 - salinity
First AO GEOSECS leg. The inversion suggest a correction of -26.6 ppm based on 8
crossovers with a mean offset of 33.975. But this is a Irminger and Lab Sea
cruise with potentially huge changes since the 70s. DO not adjust.
Posted by are.olsen@uib.no on 2012-08-31 12:01:09 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Hide comments