Hydrographic and Sonar Data Processing Management and Workflows Marine Measurement Forum Aberdeen 1St May 2013
Total Page：16
File Type：pdf, Size：1020Kb
Hydrographic and Sonar Data Processing Management and Workflows Marine Measurement Forum Aberdeen 1st May 2013 Trish Groves, Account Manager UK Fredericton – Canada • Heeswijk – The Netherlands • Washington DC – United States • Adelaide – Australia Agenda • Introduction • Application and Use Case Examples – GeoAcoustics GeoSwath • Bathymetry and Sidescan Imagery – Kongsberg EM 2040 • Bathymetry, Time Series Imagery and Water Column Imagery (WCI) • Beyond Processing… – Bathymetry and metadata management – Combining results for many applications • Summary Bathymetry Bathymetry with Imagery Bathymetry with WCI Application and Use Cases • Datasets courtesy of Shallow Survey 2012 Common Dataset • Three Survey Areas Selected – Taputeranaga Marine Reserve (East and West) – HMNZS Wellington Wreck Use Case Example: GeoSwath Plus • Selected Geoswath Survey Area – from Shallow Survey 2012 – 48.5 line kilometres – Depth range of 3 to 38 metres – +178 Million Soundings – Simultaneous swath bathymetry and sidescan HMNZS Wellington and Surrounding Area • Bathymetry processing – POSPAC used for post processing – Sound Velocity Corrections applied • Smoothed Best Estimate of Trajectory (SBET) files – Total Propagated Uncertainty (TPU) Computed – GPS tide computed using New Zealand Quasigeoid 2009 – Created Combined Uncertainty and Bathymetry Estimator (CUBE) Surfaces HMNZS Wellington and Surrounding Area • Batch Processing HMNZS Wellington and Surrounding Area • Created CUBE Surface – 0.5m resolution – Geoswath data ideal for CUBE • Large quantities of data ‘where it should be’ – Custom CUBE parameters created Default CUBE – Significant reduction of artefacts, particularly along ship track lines • Caused by lower data density under nadir of Geoswath Transducers – Isolated areas require manual intervention Custom CUBE HMNZS Wellington and Surrounding Area • Area Based Editing HMNZS Wellington and Surrounding Area • 3D View – Data visualization, QC and further editing… HMNZS Wellington and Surrounding Area • Automated Surface Filter – Filter remaining erroneous soundings using computed CUBE surface • Function of Uncertainty • Function of Standard Deviation • Greater of the Two • Lesser of the Two Soundings • Static Value (i.e. 2.0m) • Exports – Various options to export data • CSAR Files • Export Soundings to ASCII • BAG • HTF Reference Surface HMNZS Wellington and Surrounding Area • Seafloor imagery processing – Side Scan imagery processed using integrated Geocoder engine – Corrections included: • Auto Gain and TVG • Beam Pattern Correction • AVG Correction – Created geo-referenced mosaic • 20cm grid resolution • ‘Auto-Seam’ method Use Case Example: EM 2040 • Selected EM 2040 Survey Areas (Shallow Survey 2012) – Taputeranaga Marine Reserve (East): +19 Million Soundings – Taputeranaga Marine Reserve (West): +12 Million Soundings – HMNZS Wellington Wreck: +10 Million Soundings Taputeranaga Marine Reserve • Bathymetry processing – Single tide station observations applied • Predicted tides from common dataset – TPU Computed West – Created CUBE Surfaces • 50cm grid resolution • Areas of exposed reef, soft sediment and parts of HMNZS Wellington wreck observed East Taputeranaga Marine Reserve • Seafloor imagery processing – Time Series imagery processed using integrated Geocoder engine – Corrections included: • Auto Gain and TVG • Beam Pattern Correction • AVG Correction West – Created geo-referenced mosaic • 15cm grid resolution • ‘Auto-Seam’ method • Areas of exposed reef and soft sediment observed − Geocoder ARA analysis reports muddy sand, fine sand, etc. East HMNZS Wellington • Bathymetry and seafloor imagery processing – Similar to Taputeranaga Marine Reserve (East and West) areas – CUBE Surface generated at 25cm grid resolution given Increased line spacing and data density • Water Column Imagery (WCI) also acquired for the wreck site – Raw *.ALL files accompanied by *.WCD HMNZS Wellington • Wreck in main 3 sections, include bow section with gun turret – Image Source: http://en.wikipedia.org/wiki/File:HMNZSWellington1_gobeirne.jpg – Image By: Greg O`Beirne – Few returns of the gun turret barrels in the bathymetry bottom detections, but well defined in WCI… HMNZS Wellington • WCI provides: – More complete representation of submarine landscape – Improved decision support during processing – Mechanism to increase operational efficiencies • Reduce number of survey lines • WCI in HIPS and SIPS: – Seamlessly integrated • Accessed using common bathymetry editing tools – Loaded directly from the raw data files • Minimizes duplication of data – Called on demand • Controlled by extents of bathy editors – Accessible as 2D curtains and as 3D point cloud – Can also be interrogated and used to supplement bathymetry bottom detection results… HMNZS Wellington • Bathymetry supplemented in 3 easy steps… – HMNZS Wellington example: 349 observations added as ‘additional 1. Load Bathymetry 2. Load WCI bathymetry’ – Supports least depth determination, provides more complete target representation, etc. 3. Select WCI and Add Selection The Result Combining Results • Seafloor imagery processing – Ability to combine multiple sources of imagery • Time series imagery from EM2040 • Side Scan imagery from GeoSwath Plus – Mosaic produced from combining all available processed imagery – Created geo-referenced mosaic • 20cm grid resolution • ‘Overwrite’ method Beyond Processing • Marine community requirement to effectively analyze and manage processed bathymetry and associated metadata • Manage all elevation assets together • Client / server environment with relational database • Capture and store critical metadata for search and discovery • Enhances data security, integrity and usability • Worldwide user base Bathymetry Bathymetry Analysis and Management • Load Surfaces into Database EM2040 (3 Datasets) GeoSwath (1 Dataset) Bathymetry Analysis and Management • Metadata Management – Fully customizable to meet needs of the user • Multiple applications – Can be used for extensive queries of data – Used to resolve conflicts in combine operations • Use Case Example: • Geoscience Australia • Vessel name (vesnam) • Starting Port (porsta) • Ending Port (porend) • Type of Sonar (sonmod) – EM 120 – EM 300 – EM 3002D. Bathymetry Analysis and Management • Select surfaces to be combined – Output resulting surface to local disk or database • Define combine options – Output coordinate system – Resolution – Contributor layer • Set Spatial Extents • Resolve Conflicts – Most recent survey data – Shoalest Depth – Uncertainty / Standard Deviation – ZOC – and so on . Bathymetry Analysis and Management • EM 2040 and GeoSwath Plus Combined Result Contributor3D View Layer Data Accessibility • Making the data available… – Internal? – External? – Software Independent? • Web Based! Query Features Extract Bathymetry by WCS Extract to Features by WFS KML in Google Crowd Sourced Bathymetry Some data is better than no data! Summary A comprehensive workflow allows for the following: • Simultaneous processing of various data sources • Automated processing and cleaning tools • Integrating latest technologies • Long term storage and accessibility • Web based data discovery and dissemination • Interoperability through industry standards .