Professional Documents
Culture Documents
BOOK 01y
BOOK 01y
53 and up
PDS2000 - TPE Implementation-Rev4.Docx
Document ID: Date: 2012.12.21
Revision: 4
1. Introduction
The release of PDS2000 Version 3 end 2006 brought amongst many other new features, the
integration of CUBE modeling together with the implementation of the TPE computation.
As part of the CUBE support in PDS2000 a TPE (Total Propagated Error) computation is add-
ed specifically for multibeam applications. The related equipment like positioning, motion,
compass and multibeam have properties to define their accuracy.
The TPE is computed in real-time and a number of displays are available to visualize both
horizontal and vertical TPE.
It is possible to use the TPE as a filter by setting either the relevant IHO order or by defining
a custom vertical error limit. The TPE values are also the basis for the CUBE processing and
used to assign a weight to a sounding when populating the nodes in the CUBE grid
- The PDS2000 error model originates from the CUBE implementation which in turn is
based on the well known error model developed by CHS (Canadian Hydrographic Ser-
vice) and OMG (Ocean Mapping Group of University of New Brunswick)1
- The reported error values in PDS2000 are always presented as 95% confidence level
values.
- PDS2000 follows the CUBE implementation where the horizontal error resulting from the
fore-aft beam opening angle is not included.
1
1995 CHS Error Model Report – Hare, Godin and Mayer
1
Reference: PDS2000 – TPE implementation for Version 3.7.0.53 and up
PDS2000 - TPE Implementation-Rev4.Docx
Document ID: Date: 2012.12.21
Revision: 4
3. Horizontal Error
The diagram below illustrates the error contributions included in the total horizontal error.
Some apply to the entire swath while other errors are range and angle dependant
When available from the GPS system and supported by the PDS driver, the real-time accura-
cy information from the GPS will be used
When not available from GPS system, the GPS mode will be used to assign default values ac-
cording to table below.
Total GPS error Range error Heading error Angle error Pitch error Beamwidth error
GPS horizontal
error
SV profile error + Heading sensor error Angle error over Total pitch error over Eror due to Along
Range measurement over beam range beam range depth beamwidth over
error beam range
Offset measure-
ment error + re-
lated heading,
roll, pitch errors
2
Reference: PDS2000 – TPE implementation for Version 3.7.0.53 and up
PDS2000 - TPE Implementation-Rev4.Docx
Document ID: Date: 2012.12.21
Revision: 4
4. Vertical Error
The diagram below illustrates the error contributions included in the total vertical error.
Some apply to the entire swath while other errors are range and angle dependant
Total vertical Total heave er- Range error Angle error Pitch error Beamwidth er-
reduction error ror ror
Errors for Measured heave Beam uncertainty Total roll error Total pitch error Along beamwidth
Draft, Squat, error, Induced or computed over beam range over beam range coefficient over
range error (sam- depth
Load, Tide, heave error
ple dist, pulse-
GPS Z error length) +
Soundvelocity
error Total roll error : Total pitch error :
Base roll error + Pitch sensor error
Angle meas error + Alignment error
+ Angle svp error + Stabilisation
+ Angle surface error
speed error
RESON 7k multibeam sonars provide a real-time uncertainty value per beam which is fed in-
to the error mode and used to compute the range error.
PDS2000 provides default values for all parameters, when for a sensor more detailed infor-
mation is available that will be part of the driver and automatically loaded.
3
Reference: PDS2000 – TPE implementation for Version 3.7.0.53 and up
PDS2000 - TPE Implementation-Rev4.Docx
Document ID: Date: 2012.12.21
Revision: 4
4
Reference: PDS2000 – TPE implementation for Version 3.7.0.53 and up
PDS2000 - TPE Implementation-Rev4.Docx
Document ID: Date: 2012.12.21
Revision: 4
Not all parameters affect the total error at the same time. Depending on the equipment con-
figuration and the use of RTK or tide for depth reduction some parameters will not be used in
the error model. E.g. when working in RTK mode, dynamic draft is part of the measurement.
5
Reference: PDS2000 – TPE implementation for Version 3.7.0.53 and up
PDS2000 - TPE Implementation-Rev4.Docx
Document ID: Date: 2012.12.21
Revision: 4
The table below lists the parameters used in PDS for the supported orders. They are based
on S44-5th Edition 2008 and Nederlandse normen voor Hydrografische opnemingen 1st Edi-
tion 2009 – Erratum table 1
Order TPE Horizontal TPE Vertical
IHO Special Order 2m. a=0.25m
b=0.0075
IHO Order 1 5m + 5% of depth a=0.5m
b=0.013
IHO Order 2 20m + 10% of depth a=1.0m
b=0.023
IHO Order 3 150m + 5% of depth a=1.0m
(S44 4th Edition) b=0.023
NL Norm A 0.35 + 1% of depth a=0.1m
b=0.0075
6
Reference: PDS2000 – TPE implementation for Version 3.7.0.53 and up
PDS2000 - TPE Implementation-Rev4.Docx
Document ID: Date: 2012.12.21
Revision: 4
8. TPE analysis
The PDS Processing module now includes a tool that allows a more detailed analysis of the
TPE computation. With this tool the detailed results of a TPE computation for the selected
ping can be exported to a text file.
This file contains the standard deviations used for the TPE computation and the Horizontal
and Vertical errors split out to the individual error contributions.
RESON provides a an Excel sheet capable of loading the TPE text file and visualizing the TPE
results as tables and graphs. The sheet is called TPEview.xslm and can be found in the in-
stallation folder of your PDS2000 version.
7
Reference: PDS2000 – TPE implementation for Version 3.7.0.53 and up
PDS2000 - TPE Implementation-Rev4.Docx
Document ID: Date: 2012.12.21
Revision: 4
Example of Depth error graph from TPEview Example of Position error graph from TPE-
view