Acoustic depth soundings collected on Australian Antarctic Division voyages, 2006/07 to 2010/11

• Other Authors: AADC (originator), AU/AADC > Australian Antarctic Data Centre, Australia (resourceProvider)
• Format: Dataset
• Language: unknown
• Published: Australian Ocean Data Network
• Subjects: oceans; WATER DEPTH; EARTH SCIENCE; BATHYMETRY/SEAFLOOR TOPOGRAPHY; SEAFLOOR TOPOGRAPHY; BATHYMETRY; SOUNDING; DEPTH; ECHO SOUNDERS; ACOUSTIC SOUNDERS; SHIPS; R/V AA > R/V Aurora Australis; AMD/AU; AMD; CEOS; GEOGRAPHIC REGION > POLAR; Antarctic; Antarc*; aurora australis; Australian Antarctic Division; Sea ice
• Online Access: https://researchdata.ands.org.au/acoustic-depth-soundings-200607-201011/1358667; https://data.aad.gov.au/metadata/records/VMS_Bathy_Processing; https://secure3.aad.gov.au/proms/public/projects/report_project_public.cfm?project_no=2652; http://data.aad.gov.au/aadc/portal/download_file.cfm?file_id=4651; http://data.aad.gov.au/aadc/metadata/citation.cfm?entry_id=VMS_Bathy_Processing

The Ashtech GPS unit is not currently licensed to receive differential corrections and the AAD are not aware when they last paid for the annual subscription. A error value still exists for the Transducer/GPS offset, even after the script correction. A 5m error value has been applied in the horizontal accuracy calculation spreadsheet for this correction. The best assessment of the horizontal accuracy is therefore Order 2. The data processing was done by the Royal Australian Navy's (RAN) Deployable Geospatial Support Team (DGST) and was provided to the Australian Antarctic Data Centre by the Australian Hydrographic Office. The dataset is titled HI483A because the processing was done on a 2010/11 voyage to Mawson and HI 483 was going to be a RAN survey at Mawson. The RAN survey wasn't feasible because of sea ice. The data processed (12KHz EDO 323HP echo sounder data) was collected on the following voyages: 2006/07 V2, V4, V6 2007/08 SIP, V3, V6 2008/09 V0, V1, V2, V3, V5 2009/10 V0, V1, V2, V3, V4, V5, V7 2010/11 Trials, V1, V2, V3, VE2, VMS All voyage data sets were processed in the following manner. As the Aurora Australis sails from either Hobart, Tasmania or Fremantle, Western Australia all the shallow water data files containing depths less then 200m around these ports were not processed and deleted. If the sea floor image was too hard to determine during the voyage either parts of day lines were not processed or the whole line deleted depending on the quality of the data. This is evident with some day *.CSV files containing a second or third file, these files had the same file name and were given a end character of _2 or _3. Unfortunately the program Echoview is meant to allow the user to span gaps when processing a line but more often than not, this was not the case. So if there was a requirement to a have gap in the daily file then usually a second file was created. Regularly throughout all voyages files were observed that had no GPS data associated with the depths. Any raw files without GPS data could not be processed, all these files have been deleted. Occasionally corrupt files were experienced, and these corrupt files have also been deleted. When the Aurora Australis was at anchor off an Antarctic Station these files too were deleted. With the various problems with the raw data files, no voyage has complete sounding data for the whole voyage. Some voyages have large sections of data missing, but unfortunately this data was not able to processed due to one of the above factors. All soundings were processed utilising the spheroid, WGS84 and only geographic co-ordinates have been determined. UTM grid co-ordinates were not calculated during the processing stages due to software limitations. Grid co-ordinates were not calculated for the final HTF files. Scripts were developed to apply depth water corrections, tide offsets if shallower than 200m of water and the layback of the sounder with respect to the Ashtech GPS. The processing of the data from 2007/08 V3, 2007/08 V6 and 2010/11 V3 was incomplete. Complete processing of the data from these voyages was done as part of HI513 which is described by the metadata record with ID AAD_voyage_soundings_HI513. The data has not been through the verification process for use in charts. Potential uses of the data include the updating of nautical charts and the creation of bathymetric datasets.