Cruise: 74JC19960720 (dataset:CARINA) Data product: GLODAPv2.2022, v2.2023 Predecessor: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021
Synonyms (including errata!) for this cruise: 74JC9608; Greenland-Norwegian Sea; 74JC19960720; 74JC9608; Greenland-Norwegian Sea;
IMPORTANT information for GLODAP Reference Group Editors: This is the published adjustment version (GLODAPv2.2022) from GLODAPv2.2021! Click here to view previous (immutable) version (GLODAPv2.2021)
Please wait while loading list of related files


Plot/Data files re. Parameter(s) (select parameter on left side to view!): - 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: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:17 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021
74JC19960720/salinity: update slope+intercept
autogenerated: BOTsal is compatible with CALIBRATED CTDsal
Posted by svheuven@gmail.com on 2014-12-18 16:52:37 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021
74JC19960720/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:11 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021
74JC19960720 - salinity
Analysis of Nordic Seas salinity data indicated no offset for these data, see
also Nordic Sea salinity data report at
http://carboocean.ifm-geomar.de/postings/list
Are Olsen, Bergen, Norway, Aug 8 2008
Posted by are.olsen@uib.no on 2008-08-08 09:25:30 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021


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:17 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021


View comment(s) (filtered by tco2 in subject)
74JC19960720 - tco2
Inversion analyses and profiles indicated that the data were OK. See Nordic Seas
tco2 summary document at http://carboocean.ifm-geomar.de/postings/list for
details. Figure below -taken from summary document - shows inversion from
autogenerated crossovers with TTO-NAS data and 74JC19960720 highlighted.
Are Olsen
Bergen, Norway, 2 Jul 2008
Posted by are.olsen@uib.no on 2008-07-02 10:38:30 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021


View comment(s) (filtered by alkalinity in subject)
74JC19960720 - alkalinity
Inversion of manual crossover results gave an offset of 15.4 umol/kg.
Regession analyses of deep values (using alk-sal relationships) gave offset of
16 umol kg.
A reasonable adjustment is 15.5 umol/kg, this also resulted in realistic
alkalinty profiles for this cruise
This is described in the Nordic Seas alkalinity summary document at
http://carboocean.ifm-geomar.de/postings/list
Below I have uploaded page with the inversion results and 74JC19960720 cruise
highlighted.
Are Olsen
Bergen, Norway, 2 July 2008.
Posted by are.olsen@uib.no on 2008-07-02 10:46:21 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021






View comment(s) (filtered by nitrate in subject)
74JC19960720 - nitrate
The inversion suggested that this cruise was 20% too high. Figure 5 shows
nitrate profiles from this and previous and subsequent good cruises. Data
selection limited to Greenland Sea (73-80ON, 25OW to 3OE) where the 74JC19960720
cruise was carried out. The red indicators show the 74JC19960720 corrected by
0.83 (i.e. down by 17%). A factor of 0.8 gave somewhat low values compared to
the simultaneous 58JH19960720 cruise (deep mean hitting the -5% limit). 0.84
seemed a bit to high, in particular since the inversion suggested that the
58JH19960720 cruise was a bit on the high side. Thus 0.83 seems reasonable and
is suggested as the correction factor for these data.
Posted by jon@hafro.is on 2008-09-05 00:28:44 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021






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:17 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021
74JC19960720/oxygen: update slope+intercept
autogenerated: only BOToxy available (no CTDoxy)
Posted by svheuven@gmail.com on 2014-12-18 16:52:37 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021
74JC19960720/oxygen: init slope+intercept
autogenerated: using BOToxy (no CTDoxy)
Posted by svheuven@gmail.com on 2014-02-25 17:02:11 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021
74JC19960720 - oxygen
These data were part of the Nordic Seas CARINA oxygen analyses.
The analyses showed that the data were too high and should be adjusted down by
the specified fraction. The details can be found in the Nordic Seas oxygen
report available at at http://carboocean.ifm-geomar.de/postings/list.
Are Olsen
Bergen, Norway, Aug 14 2008
Posted by are.olsen@uib.no on 2008-08-14 11:19:43 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021


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:17 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021


