Samples were analyzed in triplicate, and average values shown in this dataset were only accepted if reproduced over at least two replicates; otherwise, the data was re-analyzed until a reproducible value was reached.

The standard Ocean Data View flags were used. A description of all flags is available on line at https://www.bodc.ac.uk/data/codes_and_formats/odv_format/. Flags used in this dataset are as follows:
1 = Good Value: Good quality data value that is not part of any identified malfunction and has been verified as consistent with real phenomena during the quality control process.
2 = Probably Good Value: Data value that is probably consistent with real phenomena but this is unconfirmed or data value forming part of a malfunction that is considered too small to affect the overall quality of the data object of which it is a part. (Used when only one replicate confirmed the reported value.)
3 = Probably Bad Value: Data value recognized as unusual during quality control that forms part of a feature that is probably inconsistent with real phenomena.
4 = Bad Value: An obviously erroneous data value.
6 = Value Below Detection Limit: The level of the measured phenomenon was too small to be quantified by the technique employed to measure it. The accompanying value is the detection limit for the technique or zero if that value is unknown.
9 = Missing Value: The data value is missing. Any accompanying value will be a magic number representing absent data. (All samples collected were analyzed. Any missing data was not collected.)

BCO-DMO made the following changes:
- Parameter names were modified to conform with BCO-DMO naming conventions.
- Blank cells and values of '-999' were replaced with 'nd' to indicate 'no data'.
- Added ISO_DateTime_UTC from original date and time fields.
- Corrected event number, date, and time of sample #6000.

Additional GEOTRACES Processing:
After the data were submitted to the International Data Management Office, BODC, the office noticed that important identifying information was missing in many datasets. With the agreement of BODC and the US GEOTRACES lead PIs, BCO-DMO added standard US GEOTRACES information, such as the US GEOTRACES event number, to each submitted dataset lacking this information. To accomplish this, BCO-DMO compiled a 'master' dataset composed of the following parameters: station_GEOTRC, cast_GEOTRC (bottle and pump data only), event_GEOTRC, sample_GEOTRC, sample_bottle_GEOTRC (bottle data only), bottle_GEOTRC (bottle data only), depth_GEOTRC_CTD (bottle data only), depth_GEOTRC_CTD_rounded (bottle data only), BTL_ISO_DateTime_UTC (bottle data only), and GeoFish_id (GeoFish data only). This added information will facilitate subsequent analysis and inter comparison of the datasets.

Bottle parameters in the master file were taken from the GT-C_Bottle_GT10, GT-C_Bottle_GT11, ODF_Bottle_GT10, and ODF_Bottle_GT11 datasets. Non-bottle parameters, including those from GeoFish tows, Aerosol sampling, and McLane Pumps, were taken from the Event_Log_GT10 and Event_Log_GT11 datasets. McLane pump cast numbers missing in event logs were taken from the Particulate Th-234 dataset submitted by Ken Buesseler.

A standardized BCO-DMO method (called "join") was then used to merge the missing parameters to each US GEOTRACES dataset, most often by matching on sample_GEOTRC or on some unique combination of other parameters.

If the master parameters were included in the original data file and the values did not differ from the master file, the original data columns were retained and the names of the parameters were changed from the PI-submitted names to the standardized master names. If there were differences between the PI-supplied parameter values and those in the master file, both columns were retained. If the original data submission included all of the master parameters, no additional columns were added, but parameter names were modified to match the naming conventions of the master file.

See the dataset parameters documentation for a description of which parameters were supplied by the PI and which were added via the join method.