Cruise: 09FA19941112 (dataset:CARINA) Data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023 Predecessor: CARINA
Synonyms (including errata!) for this cruise: 09FA1094; 09FA19941112; 09FA1094; s5sv; S05
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:1
oxygen:1
phosphate:3
salinity:1
silicate:1
- no files! -
Filename: | Comment: | Action | |
---|---|---|---|
additive_SAL_Favourite.pdf | 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: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:25 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112/salinity: update slope+intercept
autogenerated: only BOTsal available (no CTDsal)
Posted by svheuven@gmail.com on 2014-12-18 16:52:44 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): : make -0.006 based on
eyeballing 400km plots
Posted by svheuven@gmail.com on 2014-06-16 15:50:32 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112 - salinity
SAL: 3 deep profiles, all terribly biased and offset from each other (spread
0.015 ppt). -0.006 appear to bring together somewhat, but consider scrapping
these data or even this whole cruise.
I generated some xovers figures for this cruise using a very wide search radius
(400km). This generates about 3 xovers for each parameter, all at 48ºS, roughly
halfway Perth and Antarctica, just north of SE Indian Ridge, where strongly
zonal homogeneity may be expected. These xovers show this cruise to have been
terribly INaccurate for all parameters except oxygen. I will here provide
'eyeball' estimates of adjustments (no inversions involved), to get the worst of
this fixed. A future version of GLODAP may consider 'zonal MLR style' offset
determination to pin this down more precisely.
Posted by svheuven@gmail.com on 2014-04-22 21:31:48 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112/salinity: init slope+intercept
autogenerated: using BOTsal (no CTDsal)
Posted by svheuven@gmail.com on 2014-02-25 17:02:15 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112 - salinity
No cross over found with any other cruise
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-08-27 20:32:28 UTC for data product: CARINA
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:25 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): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:32 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:32 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.00 based on
eyeballing 400km plots. NOTE THAT 1 STATION IS BIASED 10% HIGH QC1.
Posted by svheuven@gmail.com on 2014-06-16 15:50:32 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112 - phosphate
PO4: 3 deep profiles, one of which is severely biased (~+10%). The other two
appear accurate. Do not adjust these two, and remove that biased profile in QC1.
Or consider scrapping PO4 or even this whole cruise...
I generated some xovers figures for this cruise using a very wide search radius
(400km). This generates about 3 xovers for each parameter, all at 48ºS, roughly
halfway Perth and Antarctica, just north of SE Indian Ridge, where strongly
zonal homogeneity may be expected. These xovers show this cruise to have been
terribly INaccurate for all parameters except oxygen. I will here provide
'eyeball' estimates of adjustments (no inversions involved), to get the worst of
this fixed. A future version of GLODAP may consider 'zonal MLR style' offset
determination to pin this down more precisely.
Posted by svheuven@gmail.com on 2014-04-22 21:29:16 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112 - phosphate
No cross over found with any other cruise
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-08-27 20:43:53 UTC for data product: CARINA
Filename: | Comment: | Action | |
---|---|---|---|
multiplicative_NO3_Favourite.pdf | 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 0.93 based on
eyeballing 400km plots
Posted by svheuven@gmail.com on 2014-06-16 15:50:32 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112 - nitrate
NO3: -7%. 3 deep profiles, very large spread between them, suggests data is
worthless. Moreover, the error does not appear to be multiplicative but
additive: NO3vsPO4 plots do not converge but are parallel. Consider flagging
-777.
I generated some xovers figures for this cruise using a very wide search radius
(400km). This generates about 3 xovers for each parameter, all at 48ºS, roughly
halfway Perth and Antarctica, just north of SE Indian Ridge, where strongly
zonal homogeneity may be expected. These xovers show this cruise to have been
terribly INaccurate for all parameters except oxygen. I will here provide
'eyeball' estimates of adjustments (no inversions involved), to get the worst of
this fixed. A future version of GLODAP may consider 'zonal MLR style' offset
determination to pin this down more precisely.
Posted by svheuven@gmail.com on 2014-04-22 21:12:20 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112 - nitrate
No cross over found with any other cruise
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-08-27 20:43:32 UTC for data product: CARINA
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.00 based on
eyeballing 400km plots. NOTE THAT 1 STATION IS BIASED 10% HIGH QC1.
Posted by svheuven@gmail.com on 2014-06-16 15:50:32 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112 - phosphate
PO4: 3 deep profiles, one of which is severely biased (~+10%). The other two
appear accurate. Do not adjust these two, and remove that biased profile in QC1.
Or consider scrapping PO4 or even this whole cruise...
I generated some xovers figures for this cruise using a very wide search radius
(400km). This generates about 3 xovers for each parameter, all at 48ºS, roughly
halfway Perth and Antarctica, just north of SE Indian Ridge, where strongly
zonal homogeneity may be expected. These xovers show this cruise to have been
terribly INaccurate for all parameters except oxygen. I will here provide
'eyeball' estimates of adjustments (no inversions involved), to get the worst of
this fixed. A future version of GLODAP may consider 'zonal MLR style' offset
determination to pin this down more precisely.
Posted by svheuven@gmail.com on 2014-04-22 21:29:16 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112 - phosphate
No cross over found with any other cruise
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-08-27 20:43:53 UTC for data product: CARINA
Filename: | Comment: | Action | |
---|---|---|---|
multiplicative_SIL_Favourite.pdf | 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 0.96 based on
eyeballing 400km plots
Posted by svheuven@gmail.com on 2014-06-16 15:50:32 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112 - silicate
SIL: -4%. Only 3 profiles; data look precise although offset.
I generated some xovers figures for this cruise using a very wide search radius
(400km). This generates about 3 xovers for each parameter, all at 48ºS, roughly
halfway Perth and Antarctica, just north of SE Indian Ridge, where strongly
zonal homogeneity may be expected. These xovers show this cruise to have been
terribly INaccurate for all parameters except oxygen. I will here provide
'eyeball' estimates of adjustments (no inversions involved), to get the worst of
this fixed. A future version of GLODAP may consider 'zonal MLR style' offset
determination to pin this down more precisely.
Posted by svheuven@gmail.com on 2014-04-22 21:20:22 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112 - silicate
No cross over found with any other cruise
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-08-27 20:44:04 UTC for data product: CARINA
Filename: | Comment: | Action | |
---|---|---|---|
multiplicative_O2_Favourite.pdf | note that 09AR20041223 ("336" in plot) get adjusted -2.5% itself. |
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: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:25 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112/oxygen: update slope+intercept
autogenerated: only BOToxy available (no CTDoxy)
Posted by svheuven@gmail.com on 2014-12-18 16:52:44 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 based on
eyeballing 400km plots
Posted by svheuven@gmail.com on 2014-06-16 15:50:32 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112 - oxygen
O2: appears quite accurate. Do not adjust.
I generated some xovers figures for this cruise using a very wide search radius
(400km). This generates about 3 xovers for each parameter, all at 48ºS, roughly
halfway Perth and Antarctica, just north of SE Indian Ridge, where strongly
zonal homogeneity may be expected. These xovers show this cruise to have been
terribly INaccurate for all parameters except oxygen. I will here provide
'eyeball' estimates of adjustments (no inversions involved), to get the worst of
this fixed. A future version of GLODAP may consider 'zonal MLR style' offset
determination to pin this down more precisely.
Posted by svheuven@gmail.com on 2014-04-22 21:13:21 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112/oxygen: init slope+intercept
autogenerated: using BOToxy (no CTDoxy)
Posted by svheuven@gmail.com on 2014-02-25 17:02:15 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112 - oxygen
No cross over found with any other cruise
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-08-27 20:44:13 UTC for data product: CARINA
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:25 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View 24 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:25 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112/oxygen: update slope+intercept
autogenerated: only BOToxy available (no CTDoxy)
Posted by svheuven@gmail.com on 2014-12-18 16:52:44 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112/salinity: update slope+intercept
autogenerated: only BOTsal available (no CTDsal)
Posted by svheuven@gmail.com on 2014-12-18 16:52:44 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 based on
eyeballing 400km plots
Posted by svheuven@gmail.com on 2014-06-16 15:50:32 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 0.96 based on
eyeballing 400km plots
Posted by svheuven@gmail.com on 2014-06-16 15:50:32 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.00 based on
eyeballing 400km plots. NOTE THAT 1 STATION IS BIASED 10% HIGH QC1.
Posted by svheuven@gmail.com on 2014-06-16 15:50:32 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 0.93 based on
eyeballing 400km plots
Posted by svheuven@gmail.com on 2014-06-16 15:50:32 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:32 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): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:32 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): : make -0.006 based on
eyeballing 400km plots
Posted by svheuven@gmail.com on 2014-06-16 15:50:32 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112 - salinity
SAL: 3 deep profiles, all terribly biased and offset from each other (spread
0.015 ppt). -0.006 appear to bring together somewhat, but consider scrapping
these data or even this whole cruise.
I generated some xovers figures for this cruise using a very wide search radius
(400km). This generates about 3 xovers for each parameter, all at 48ºS, roughly
halfway Perth and Antarctica, just north of SE Indian Ridge, where strongly
zonal homogeneity may be expected. These xovers show this cruise to have been
terribly INaccurate for all parameters except oxygen. I will here provide
'eyeball' estimates of adjustments (no inversions involved), to get the worst of
this fixed. A future version of GLODAP may consider 'zonal MLR style' offset
determination to pin this down more precisely.
Posted by svheuven@gmail.com on 2014-04-22 21:31:48 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112 - phosphate
PO4: 3 deep profiles, one of which is severely biased (~+10%). The other two
appear accurate. Do not adjust these two, and remove that biased profile in QC1.
Or consider scrapping PO4 or even this whole cruise...
I generated some xovers figures for this cruise using a very wide search radius
(400km). This generates about 3 xovers for each parameter, all at 48ºS, roughly
halfway Perth and Antarctica, just north of SE Indian Ridge, where strongly
zonal homogeneity may be expected. These xovers show this cruise to have been
terribly INaccurate for all parameters except oxygen. I will here provide
'eyeball' estimates of adjustments (no inversions involved), to get the worst of
this fixed. A future version of GLODAP may consider 'zonal MLR style' offset
determination to pin this down more precisely.
Posted by svheuven@gmail.com on 2014-04-22 21:29:16 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112 - silicate
SIL: -4%. Only 3 profiles; data look precise although offset.
I generated some xovers figures for this cruise using a very wide search radius
(400km). This generates about 3 xovers for each parameter, all at 48ºS, roughly
halfway Perth and Antarctica, just north of SE Indian Ridge, where strongly
zonal homogeneity may be expected. These xovers show this cruise to have been
terribly INaccurate for all parameters except oxygen. I will here provide
'eyeball' estimates of adjustments (no inversions involved), to get the worst of
this fixed. A future version of GLODAP may consider 'zonal MLR style' offset
determination to pin this down more precisely.
Posted by svheuven@gmail.com on 2014-04-22 21:20:22 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112 - oxygen
O2: appears quite accurate. Do not adjust.
I generated some xovers figures for this cruise using a very wide search radius
(400km). This generates about 3 xovers for each parameter, all at 48ºS, roughly
halfway Perth and Antarctica, just north of SE Indian Ridge, where strongly
zonal homogeneity may be expected. These xovers show this cruise to have been
terribly INaccurate for all parameters except oxygen. I will here provide
'eyeball' estimates of adjustments (no inversions involved), to get the worst of
this fixed. A future version of GLODAP may consider 'zonal MLR style' offset
determination to pin this down more precisely.
Posted by svheuven@gmail.com on 2014-04-22 21:13:21 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112 - nitrate
NO3: -7%. 3 deep profiles, very large spread between them, suggests data is
worthless. Moreover, the error does not appear to be multiplicative but
additive: NO3vsPO4 plots do not converge but are parallel. Consider flagging
-777.
I generated some xovers figures for this cruise using a very wide search radius
(400km). This generates about 3 xovers for each parameter, all at 48ºS, roughly
halfway Perth and Antarctica, just north of SE Indian Ridge, where strongly
zonal homogeneity may be expected. These xovers show this cruise to have been
terribly INaccurate for all parameters except oxygen. I will here provide
'eyeball' estimates of adjustments (no inversions involved), to get the worst of
this fixed. A future version of GLODAP may consider 'zonal MLR style' offset
determination to pin this down more precisely.
Posted by svheuven@gmail.com on 2014-04-22 21:12:20 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
General comment.
I generated some xovers figures for this cruise using a very wide search radius
(400km). This generates about 3 xovers for each parameter, all at 48ºS, roughly
halfway Perth and Antarctica, just north of SE Indian Ridge, where strongly
zonal homogeneity may be expected. These xovers show this cruise to have been
terribly INaccurate for all parameters except oxygen. I will here provide
'eyeball' estimates of adjustments (no inversions involved), to get the worst of
this fixed. A future version of GLODAP may consider 'zonal MLR style' offset
determination to pin this down more precisely.
Posted by svheuven@gmail.com on 2014-04-22 21:08:28 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112/oxygen: init slope+intercept
autogenerated: using BOToxy (no CTDoxy)
Posted by svheuven@gmail.com on 2014-02-25 17:02:15 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112/salinity: init slope+intercept
autogenerated: using BOTsal (no CTDsal)
Posted by svheuven@gmail.com on 2014-02-25 17:02:15 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
No subject
This cruise don't have any crossovers in either GLODAP nor CARINA.
No suggestions for adjustments possible at this stage.
Posted by ttanhua@geomar.de on 2012-07-17 16:38:33 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
09FA19941112 - oxygen
No cross over found with any other cruise
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-08-27 20:44:13 UTC for data product: CARINA
09FA19941112 - silicate
No cross over found with any other cruise
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-08-27 20:44:04 UTC for data product: CARINA
09FA19941112 - phosphate
No cross over found with any other cruise
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-08-27 20:43:53 UTC for data product: CARINA
09FA19941112 - nitrate
No cross over found with any other cruise
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-08-27 20:43:32 UTC for data product: CARINA
09FA19941112 - salinity
No cross over found with any other cruise
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-08-27 20:32:28 UTC for data product: CARINA
Hide comments