View comment(s) (filtered by cfc12 in subject)
74JC19960720 - cfc12
The CFCs were included in a late stage for this cruise and therefore they were
not included in the crossover analysis. However, the CFC12 values from
74JC19960720 are consistent with the values from other CARINA cruises between
1995 and 1997, and the uncertainty in the data seems OK, and they are thus
recommended to be included in the merged data set.
Posted by emje@norceresearch.no on 2009-05-21 16:37:29 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021


View comment(s) (filtered by cfc11 in subject)
74JC19960720 - cfc113
The CFCs were included in a late stage for this cruise and therefore they were
not included in the crossover analysis. However, the CFC113 values from
74JC19960720 are consistent with the values from other CARINA cruises between
1995 and 1997, and the uncertainty in the data seems OK, and they are thus
recommended to be included in the merged data set.
Posted by emje@norceresearch.no on 2009-05-21 16:39:25 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021
74JC19960720 - cfc11
The CFCs were included in a late stage for this cruise and therefore they were
not included in the crossover analysis. However, the CFC11 values from
74JC19960720 are consistent with the values from other CARINA cruises between
1995 and 1997, and the uncertainty in the data seems OK, and they are thus
recommended to be included in the merged data set.
Posted by emje@norceresearch.no on 2009-05-21 16:38:58 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021


View comment(s) (filtered by cfc113 in subject)
74JC19960720 - cfc113
The CFCs were included in a late stage for this cruise and therefore they were
not included in the crossover analysis. However, the CFC113 values from
74JC19960720 are consistent with the values from other CARINA cruises between
1995 and 1997, and the uncertainty in the data seems OK, and they are thus
recommended to be included in the merged data set.
Posted by emje@norceresearch.no on 2009-05-21 16:39:25 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021


