Triton Navigation - Manual (Page 4)

Page 1
Navigation Processing
Processing navigation is an important step to obtaining clean results and some thought
should go into what parameters to use and what level of processing is necessary for the
collected data. Discussed in the following sections are how Perspective sorts and displays
the navigation data from imported raw data files, reasons to process navigation prior to
creating mosaics or DTMs, available options for navigation processing, and possible
workflows. There are also a couple examples of processing files with bad navigation at the
end of this document
1.0 Navigation Types
In Perspective, when raw data files are imported the navigation data is automatically
extracted, displayed in the map view, and placed in the file tree navigation layers. The
navigation file tree is sorted into 5 main categories:

Sidescan - navigation for sidescan data extracted from raw data file

Bathymetry - navigation for bathymetry data extracted from raw data file

Singlebeam - navigation for singlebeam data extracted from raw data file

Subbottom - navigation for subbottom data extracted from raw data file

Vessel - vessel navigation extracted from raw data file
If multiple data types are available in one raw data file, importing that one data file can
populate multiple navigation data fields.
For example, if the data file comes from a Reson 7125
survey and includes both multibeam bathymetry and
sidescan data, the importing of only one raw data file will
populate the
Sidescan navigation file tree node, the
Bathymetry navigation node and the Vessel navigation
node as shown right.
This is very important as it allows the user to perform minimal processing on the
bathymetry navigation just to remove spikes in the data while heavily processing the
sidescan navigation to get parallel uniformly spaced beam lines for clean mosaics.