The Lowered Acoustic Doppler Current Profiler (LADCP) data were acquired while the Conductivity Temperature Depth (CTD) sensor was in the water during the Australian 2006 V3 BROKE-west survey. Data Acquisition: The LADCP is mounted on the CTD frame and is lowered through the water column from surface to bottom on each CTD cast. During the cast upward and downward facing sensor heads ensonify the water column with four beams per head, collecting the data necessary to calculate the vertical velocity of the LADCP on the CTD frame, as well as the northward and eastward components of the current relative to the LADCP for the entire water column. Once the LADCP has been retrieved, the data collected in the cast are downloaded to a PC as two raw binary .adp files, one for the upward looking head and one for the downward. This occurs for each CTD cast. The only modification to a normal CTD cast procedure for the LADCP is a 5 minute pause within 50 m of the sea floor on the upcast. This gives the downward sensor time to gather enough data for later determination of relative bottom velocity. The shipboard ADCP is a continuous recording device that operates over the duration of the voyage, ensonifying the water column once a second. It operates in a similar way to the LADCP, except that as it is fixed to the ship, it has only a range of approximately 250m deep. The ADCP data are necessary for final LADCP data processing. Similarly shipboard 10 seconds GPS records and CTD pressure data for the period of each cast is required for LADCP data processing. Data Processing: Once collected the upward and downward raw .adp LADCP files are subjected to fairly extensive processing using software written for the Matlab package, to produce the usable .mat data files given by this dataset. This software, written by Sergeui Sokolov (sergeui.sokolov AT csiro.au), and slightly modified for the 2005/06 V3 BROKE-west voyage by Andrew Meijers and Andreas Klocker combines the raw .adp files with the shipboard ADCP data, 10 second ship GPS data and CTD profile data. While the raw LADCP .adp files can be processed alone with minimal CTD data (date, start time, end time, start and end lat and long and max depth), they will only give current velocities relative to the CTDs frames motion. To gain an absolute profile the software identifies bottom and surface reflections, and uses this and ship ADCP and GPS data as boundary conditions for an integration of the velocity shear in the raw .adp files. The end result of processing is velocity in north and south components for each depth over the CTD cast. For more details refer to the above reference (Wijffels, et. al. 2005). Dataset format: The processed LADCP file (AU0603_LADCP_3_to_120.mat) is given in matlab .mat format, and before future processing with properly calibrated ADCP data, should be regarded as preliminary only. All CTD casts for BROKE-West are included, except for casts 1,2 and 119, where the LADCP was not used in the CTD cast. Casts 1 and 2 are not in the dataset, while 119 is represented by NaN (not a number) values. The absence of casts 1 and 2 from the data mean that care should be taken in attributing the data to the correct cast. Column one in each velocity matrix represents cast 3, not 1, and column 2 is cast 4 and so on up to column 118 representing CTD cast 120. On several casts the ADCP data were not available, meaning only part of the LADCP processing could be completed. This occurred for casts 5, 46, 91, 92, and 96, and data given here are unreferenced to a bottom velocity or ship track. Other errors occurred that meant that casts 68 and 115 could not be processed at all, and so data for these casts are represented by NaN values. Casts not present in dataset: 1,2 Casts represented by NaN values: 68,115 and 119 LADCP data created without ADCP input on casts: 5,46,91,92,96 (warning unconstrained values) The matlab variables contained in the file are: bindep: 20 depth levels in meters at which velocity data occurs for each profile. Each row of matrix represents a depth level, each column a CTD cast, ascending from cast 3 to 120. date: Start date of each cast (UT) (year month day) lat: Start latitude of each cast (decimal degrees) lon: Start longitude of each cast (decimal degrees) stationno: Last 3 digits gives the CTD cast number time: Start time of CTD cast (UT) of each cast (hours min sec) u_down: u (eastward) component of velocity in ms-1 for each bindepth and CTD cast, using only downward looking head data u_final: As for u_down but using data from both heads. This is the best estimate of velocity. u_up: As for u_down, but upward looking head data only. v_down: As for u_down, but northward component of velocity v_final: As for u_final, but northward component of velocity v_up: As for u_up, but northward component of velocity zbottom: Bottom depth in meters for each cast (m) Acronyms used: LADCP: Lowered Acoustic Doppler Current Profiler ADCP: Acoustic Doppler Current Profiler CTD: Conductivity Temperature Depth IASOS: Institute of Antarctic and Southern Ocean Studies CSIRO: Commonwealth Scientific and Industrial Research Organisation This work was completed as part of ASAC projects 2655 and 2679 (ASAC_2655, ASAC_2679).