View comment(s) (filtered by ccl4 in subject)
74JC19960720 - ccl4
The CFCs were included in a late stage for this cruise and therefore they were
not included in the crossover analysis. The other CFCs from this cruise are
consistent with the values from other CARINA cruises between 1995 and 1997, but
there is an issue with the CCl4 values, which are both clearly lower, for almost
all parts of the water column, and with a much larger uncertainty. At the same
time the surface saturation of CCl4 fro this cruise seem even some what higher
than for the compared cruises. Due to this, and the fact that there are good
data from the other cruises between 1995 and 1997 I recommend to excluded the
CCl4 data from this cruise from the merged data product.
recommended to be included in the merged data set.
Posted by emje@norceresearch.no on 2009-05-21 16:43:53 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021




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: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:17 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021
74JC19960720/oxygen: update slope+intercept
autogenerated: only BOToxy available (no CTDoxy)
Posted by svheuven@gmail.com on 2014-12-18 16:52:37 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021
74JC19960720/salinity: update slope+intercept
autogenerated: BOTsal is compatible with CALIBRATED CTDsal
Posted by svheuven@gmail.com on 2014-12-18 16:52:37 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021
74JC19960720/oxygen: init slope+intercept
autogenerated: using BOToxy (no CTDoxy)
Posted by svheuven@gmail.com on 2014-02-25 17:02:11 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021
74JC19960720/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:11 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021
74JC19960720 - ccl4
The CFCs were included in a late stage for this cruise and therefore they were
not included in the crossover analysis. The other CFCs from this cruise are
consistent with the values from other CARINA cruises between 1995 and 1997, but
there is an issue with the CCl4 values, which are both clearly lower, for almost
all parts of the water column, and with a much larger uncertainty. At the same
time the surface saturation of CCl4 fro this cruise seem even some what higher
than for the compared cruises. Due to this, and the fact that there are good
data from the other cruises between 1995 and 1997 I recommend to excluded the
CCl4 data from this cruise from the merged data product.
recommended to be included in the merged data set.
Posted by emje@norceresearch.no on 2009-05-21 16:43:53 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021
74JC19960720 - cfc113
The CFCs were included in a late stage for this cruise and therefore they were
not included in the crossover analysis. However, the CFC113 values from
74JC19960720 are consistent with the values from other CARINA cruises between
1995 and 1997, and the uncertainty in the data seems OK, and they are thus
recommended to be included in the merged data set.
Posted by emje@norceresearch.no on 2009-05-21 16:39:25 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021
74JC19960720 - cfc11
The CFCs were included in a late stage for this cruise and therefore they were
not included in the crossover analysis. However, the CFC11 values from
74JC19960720 are consistent with the values from other CARINA cruises between
1995 and 1997, and the uncertainty in the data seems OK, and they are thus
recommended to be included in the merged data set.
Posted by emje@norceresearch.no on 2009-05-21 16:38:58 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021
74JC19960720 - cfc12
The CFCs were included in a late stage for this cruise and therefore they were
not included in the crossover analysis. However, the CFC12 values from
74JC19960720 are consistent with the values from other CARINA cruises between
1995 and 1997, and the uncertainty in the data seems OK, and they are thus
recommended to be included in the merged data set.
Posted by emje@norceresearch.no on 2009-05-21 16:37:29 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021
74JC19960720 - nitrate
The inversion suggested that this cruise was 20% too high. Figure 5 shows
nitrate profiles from this and previous and subsequent good cruises. Data
selection limited to Greenland Sea (73-80ON, 25OW to 3OE) where the 74JC19960720
cruise was carried out. The red indicators show the 74JC19960720 corrected by
0.83 (i.e. down by 17%). A factor of 0.8 gave somewhat low values compared to
the simultaneous 58JH19960720 cruise (deep mean hitting the -5% limit). 0.84
seemed a bit to high, in particular since the inversion suggested that the
58JH19960720 cruise was a bit on the high side. Thus 0.83 seems reasonable and
is suggested as the correction factor for these data.
Posted by jon@hafro.is on 2008-09-05 00:28:44 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021
74JC19960720 - oxygen
These data were part of the Nordic Seas CARINA oxygen analyses.
The analyses showed that the data were too high and should be adjusted down by
the specified fraction. The details can be found in the Nordic Seas oxygen
report available at at http://carboocean.ifm-geomar.de/postings/list.
Are Olsen
Bergen, Norway, Aug 14 2008
Posted by are.olsen@uib.no on 2008-08-14 11:19:43 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021
74JC19960720 - salinity
Analysis of Nordic Seas salinity data indicated no offset for these data, see
also Nordic Sea salinity data report at
http://carboocean.ifm-geomar.de/postings/list
Are Olsen, Bergen, Norway, Aug 8 2008
Posted by are.olsen@uib.no on 2008-08-08 09:25:30 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021
74JC19960720 - alkalinity
Inversion of manual crossover results gave an offset of 15.4 umol/kg.
Regession analyses of deep values (using alk-sal relationships) gave offset of
16 umol kg.
A reasonable adjustment is 15.5 umol/kg, this also resulted in realistic
alkalinty profiles for this cruise
This is described in the Nordic Seas alkalinity summary document at
http://carboocean.ifm-geomar.de/postings/list
Below I have uploaded page with the inversion results and 74JC19960720 cruise
highlighted.
Are Olsen
Bergen, Norway, 2 July 2008.
Posted by are.olsen@uib.no on 2008-07-02 10:46:21 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021
74JC19960720 - tco2
Inversion analyses and profiles indicated that the data were OK. See Nordic Seas
tco2 summary document at http://carboocean.ifm-geomar.de/postings/list for
details. Figure below -taken from summary document - shows inversion from
autogenerated crossovers with TTO-NAS data and 74JC19960720 highlighted.
Are Olsen
Bergen, Norway, 2 Jul 2008
Posted by are.olsen@uib.no on 2008-07-02 10:38:30 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021
Hide comments