University of Edinburgh, Department of Geology
Type of resources
Contact for the resource
The dataset contains physical, biological and chemical oceanographic measurements, and meteorological data. Hydrographic measurements include temperature, salinity, attenuance and backscatter, pH and dissolved oxygen concentrations, while water samples were analysed for concentrations of carbon, nitrogen, hydrocarbons, nutrients and pigments. Samples were also collected for phytoplankton and zooplankton analyses, while results from production experiments are also included in the data set. These oceanographic data are supplemented by surface meteorological measurements. Measurements were taken at sites in the Bellinghausen Sea as part of a 2-ship Eulerian experiment between the 28th of October and the 17th of December 1992. The data were collected via (i) underway sampling (SeaSoar Undulating Oceanographic Recorder (UOR), lightfish, hull-mounted acoustic Doppler current profiler (ADCP), meteorology and surface ocean parameters) of which there are 121179 records and (ii) discrete sampling (conductivity-temperature-depth (CTD) and expendable bathythermograph (XBT) casts, bottle stations, net hauls, productivity incubations) of which there are over 1000 deployments and experiments. The study aimed to measure the magnitude and variability of carbon and nitrogen fluxes during early summer in the Southern Ocean, with particular emphasis on rates and processes in the marginal ice zone. The data were collected and supplied by UK participants in the Joint Global Ocean Flux Study (JGOFS). The British Oceanographic Data Centre (BODC) are responsible for calibrating, processing, quality controlling and documenting the data and assembling the final data set. Underway data are stored as 1 minute interval time series for each cruise with all parameters merged on date/time. The data are fully quality controlled; checks were made for instrument malfunction, fouling, constancy, spikes, spurious values, calibration errors, baseline and salt-water corrections. The discrete data are stored in a relational database (Oracle RDBMS), chiefly as vertical profiles and are uniquely identified by a combination of deployment number and depth.