Files in the Dataset have been checked for format consistency, and merged into a single, integrated, downloadable file.
Download Entire Dataset Submit Data For This Cruise How to Cite DatasetFiles listed here are the most recent version submitted by the cruise scientists, but have not yet been checked for consistency and merged into the main Dataset. They are provided "as is". If you are unsure of which files to use, stick to the Dataset files above.
These files are not yet in the Dataset.
| Filename (Download) | Size | Date Submitted |
| 325019931005.exc.csv | 1.1 MB | 2014-05-21 |
CCHDO-1.0 CF netCDF files converted from bottle exchange file
CCHDO-1.0 CF netCDF files converted from ctd exchange file
File was created on or before this date
File was created on or before this date
File was created on or before this date
File was created on or before this date
File was created on or before this date
File was created on or before this date
File was created on or before this date
File was created on or before this date
File was created on or before this date
File was created on or before this date
File was created on or before this date
File was created on or before this date
Bottle file, all of the alk values for stations 77 and 86 have been re-flagged 3.
Expocode: 3250TN026_1 Ship: THOMAS G. THOMPSON Woce Line: P10 Note: Replace bottle file. see email from Bob on 2014-05-21: CCHDO and Alex, As part of the 2nd QC for v2 (crossover and inversion, independently) we discovered 2 anomalous alk stations (77 & 86) from WOCE P10. The plot below illustrates the issue. Plots against other parameters show the same thing. I have been in contact with Chris Sabine, the alk PI for this cruise. I have examined all the records and can find no specific reason to explain the problem, however the magnitiude is such that we agree that the alk for these 2 stations should be flagged 3. In addition to being strange relative to other values from this cruise, these data are also anomalous relative to the 2005 Japanese reoccupation of this line. While I did not check all combinations, the several that I did check showed no corroborating signal among other parameters (i.e. as one might expect from a front or similar feature). Consequently, I attach a new exchange format copy of the SV data file for this cruise. In this file all of the alk values for stations 77 and 86 have been re-flagged 3. I made a note of the change in the header metadata. best, bob
The following files are now available online under 'Files as received', unprocessed by the CCHDO.
325019931005.exc.csv
As part of the 2nd QC for v2 (crossover and inversion, independently) we discovered 2 anomalous alk stations (77 & 86) from WOCE P10. The plot below illustrates the issue. Plots against other parameters show the same thing. I have been in contact with Chris Sabine, the alk PI for this cruise.
I have examined all the records and can find no specific reason to explain the problem, however the magnitiude is such that we agree that the alk for these 2 stations should be flagged 3. In addition to being strange relative to other values from this cruise, these data are also anomalous relative to the 2005 Japanese reoccupation of this line. While I did not check all combinations, the several that I did check showed no corroborating signal among other parameters (i.e. as one might expect from a front or similar feature).
Consequently, I attach a new exchange format copy of the SV data file for this cruise. In this file all of the alk values for stations 77 and 86 have been re-flagged 3. I made a note of the change in the header metadata.
Replaced DELC13 decimal-1-data with decimal-2-data from same original data files. Notes file sent to Jerry with details.
Notes on P10 Feb. 20, 2003 D. Muus
1. Replaced 1-decimal-place DELC13 in P10hy.txt (20020619WHPOSIOSA)
with 2-decimal-place DELC13 from:
/usr/export/html-public/data/onetime/pacific/p10/original/
2001.01.30.P10_C13_DSTUART.DIR/p10_c13.data
2. The 5 extra DELC13 values described in the 2002/05/01 merge notes
appear to belong to Station 74 Cast 1 (Gerard barrel cast)
rather than Cast 3 rosette.
3. Made new exchange file for Bottle data.
4. Checked new bottle file with Java Ocean Atlas.
Changed the Q1 and Q2 flags for the SILCST at sta. 22, bottles 30, 29. and 28 to 3 re Lynne Talley's e-mail. Created new exchange file.
DELC13 merged into bottle file and put on line together with new exchange file.
Notes on P10 merging Apr 30, 2002 D.Muus
1. Merged DELC13 from:
/usr/export/html-public/data/onetime/pacific/p10/original/2001.01.30.P10_C13_DSTUART.DIR/p10_c13.data
into bottle file (20010828WHPOSIODM)
2. Only sample reference in p10_c13.data is station, cast and niskin. Assume "niskin" refers to SAMPNO rather than last 2 digits of BTLNBR. CFC and Helium/Tritium merging last year had same problem but contained pressures to confirm "bottle" in data file was same as SAMPNO in bottle file.
3. Following "niskin" numbers in p10_c13.data not in web bottle file as either SAMPNO or last 2 digits of BTLNBR.
Sta 74 Ca 3 niskin 81
74 3 82
74 3 88
74 3 92
74 3 94
4. Made new exchange file for Bottle data.
5. Checked new bottle file with Java Ocean Atlas.
created .ps files, check with gs viewer. Created *check.txt file.
CTD has been converted to exchange using the new code and put online.
New documentation for this cruise has been put online. Old documentation was moved to original directory.
I have replaced the current P10 bottle file with a file containing updated CFC 11 and 12 values as well as merged helium, delhe3, tritium, and neon data. Data merged by D. Muus. According to Jenkins (by way of J. Swift) all tracer data may be made public, and therefore the entire bottle file has been made publicly available in WOCE and Exchange format. Old files have been moved to original subdirectory and have been renamed to reflect replacement. All tables and references have been updated to reflect this change.
below please find additional (ie replacement) notes regarding the merging of P10 updated CFC's (there was a problem with flags after first merging) and newly merged helium, tritium, delhe3, and neon (with error values). New files are already online and all data is public.
-------------------------------------------------------------------
Notes on P10 CFC and Helium, Tritium and Neon merging Aug 28, 2001. D. Muus
1. New CFC-11 and CFC-12 from: /usr/export/html-public/data/onetime/pacific/p10/original/
20010709_CFC_WISEGARVER_P10/20010709.172120_WISEGARVER_P10_p10_CFC_DQE.dat merged into plain text web SEA file as of Aug 20, 2001 (20000414WHPOSIODMB)
2. New HELIUM, DELHE3, NEON, and TRITUM from: /usr/export/html-public/data/onetime/pacific/p10/original/
2000.11.13_TRIT_HE_REFORMAT_P10_SA
merged into plain-text SEA file after CFCs merged (Item 1 above). Encrypted web Sea file (20000328WHPOSIODMB) has 60 more bottles with helium data than the new helium file and a net of 7 more tritium levels than the new tritium file.
a. New files have no SAMPNO but BTLNBR appears to be same as SAMPNO in original SEA file while BTLNBR in original SEA file differs from new helium,tritium, neon files BTLNBR (e.g. Sta 1, Cast 1, 8.4db: "WG009" in Sea file, "9" in new file). Matched SAMPNO in SEA file with BTLNBR in new files for this merge. Used original SEA file SAMPNOs and BTLNBRs. No quality codes from data originator so used "2"s used for both QUALT1 and QUALT2.
b. New files have Cast 2 for Stations 16, 56, 74 and 90. SUMMARY file and web SEA file have Station 16 Cast 3(ROS) (Cast 2 is BUC)
56 3(ROS) (No tritium, Cast 2 is LVS)
74 3(ROS) (No tritium, Cast 2 is BUC)
90 1(ROS) (No Cast 2)
Changed new files to match SUMMARY and SEA file data for ROS.
4. Exchange files made for both the Public and Non-Public versions and checked using Java Ocean Atlas.
Steve - Please make the following changes from non-public to public. All Jenkins Pacific/Indian data are public according to an email he sent 2/26/2001, hence P10 3250TN026_1 The He/Tr data are not in the public data file. Please make them public and available.
Although Dave Muus has merged updated CFC's into the current P10 bottle file there was a small flag missmatch in the public version of the data. Because helium and tritium still need merging into this file, this will be done and the final merged bottle file (also with corrected flags) will then be put online.
So for now no updated CFC's will be online until the helium and tritium is merged.
Notes on P10 CFC merging Aug 21, 2001. D. Muus
1. New CFC-11 and CFC-12 from: /usr/export/html-public/data/onetime/pacific/p10/original/ 20010709_CFC_WISEGARVER_P10/20010709.172120_WISEGARVER_P10_p10_CFC_DQE.dat merged into plain text web SEA file as of Aug 20, 2001 (20000414WHPOSIODMB) and into encrypted web SEA file as of Aug 20, 2001 (20000328WHPOSIODMB)
2. Changed header "SIGTRI" to "TRITER". Header in Jenkins tritium data file was "ErrTritium".
3. Exchange file made for the plain test version and checked using Java Ocean Atlas.
Files put online by K. Uribe. p10_3250TN026_1.txt (replaces the txt file currently online), p10_3250TN026_1.pdf.bin
CTD and Bottle files in exchange format have been put online.
JENKINS received Oct 17 and NOV1, 2000. NP per table and data history. Not on plain text web file: 20000414WHPOSIODMB but encrypted file exists. Public per Jenkins referenced message above.
It was brought to my attention that the WOCE Pacific/Indian He-Tr data was not as yet made public. After submitting it to you last year, I had intended on going through it one more time to ensure there were no problems with it. Unfortunately, I have not had the time to do this. Is it possible, therefore, to release it as public data, and if there are any subsequent minor revisions, to make changes? I suspect there might be a few samples in the set that might have got through our initial quality control.
Enclosed are three text files (and data) for the Pacific. The headers are:
Lab ID
WHPID
Station
Cast
Niskin
Del-C13
C13 flag
The files are for P10, P14C, P17E, and P17E/P19S
includes cfc report, nutrients report, ctd & hyd dqe reports and large- and small-volume c14 reports.
2000.12.11 KJU
File contained here is a CRUISE SUMMARY and NOT sumfile. Documentation is online.
2000.10.11 KJU
Files were found in incoming directory under whp_reports. This directory was zipped, files were separated and placed under proper cruise. All of them are sum files.
Received 1997 August 15th.
I have put the Jenkins tritium data into WOCE format. There were no quality codes so I set the TRITUM to 2.
I have put the Jenkins helium and neon in WOCE format. There were no quality codes so I set the HELIUM, DELHE3, and NEON to 2.
WHPO,
The following data were received from Bill Jenkins 2000/11/01: and were reformatted by Sarilee Anderson.
P10: tr/he/ne
P13: tr
P14C:tr
P18: tr/he/ne
P19: tr/he/ne
P21: tr/he/ne
SAVE: S. Atlantic tritium data from SAVE program
*Files for Helium and Neon Data:
WOCE Indian Ocean = WIHe.dat Contains all legs
WOCE Pacific P10 = WP10He.dat
WOCE Pacific P18 = WP18He.dat
WOCE Pacific P19 = WP19He.dat
WOCE Pacific P21 = WP21He.dat
*Column Layout as follows:
Station, Cast, Bottle, Pressure, Delta3He, ErrDelta3He, ConcHelium, ErrConcHelium, ConcNeon, ErrConcNeon
*Units as follows:
Delta3He and ErrDelta3He in %
ConcHelium, ErrConcHelium, ConcNeon, and ErrConcNeon in nmol/kg
*Null values (for ConcNeon and ErrConcNeon only ) = -9.000
*All data are unfortunately still preliminary until we have completed the laboratory intercomparision and intercalibration that is still underway.
*Files for Tritium Data:
WOCE Indian Ocean = WITrit.dat Contains all legs
WOCE Pacific P10 = WP10Trit.dat
WOCE Pacific P13 = WP13Trit.dat
WOCE Pacific P14c = WP14cTrit.dat
WOCE Pacific P18 = WP18Trit.dat
WOCE Pacific P19 = WP19Trit.dat
WOCE Pacific P21 = WP21Trit.dat
SAVE South Atlnt = SAVETrit.dat
*Column Layout as follows: Station, Cast, Bottle, Pressure, Tritium, ErrTritium
*Units as follows: Tritium and ErrTritium in T.U.
*All data are unfortunately still preliminary until we have completed the laboratory intercomparision and intercalibration that is still underway.
Added Large Volume Samples file to website.
My apologies for the silence, but I have been rather busy as of late with adminstrative duties, and have been unable to work with or access the WOCE data with in any convenient format. Based on the information you gave me, I offer the following comments:
I regret that the format I sent you was not entirely consistent with the WOCE convention, but my understanding at the time was that this was not a formal submission, but rather a quick response to a personal request by Lynne to look at the data. I have not had the time to work through the data into the final format, as this was to be part of the currently active WOCE-AIMS data mop-up program for tritium-helium. I had hoped that prior to official/final transmission, we could have an opportunity to complete inter-lab comparisons and final data quality control.
For the tritium data, -99.00 means no sample, or that the sample analysis failed (e.g., sometimes storage flasks leaked, invalidating the measurement). For helium data, -9.90in the del-3He column means a null value (it's actually -99.00 per mil, but expressed in percent). The corresponding helium concentration value (which for some reason is a negative, but irrelevant number) will be invalid. The reason why the number appears like this is a minor bug in the reporting programme, and should be ignored.
No flags were reported for the data at present for the reasons described above.
hope this helps, bill
PS: I'm hoping to put together the Pacific tirtium-helium data submission sometime in the next few months, once we get through this year's graduate admissions process and a couple of other deadlines.
SMALL ERROR I know there is a non-WOCE header for P10 TR data, but I haven't yet heard anything from Jenkins on changing it. I cc'd you on a correspondence regarding that problem (and others) since they should be in the information about P10 that is available to users.
As of 3/2000 the 2 year clock expired on the last of the Pacific Ocean C14 data (P10). All Pacific Ocean WOCE C-14 data should be made public.
I have remerged the helium and tritium values sent by Jenkins into the p10 bottle file. The file now contains: TRITUM, HELIUM, DELHE3, and SIGTRI (which I think should be TRITER but is left as is until word from the PI). There were some questions regarding missing data values for HELIUM, and the PI was notified, however no response has come yet. Data were merged AS-IS.
On line bottle file has been replaced and the table has been edited to reflect this change.
It was discovered by L.Talley that the current version of p10 bottle file on line, has incorrect helium and tritium data merged into it. Therefore the original helium/tritium data sent by Jenkins, was re-merged into the current bottle file. Please see file README.p10 regarding first merging of these data and documentation.
NOTES on merging:
- Used DMN code mrgsea to merge TRITUM, HELIUM, DELHE3, SIGTRI (which possibly should be TRITER)
- changed missing data value for TRITUM from -99.00 to -9.0
- changed missing data value for SIGTRI from -99.00 to -9.0
- changed missing data value for DELHE3 from -9.90 to -999.00
- added missing data value for HELIUM -9.0.
- changed HELIUM units from PMOL/KG to NMOL/KG.
- ran wocecvt with no bottle file errors.
- ran read_hyd. Code did not recognize SIGTRI as WOCE accepted parameter. no other errors detected.
- ran maskhyd to add date/name stamp. Code stopped after not recognizing SIGTRI as WOCE parameter.
- added date/name stamp by hand edit.
- ran movehyd to put parameter columns in WOCE order.
- Final file is called p10_complete_20000328.txt
PROBLEMS:
** Erroneous HELIUM values -4.417 correspond to DELHE3 values of -9.90 and may be the intended missing data value. These values are out of the accepted range for HELIUM in the WOCE Operations Manual 90-1. These values were merged and left as-is until further word from PI.
** Precision for HELIUM varied from f8.1 to f8.3. WOCE Operations Manual 90-1 states precision for HELIUM should be f8.4. Therefore precision was "added" to these values when merged into the current bottle file.
** SIGTRI is not a recognized WOCE parameter and possibly should be TRITER but no course of action had been given by PI. Parameter was merged as is until further word from PI.
** See email below. This was the second contact for this PI regarding these data problems.
Hello Dr. Jenkins,
Lynne Talley recently caught an error in the helium/tritium data that was merged into the P10 bottle file, which caused me to delve back into the original data you sent a year or so ago. The error Lynne caught was a result of the merging process, however I cannot seem to find a response from you on the following problems/questions we had regarding the data.
Can you please look through the original emails (attached) and reply with a course of action to be taken on these data. Also at this time, may we make the helium and tritium data public?
2000.03.07 DMB:
Merged CFC11/12 values from Mark Warner (email below). Used "driver.pl" and "warner.pl" to reformat data in order to merge.
Used D. Newton's "mrgsea" for merging both values into existing P10 bottle file obtained from WHPO website.
Ran wocecvt on merged bottle file. No errors. Ran maskhyd to include date/name stamp. Also made a public version with he/tr and C14 masked out of file (named p10hy.txt).
Renamed merged bottle file p10hy_all_params encrypted it and moved old file to 'original' subdirectory with replacement date in filename.
Since John Bullister has asked us all to check our data, I have resubmitted the WOCE P10 CFC data to the ftp site. I have changed it to the SIO1993 calibration scale, and flagged one or two questionable points.
TCARBN: merged new values into existing column. Changed missing data value from -999.9 in latest co2 data set to -9.0 in current bottle file.
ALKALI: merged new values into existing column. Changed missing data value from -999.9 in latest co2 data set to -9.0 in current bottle file.
C14ERR: added new column for these values into existing column. Changed missing data value in latest co2 data set from -999.9 to -9.0 in current bottle file.
Ran maskhyd to add name/date stamp. Ran wocecvt to check format. Both programs ran with no errors detected in routine formatting.
New file has been placed in p10 directory, and table has been updated to reflect the change.
This information has been added as a readme file to the original p10 directory.
I understand the problem. Some days I'm not sure what ocean I'm working on. P10LV files are attached, including the Final Report (pdf). A few additional notes regarding this data set follow. Some of these comments are generic to my LV file procedure (i.e. treatment of missing bottom
depth in SUM file), but most are specific to p10
1. cast numbers. Some confusion existed here because after the cruise Terry and staff changed cast numbers on stations which had a Ra-228 surface soak. This messed up shore based
measurements since the sample collection deck logs no longer matched the SUM file. The attached file P10LVSUM.ASC is a copy of the SUM file produced by WHOI whenever. The file p10lvsta is my reduction of that file with corrections to what I think things should be.
2. In p10lvsta, I have filled in any missing bottom depths.
3. The locations (BE,BO,EN) are better taken from P10LVSUM.ASC than from p10lvsta since I only keep one location (almost always BO).
4. The data file has a flag (tf) for the reversing temperature values
5. Some values in the data file have a flag value of "0" intentionally, by agreement between Jim Swift and me. This indicates that the value was somehow approximated. Oxygen was never measured for the LV casts. Here I interpolated oxygen based on the measured rosette values at the same station. Missing temperature and salinity values were interpolated from surrounding LV cast samples on the same station.
6. I provided all QC flags. QC values are burst into individual flag values with names that are easily recognized (i.e. sif=silicate flag, sf=salt flag). Marking is according to WOCE convention. QC performed relative to this cruise only (i.e. no comparison to other cruises). Gerard barrel QC on nutrients not as strict as Rosette samples. Note however that the salts values (especially deep) for the first half of this cruise are better than the measured Rosette salt values due to "lazy" collection technique by a graduate student on the Rosette salts (should be a comment in the Ch. Sci. Rpt. about this, but I wouldn't bet on it - Mandy was in way over her head on this one).
7. Depths estimated from latitude and pressure using the algorithm published anon. in the 1970 Bulletin Geodesique.
8. Number of decimal places. There should be the required number or more for all variables, however, my software truncates trailing "0's" on print.
7. Nutrient data received in umol/l; converted with lab temperature of 25C and measured salinity.
8. AOU values calculated using the Weiss algorithm rather than the
Garcia algorithm. I now prefer the latter, but you should probably just dump these and recalculate using your programs to be sure of consistancy. Ditto on theta and sigmaX.
This is probably more than you wanted to know. Rather than me sending you a giant data dump, I suggest that we deal with the LV cruises one at a time so that the exceptions get properly noted for the final archive.
I have all LV data that exists from U.S. WOCE Pacific.
Converted the file from Bob Key to the WHP .lvs format.
Parameters that were in the original file but were not retained in the .lvs file because they are not in the .lvs record format description:
latitude
longitude
depth (m)
nitrate
nitrite
phosphate
silicate
AOU
sigma 0
sigma 1
sigma 2
sigma 3
sigma 4
QUALT1 flags for:
temperature
nitrate
nitrite
phosphate
silicate
aou
The Key file had station numbers 1-13, but the .sum file indicated that the LVS stations were 16, 25, 34, 47, 56, 65, and 74. In addition the the cast numbers in the Key file were always 1 and 3, which did not agree with the .sum file. After comparing the maximum pressure in the .sum file with the maximum pressure in the Key file for each cast, I was able to determine which station and cast numbers to use.
There is a 0 flag for some of the parameters, in fact all of the oxygens except where there was no sample which is flagged 9. This is not a valid number for the quality flags. I left them as 0 since I have no way of knowing what they should be.
I have replaced both the public (he/tr, Tcarb, Alk, and DELC14 masked out of the file) and nonpublic (encrypted) bottle files with the newly formatted version from George Anderson. The new files have correct Q2 bytes in the QUALT2 column now. Old version had all 1's in the Q2 word. I have updated the table to reflect the date of the update.
I have provided hyd files for all these cruises, QC'ed by me, albeit not in WOCE format. I can resend if needed. Other than format, the only strange thing about these files was that I supplied a flag for revtmp, which I think appropriate given the number of things that can go wrong. Lynne may have these files reformatted since she has been using the results in the atlas prep.
In regards to my previous email on the questions surrounding helium and tritium data for p10 I'd like to add another.
Further inspection of the data with Steve Diggs revealed some values that may be questionable. Steve suggested I ask you about these as well.
The tritium and sigma tritium data use -99.00 as missing values, however the same does not appear to be true for the helium and delta helium3 values. There is a value of -9.90 that appears in the delta helium3 column which corresponds to a helium value of -4.417 consistantly. To my (very limitted) knowledge the range of helium values is somewhere between 1-3 nmol/kg. Is -4.417 a valid value for helium or is this an artifact of a calculation? Could you briefly explain what parameters comprise the ratio of delta helium3?
Also, there are some values in the helium column that have a different precisions. For example, is 1.7 appears as a helium value in the same station as 1.860. Is 1.7 actually 1.700? The WOCE format standards for helium are 8.4 which means precision will be 'added' to these values. If you have carried out measurements to this precision, do you wish to resend values for helium? The WOCE formats will also force the tritium (and sigma tritium) values to a precision of 8.2. These values will be rounded.
Thanks very much for your time concerning this data! A sample station (that has values in question) follows below.
Sincerely, Danie Bartolacci
90 15 34.93 141.21 8 11 93
224 49 20.336 34.511 216. -99.00 -99.00 0.48 1.7
223 98 17.474 34.642 187. 1.441 0.010 4.28 1.757
221 197 12.735 34.476 168. 1.558 0.011 9.48 1.797
220 246 10.899 34.391 156. 1.238 0.009 11.42 1.803
218 345 8.834 34.305 139. 1.199 0.010 13.59 1.810
217 396 7.652 34.271 127. 1.053 0.009 14.34 1.817
216 496 5.459 34.247 91. 0.607 0.007 15.82 1.839
215 597 4.411 34.320 73. 0.349 0.005 16.51 1.849
214 697 3.684 34.328 55. 0.218 0.004 16.35 1.860
213 796 3.433 34.367 55. -99.00 -99.00 16.85 1.9
212 897 3.112 34.395 54. 0.117 0.003 -9.90 -4.417
I would like to thank you for the submission of helium and tritium data for p10, and ask you a few questions about the data.
The data sent had no WOCE quality flags associated with them. Upon merging, data are designated a flags solely on the basis of being present or missing from the data set (i.e. if a value was present, it was considered an acceptable measurement and designated a flag of 2, if a missing value was present [-99.00] it was understood that no sample was drawn from the bottle and was designated a flag of 9). However, if you wish to send flags that further describe the quality of the data they would be most welcome! Definitions of the WOCE quality flags can be found in the WOCE Operations Manual, which is also on line at http://whpo.ucsd.edu/ under WHP Manuals (chapter 4).
Along with Tritium was a parameter named Sigma Tritium which was defined as the uncertainty in the Tritium measurement. Can we assume this parameter to be equivalent to the WOCE parameter Tritium Error?
If the quality flags we designated are acceptable, please notify us and we will continue with the merging process. Thank you for your time!
__________________________________________
According to email sent by Lynne Talley, the incorrect units on HELIUM were changed from PMOL/KG to NMOL/KG. See email below.
B. Jenkins was notified via email and phone regarding these data descrepancies. No word from the PI on a course of action. See email below.
I've updated the p10 doc file, and changed the table accordingly.
-- Danie
In regard to the "P10 - Nitrate" note Lou sent to you the other day - the data listed under the "NITRATE" column is in fact the total of "Nitrate AND Nitrite" or N+N. You are correct in stating that to obtain NITRATE only, you must subract out the corresponding NITRITE value. Again, the units of umol/Kg are correct for all nutrients.
To clarify, I obtained the P10 data (p10hy.txt) from the WOCE website that your PACIFIC data listing website linked - http://whpo.ucsd.edu/data/onetime/pacific/p10/index.htm.
I just found an error in the p10su.txt file, on line
231, where cast 4 (LVS) was mislabelled as station 66, and should
have been 65. I corrected it and put the corrected file in my
ftp site on whpo.ucsd.edu.
Yes they can be public.
-Mark
Attached is a listing of the preliminary data (we have a proposal into NSF to do a synthesis to finalize the data).
S.Diggs noted problems merging this data w/ BTL file.
As data originators of the TCO2 and alkalinity data for P10, we consider it to be public. It only becomes "officially" public after CDIAC has issued its final report
For now, P10 C14 is still proprietary except to WOCE PIs.
I have put the final CO2-related data file for the Pacific Ocean
WOCE Section P10 to the WHPO ftp INCOMING area.
Today I uploaded the P10 small volume data and final report to your anon ftp site. I send the final report in three formats: P10.ps (postscript version with figures), P10.txt (ascii with no figs), P10.rtf (rich text format). proprietary till March, 2000.