The Acoustic Doppler Current Profiler (ADCP) data were acquired constantly over the duration of the Australian 2006 V3 BROKE-West survey. Data presented here are the results of 1/2 hour integrations of the cruise data from the start of the voyage in Fremantle, Australia, to the start of the return leg just north of Australia's Davis Station in Antarctica (-66.56S, 77.98E). North and eastward components of the current velocity are given for depths up to 300m below the surface along the ship track. Data Acquisition: The shipboard ADCP is a continuous broadband recording device that operates over the duration of the voyage, ensonifying the water column once a second. As the instrument is fixed to the ship, it has a range of approximately 250m deep. Data from the shipboard Ashtek 3 dimensional GPS system is used along with bottom tracking data (when the water is shallow enough i.e. less than 250m) and automatically integrated into ADCP ping data to provide absolute current velocities. Data Processing: The ship ADCP constantly and automatically collects and stores raw .rawdp binary files in ensembles of three minutes worth of pings. This is regularly automatically collated into larger .adp files containing data for several hours (200+ ensembles). This data are processed for use in analysis using specialist software provided by Mark Rosenberg (mark.rosenberg AT utas.edu.au) that integrates together data from the ADCP .adp files for periods (30 minutes in this case) over a give time (from cruise start to the 3-Mar-2006). This produces .any ASCII files. These ASCII files are read into the Matlab processing package using scripts provided by Sergeui Sokolov (sergeui.sokolov AT csiro.au) which then produces the .mat matlab data files covered by this metadata. ADCP data requires proper calibration with respect to ship motion, which were not carried out for this data set, and could cause significant change when processed properly after the voyage. Dataset format: The processed ADCP file is given in matlab .mat format. All 1/2 hour integrations of ADCP data for BROKE-West from 3 days (31-dec-2005) before departure from Fremantle, to the 3-Mar-2006 are included, each column in each matrix or array representing an individual 1/2 hour integration in chronological order. There are numerous gaps in the data that occurred when the ADCP crashed and was not immediately reset or when bad data prevented processing. The location can be identified by plotting a scatter plot of longitude vs latitude, and the times by plotting the julian date. The matlab variables contained in the BROKE_West_ADCP.mat file are contained inside the adcp structure: lon: Longitude (decimal degrees) lat: Latitude (decimal degrees) time: Each column gives the year month day and hour of collection of the corresponding columns in the other variables. depth: Depth of each corresponding velocity value for each 1/2 profile. 60 fixed bin depths are given for each profile. (meters) press: As for depth but given in db. (db) u: Absolute current eastward component in ms-1 for each depth and profile. v: Absolute current northward component in ms-1 for each depth and profile. unav: Ship absolute eastward component in ms-1 for each profile vnav: Ship absolute northward component in ms-1 for each profile jtime: Julian date for each profile (julian days) badvals: Indexes of anomolous latitude and longitude values Acronyms used: ADCP: Accoustic Doppler Current Profiler IASOS: Institute of Antarctic and Southern Ocean Studies CSIRO: Commonwealth Scientific and Industrial Research Organisation This work was completed as part of ASAC projects 2655 and 2679 (ASAC_2655, ASAC_2679).

The Thala Valley Tip Site GIS dataset mapped from January 2001 aerial photography. The dataset includes watercourse, waterhole, breakline, spot height, contour, embankment, rock, sea ice, snow, tide crack and contaminated site features.