Академический Документы
Профессиональный Документы
Культура Документы
PDS2000
Version 4.2.4
March 2013
RESON B.V.
Stuttgartstraat 42- 44
3047 AS Rotterdam
The Netherlands
2 PDS2000 Documentation 3
2.1 Introduction ............................................................................................................. 3
2.2 Overview ................................................................................................................. 3
2.2.1 Anchor Handling ........................................................................................... 3
2.2.2 Bar Sweep..................................................................................................... 3
2.2.3 Boeilog .......................................................................................................... 4
2.2.3.1 Appendix Boeilog................................................................................. 4
2.2.4 Boraciet ......................................................................................................... 4
2.2.4.1 Addendum Boraciet ............................................................................. 4
2.2.5 Bottom Classification .................................................................................... 4
2.2.6 Bucket Dredging ........................................................................................... 5
2.2.7 Cable Lay ...................................................................................................... 5
2.2.8 Cutter Dredge ............................................................................................... 5
2.2.9 ES3 ............................................................................................................... 5
2.2.10 Excavator .................................................................................................... 5
2.2.11 Frequently Asked Questions ....................................................................... 6
2.2.12 HydroBat ..................................................................................................... 6
2.2.13 Interface Setup ............................................................................................ 6
2.2.14 Multibeam.................................................................................................... 6
2.2.15 Multibeam Calibration ................................................................................. 6
2.2.16 PDS2000 LiteView ...................................................................................... 7
2.2.17 PDS2000 User Manual ............................................................................... 7
2.2.18 Pipe Detection ............................................................................................. 7
2.2.19 Pipe Position Monitor .................................................................................. 7
2.2.20 Pipe Position Monitor J-Lay ........................................................................ 8
2.2.21 Rope Excavator .......................................................................................... 8
2.2.22 Slope Protection .......................................................................................... 8
2.2.23 Sonar Swath ............................................................................................... 8
2.2.24 Tide Application .......................................................................................... 9
2.2.25 Trailing Suction Hopper .............................................................................. 9
2.2.26 Trencher ...................................................................................................... 9
2.2.27 USBL ........................................................................................................... 9
3 Installation 11
3.1 Introduction ........................................................................................................... 11
3.1.1 Requirements .............................................................................................. 11
3.1.2 Memory Improvement ................................................................................. 12
3.2 Install PDS2000 .................................................................................................... 12
3.2.1 Start PDS2000 Installation .......................................................................... 12
4 Using PDS2000 47
4.1 Introduction .......................................................................................................... 47
4.2 Docking ................................................................................................................ 48
4.2.1 Dock Areas ................................................................................................. 49
4.3 Context Menus ..................................................................................................... 49
4.4 Navigation in a 3D View ....................................................................................... 50
4.4.1 Rotate the Data .......................................................................................... 50
4.4.2 Shift the Data .............................................................................................. 51
4.4.3 Zoom in/out in the Data .............................................................................. 51
4.4.4 Scale the Data ............................................................................................ 51
4.4.5 Center the Data .......................................................................................... 51
5 Starting PDS2000 53
5.1 Introduction .......................................................................................................... 53
5.1.1 Project......................................................................................................... 53
5.1.2 Application Type ......................................................................................... 53
5.1.3 Configuration .............................................................................................. 53
5.2 Project Structure .................................................................................................. 54
5.3 Projects Common Files ........................................................................................ 54
5.4 New Project Wizard .............................................................................................. 55
5.4.1 Project Configuration .................................................................................. 57
5.4.1.1 Description ........................................................................................ 57
5.4.1.2 Units .................................................................................................. 58
5.4.1.3 Coordinate System ........................................................................... 58
5.4.1.4 Formats ............................................................................................. 59
5.4.1.5 Log Files ............................................................................................ 59
5.4.1.6 File History ........................................................................................ 61
5.4.1.7 Disk Space ........................................................................................ 61
6 Coordinate System 71
6.1 Introduction ........................................................................................................... 71
6.2 Project Coordinate System ................................................................................... 72
6.3 Coordinate System Wizard ................................................................................... 73
6.3.1 New Coordinate System ............................................................................. 73
6.3.2 Select Coordinate System .......................................................................... 74
6.3.3 Ellipsoids ..................................................................................................... 75
6.3.4 Datum Transformation ................................................................................ 76
6.3.5 Select Datum Transformation ..................................................................... 77
6.3.6 Datum Transformation Parameters ............................................................ 78
6.3.7 Geoid Model ................................................................................................ 79
6.3.8 Unit .............................................................................................................. 81
6.3.9 Projection .................................................................................................... 82
6.3.10 Select Projection ....................................................................................... 83
6.3.11 Projection Parameters .............................................................................. 84
6.3.12 Post Correction ......................................................................................... 85
6.3.13 Save Coordinate System .......................................................................... 86
6.3.14 Coordinate System Overview ................................................................... 87
6.4 Edit Coordinate System ........................................................................................ 87
7 Vessel Configuration 91
7.1 Introduction ........................................................................................................... 91
7.2 Setup a Vessel Configuration ............................................................................... 91
7.2.1 New Vessel Configuration........................................................................... 92
7.3 Geometry .............................................................................................................. 93
7.3.1 Vessel Contour ........................................................................................... 95
7.3.1.1 Import Vessel Contours ..................................................................... 96
7.4 Equipment............................................................................................................. 96
7.4.1 Sub System ................................................................................................. 98
7.4.2 Navisound Graphical Trace ........................................................................ 99
7.4.3 Outputs...................................................................................................... 100
7.5 Computations ..................................................................................................... 101
7.5.1 Advanced Computations ........................................................................... 101
7.6 Data Sources ...................................................................................................... 103
7.7 Guidance ............................................................................................................ 104
7.8 Tools ................................................................................................................... 105
8 Guidance 131
8.1 Introduction ........................................................................................................ 131
8.2 Route .................................................................................................................. 132
8.2.1 Route Editor .............................................................................................. 133
8.2.2 ASCII Import Wizard ................................................................................. 136
8.3 Runlines ............................................................................................................. 138
8.3.1 Runlines Editor ......................................................................................... 139
8.4 Waypoints .......................................................................................................... 141
8.4.1 Waypoints Editor ...................................................................................... 142
8.5 Design Model ..................................................................................................... 143
8.5.1 3D Design Model Editor............................................................................ 144
8.6 Cutter Dredge ..................................................................................................... 146
8.7 Work Areas ........................................................................................................ 147
8.8 Restricted Areas ................................................................................................. 148
8.8.1 Restricted Areas Editor............................................................................. 148
9 Events 155
9.1 Introduction ......................................................................................................... 155
9.2 Events Mode ....................................................................................................... 155
9.2.1 Mode ......................................................................................................... 156
9.2.2 Conditions ................................................................................................. 156
9.2.3 Push Button .............................................................................................. 156
9.2.4 Event Definition ......................................................................................... 156
9.2.4.1 Separator Delimited ......................................................................... 158
9.2.4.2 Fixed Field ....................................................................................... 158
9.2.4.3 Field Selection ................................................................................. 159
9.3 Events Data Source ............................................................................................ 160
9.4 Events Numbering .............................................................................................. 161
11 Explorer 209
11.1 Introduction ...................................................................................................... 209
11.2 Context Menus ................................................................................................. 210
11.2.1 General Context Menu ........................................................................... 211
11.2.1.1 Backup Files Outside Project ........................................................ 211
11.2.2 File Group Context Menu ....................................................................... 213
11.2.3 File Context Menu .................................................................................. 213
11.3 Projects Common Database ............................................................................ 214
11.4 PDS2000 Database ......................................................................................... 215
11.4.1 Convert S-57 to C-Map........................................................................... 217
11.4.1.1 Updates ......................................................................................... 219
11.5 Project Database .............................................................................................. 219
11.5.1 Clipping Polygons ................................................................................... 224
11.5.1.1 Clipping Polygon Editor ................................................................. 225
11.5.2 Color Tables ........................................................................................... 226
11.5.2.1 Color Table Generator .................................................................. 226
11.5.2.2 Color Table for Bottom Classification ........................................... 230
11.5.2.3 Dredge Differential Color Table .................................................... 231
11.5.3 Contour Definitions ................................................................................. 231
11.5.3.1 Contour Definition Generator ........................................................ 232
12 Acquisition 251
12.1 Introduction ....................................................................................................... 251
12.2 Start Acquisition ................................................................................................ 251
12.2.1 Simulation ............................................................................................... 251
12.2.2 Realtime .................................................................................................. 251
12.3 Data Visualization ............................................................................................. 252
12.3.1 Layout ..................................................................................................... 252
12.4 Acquisition Menu Bar and Toolbar ................................................................... 254
12.4.1 Selecting Guidance ................................................................................. 259
12.4.1.1 Making Runlines or Routes Real Time .......................................... 260
12.5 Logging ............................................................................................................. 260
12.5.1 Check the Logging .................................................................................. 261
12.6 Shortcuts........................................................................................................... 262
12.6.1 F-Keys ..................................................................................................... 263
12.6.2 Attribute Actions ...................................................................................... 265
12.6.2.1 Attach to Button ............................................................................. 266
12.6.3 Manual Input Actions .............................................................................. 267
12.6.4 View Attribute Actions ............................................................................. 267
12.6.5 Shortcut Keys .......................................................................................... 270
12.7 Presentations .................................................................................................... 270
13 Views 271
13.1 Introduction ....................................................................................................... 271
13.2 3D View ............................................................................................................ 272
13.2.1 3D View – Online .................................................................................... 273
13.2.2 3D View – Online Dredge ....................................................................... 274
13.2.3 3D View – Toolbar and Context Menu .................................................... 275
13.2.4 3D View – Layers .................................................................................... 277
14 Replay 389
14.1 Introduction ...................................................................................................... 389
14.1.1 Controlling the Replayer ......................................................................... 389
14.1.2 External Replay Settings ........................................................................ 390
14.1.3 Saving Layout and Vessel Configuration ............................................... 391
14.1.4 Recomputation and Saving Results ....................................................... 391
15 Processing 393
15.1 Introduction ...................................................................................................... 393
15.2 Validating and Presenting Survey Results ....................................................... 393
16 Editing 395
16.1 Introduction ...................................................................................................... 395
16.1.1 Available Editors ..................................................................................... 395
20 Plot 547
20.1 Getting Started ................................................................................................. 547
20.1.1 Create a Plot Project .............................................................................. 547
20.1.2 Add Data Files ........................................................................................ 549
20.1.3 Place a Plan View ................................................................................... 549
20.1.4 Create a Plot ........................................................................................... 551
20.1.5 Place Panels ........................................................................................... 553
20.1.6 Add Layers ............................................................................................. 554
20.1.7 Print or Export a Plot .............................................................................. 554
20.2 How Plotting Works .......................................................................................... 555
20.2.1 Regeneration .......................................................................................... 555
20.2.2 Panel and Layer Order ........................................................................... 556
20.2.3 Overwrite Suppression ........................................................................... 556
20.2.4 Templates ............................................................................................... 557
20.2.5 Keywords ................................................................................................ 557
20.3 Available Panels ............................................................................................... 557
20.3.1 Plan Panel .............................................................................................. 558
20.3.2 North Arrow Panel .................................................................................. 559
20.3.3 Profile Panel ........................................................................................... 560
20.3.4 Profile Volume ........................................................................................ 561
20.3.5 Profile Series Panel ................................................................................ 564
20.3.6 Profile Cross Series Panel...................................................................... 565
20.3.7 Profile Info Panel .................................................................................... 566
20.3.8 Text Block Panel and Text Box .............................................................. 566
20.3.9 DXF Panel .............................................................................................. 567
20.3.10 Color Mapping Panel ............................................................................ 568
20.3.11 Image Panel ......................................................................................... 568
20.3.12 Key Map Panel ..................................................................................... 569
20.3.13 Scale Bar Panel .................................................................................... 569
20.4 Available Layers ............................................................................................... 570
20.4.1 Clipping Polygon Layer........................................................................... 571
20.4.2 CMap Layer ............................................................................................ 571
20.4.3 Dredge Track Layer ................................................................................ 572
20.4.4 DXF Layer .............................................................................................. 572
20.4.5 Events Layer ........................................................................................... 573
20.4.6 Event Markers Layer .............................................................................. 573
20.4.7 Geographic Grid Layer ........................................................................... 573
22 Export 613
22.1 Introduction ...................................................................................................... 613
22.1.1 Export Configuration File ........................................................................ 613
22.1.2 Export Type ............................................................................................ 614
22.2 Export Window ................................................................................................. 615
22.2.1 Excel and Comma Separated ................................................................ 615
22.2.2 Simrad EM Datagram ............................................................................. 617
22.2.3 Multibeam XYZ ....................................................................................... 618
22.2.4 XTF ......................................................................................................... 620
22.2.5 S7K ......................................................................................................... 622
22.2.6 SDS ........................................................................................................ 622
22.2.7 SZ ........................................................................................................... 623
22.2.8 Magnetometer DAT ................................................................................ 624
22.2.9 FAU......................................................................................................... 625
22.2.10 GSF ...................................................................................................... 625
22.3 Exporting .......................................................................................................... 625
1.1 PDS2000
PDS2000 is a software package for hydrographic survey and dredging
operations. It offers modules that cover the entire operation from
acquisition to an end product. The software runs on standard PC’s with
the Windows operating system. PDS2000 is available in different versions
tailored to specific operations.
The purpose of all the measurements is real time reading of data from
one or more sensors, make computations with the data, show the results
of the computations and simultaneously log the data. To be able to control
those processes a number of Views has been developed that will show
the reading, computations, results and logging processes. A view can
show the data either graphically or alpha-numerically.
Data needs to be checked after the measurements. PDS2000 gives
several options to remove anomalies and outliers, either manually or
automatically.
The final presentation of the cleaned data can be in the form of models,
tables, files, volumes, nautical charts and reports.
This manual is also available as a HTML Help file. Press F1 or select
Help > Help Topics to open the PDS2000 help files.
2.1 Introduction
This chapter will give an overview of all the manuals that will be delivered
with a PDS2000 version.
All these documents are accessible as PDF via the Start menu of
Windows at the location Start > Reson > PDS2000 Vx.x.x.x > PDS2000
Documentation. The documents can also be found in the folder
‘C:\Program Files\RESON\PDS2000 Vx.x.x.x\manuals’.
2.2 Overview
The manuals are listed not in order of importance but in alphabetic order.
For each manual a brief explanation will be given.
2.2.4 Boraciet
The Boraciet application is meant to monitor on the shore the work and
movements of the (dredging) vessel. To monitor this a GPRS link is made
between the vessel and on shore (called ‘wal server’). With this link it is
also possible to send data to the vessels. The ‘wal server’ is the central
place where the information of the different vessels comes together.
On shore the ‘wal server’ is connected by Ethernet with several PC’s
(called ‘wal clients’). On these ‘wal clients’ the activities of the vessels can
be monitored online. It is also possible to replay the activities of the
vessels on the ‘wal clients’.
The documentation is in Dutch.
For more information see the file Boraciet.pdf.
2.2.9 ES3
This document is made as an additional section in the ES3 User Manual
to explain the setup of PDS2000 for the Odom ES3.
The Odom ES3 and the other sensors (navigation, motion, heading and
sv probe) are interfaced to the RTA (Real Time Appliance) box. Therefore
in PDS2000 the setup of the clock synchronization and the interface to
the different sensors is different from the standard interfacing in
PDS2000.
For more information see the file ES3.pdf.
2.2.10 Excavator
The application type ‘Excavator’ is for a project where an excavator is
used for dredging.
A project with the application type ‘Excavator’ can contain one or two
vessels. For a one vessel project the vessel is the excavator and for a two
vessels project the vessels are the excavator and a pontoon on which the
excavator is located.
In this application manual the setup of an excavator project for a stand-
alone excavator and for an excavator on a pontoon will be discussed.
After the project is setup the separate tools of the excavator configuration
2.2.12 HydroBat
The HydroBat is a multibeam system where the data collection and the
control of the HydroBat will take place in PDS2000.
An explanation of the setup of the HydroBat in the equipment list will be
discussed and the special views for the HydroBat in the Acquisition will be
explained.
For more information see the file HydroBat.pdf.
2.2.14 Multibeam
The Multibeam Survey application in the PDS2000 software is an
application type for a survey with one or more multibeam systems.
In this manual the equipment, which is necessary for a multibeam survey,
will be discussed and also how to setup PDS2000 for this type of survey.
For more information see the file Multibeam.pdf.
2.2.26 Trencher
In PDS2000 the application ‘Trencher’ is made for the support of a cable
trencher. The cable will be trenched with a cable trencher and in this
application the knife depth will be calculated to determine the burial depth
of the cable.
In PDS2000 two vessels have to be setup, one is the survey vessel and
one is the trencher. The trencher will be positioned by a USBL positioning
system.
In this document will be explained which equipment on the trencher and
on the survey vessel, next to the standard equipment, have to be
selected. After the setup the calibration will be explained and some views
in the Acquisition will be discussed.
For more information see the file Trencher.pdf.
2.2.27 USBL
In this manual the USBL (Ultra Short BaseLine) as used in PDS2000 will
be explained.
The USBL equipment has to be setup in the Equipment list of PDS2000.
A USBL transceiver device and a USBL transponder device has to be
selected and setup.
Before a USBL survey can be started, a USBL calibration has to be done
to find the misalignment of the USBL transceiver. In this manual the
procedure for the USBL calibration will be explained.
For more information see the file USBL.pdf.
3.1 Introduction
This part of the manual describes the minimum requirements, how to
install PDS2000, C-Map charts and Tresco charts on a computer and how
to configure the computer for optimum use with PDS2000.
3.1.1 Requirements
The supported operating systems are for 32 bit and 64 bit:
MS Windows XP Professional Service Pack 3 or higher
MS Windows Vista
MS Windows 7
The system requirements for a desktop and laptop system are:
Minimal requirements:
CPU: modern Quad Core Processor
Monitor: single monitor system
Graphic card with OPENGL support and 1 Gb of memory; i.e.
NVidia Geforce GTX 4xx
4 Gb internal memory
1 x 500 Gb Hard disk
DVD Writer
Multi serial I/O card
Preferred requirements:
CPU: 8 Core Processor
Monitor: dual monitor system
Dual Graphic card with OPENGL support and 3+ Gb of memory,
i.e. NVidia GeForce GTX 6xx or ATI Radion HD 79xx
Having a 32 bit operating
system limits the amount of 8 Gb internal memory
usable internal memory to
Raid 0 Hard disk system for data storage: 1 Tb minimum
4 Gb.
DVD Writer
Multi serial I/O card
The requirements for the PC are depending on the application. A single-
Do this only once! It will be remembered by Windows the next time the
system is started.
When these steps are not performed the application can only use the
default maximum memory. So it is not necessary to apply these changes
but when done you get more memory for the applications.
The modification is only needed for 32 bit Windows operating systems. 64
Bit Windows operating systems don’t need to be modified. They already
are able to give the applications memory allocation bigger than 2 Gb.
b. Before the actual installation will start the user has to select the type of
setup.
From this new PDS2000 version onwards PDS2000 will only run with
the new version of the C-Map software. Click on to start with
the installation of the new C-Map software. If the user clicks on
no C-Map software will be installed and PDS2000 will not run
with C-Map anymore. Only when the user install later on the new C-
Map software PDS2000 will run again with C-Map.
See the chapter ‘Installing and Using C-Map’ on page 24 for a detailed
explanation of the C-Map installation.
f. Click on in the next page of the install wizard to start the
PDS2000 installation. Click on to finish the installation.
Installing PDS2000 will place the PDS2000 and the Dongle software
on the hard disk of the computer.
PDS2000 V.x.x.x.x
Where x.x.x.x is the installed version number. This folder contains the
programs and supporting files to run PDS2000.
General
Contains device drivers and more supporting files.
GeoidModels
Contains the files with the geoid models (see page 79) and X, Y
Figure 3-6 Device Manager window with the Moxa extender card
d. Set the Rx FIFO Trigger to 1. Check the option Set the change to all
the ports and click on .
This sets the timing for all ports to optimal, giving the shortest possible
delays.
Select in window Found New Hardware Wizard dialog the option Yes, this
time only and click on to continue with the wizard.
Figure 3-10 The About Control Center window where the PDS2000 dongle
can be updated
When the dongle update is available with the latest PDS2000 installation
select the ‘All Dongles.dk4’ file. This file contains the dates for all
PDS2000 released dongles as maintained by RESON.
When the user has received a separate patch for his dongle then browse
to the correct folder and select the dk4 file as received from RESON.
Click on to start the update of the dongle. When the update is
not successful contact your local agent or RESON B.V. and inform them
on the internal ID and the dongle s/n.
The Remote Presentation should have the same version number as the
PDS2000 version on the main computer!!
a. Select the folder ‘CMap’ on the CD-Rom of PDS2000, and start the file
‘Setup.exe’.
It is very important not to install the driver when Windows detects the
eToken driver and wants to install it.
Figure 3-17 C-Map Professional SDK Setup with installation of the eToken
dongle and the C-Map software
The eToken PRO (32k) Select when the old eToken dongle is used, select
does not work on MS when the new dongle is used.
Windows 7 64bits!!!!!
d. It is possible that after the installation of the eToken driver or after
Figure 3-19 C-Map Professional SDK Setup with installation of the C-Map
software
Figure 3-20 Welcome page of the C-Map Professional SDK Runtime Setup
wizard
The diagonal of the main computer screen used for PDS2000 has to
be set. This will be used to find the best display resolution. Click on
when the diagonal is not known.
Click on after the right screen diagonal is entered.
When the C-Map software is installed on a computer where no C-Map
software was installed before then the next dialog will be ‘l‘.
j. When old C-Map software with a license was active before the new
software is installed then the next dialog will ask what to do with the
license.
The users who are only using the S-57 converted charts in C-Map can
skip the items b – h and continue with item i on page 33.
Figure 3-31 C-Map Chart Manager with the Professional+ database set as
default
To use C-Map with the Select the right database at the top and choose one of the license
same eToken dongle on a actions.
different computer the
same license information Click on when the user wants to read the usr file with
has to be activated again. the license information. Select the file and click on in the
‘Select a license file’ dialog to read the license code(s) from the file.
For clients who are only using the converted S-57 files select as
database ‘Software Modules’ and use always
this database does not have a Zone defined in the usr file.
because
Figure 3-34 Add License Manually window to add the license code(s)
Select the right zone with the right area and enter the license code as
given in the email or from the usr file. Click on to activate
the license for the selected zone. Repeat this for each zone and/or
area that needs a license.
Figure 3-35 Licenses page of the C-Map Chart Manager with a license for
a zone.
k. C-Map with the right database is now installed and can be used in the
views of PDS2000.
a. Place the new DVD with the database in the DVD drive and click on
.
3.3.0.0. But before it will work in one of these ‘old’ versions, the file
‘CMGBase.dll’ located in the ‘PDS2000 Vx.x.x.x’ folder of the ‘old’ version
has to be deleted.
In some dedicated plan views in PDS2000, C-Map can be viewed as a
layer. Click on in the toolbar or select Layer Control in the context
menu to get the Layers window.
C-Map charts are digitized with a precision of 0.3 mm. This results in
chart accuracy on the display, which is given in the table above for the
largest scale of each scale level.
Display Detail
For the details of the C-Map chart the options are:
Full shows all the soundings, texts etc.
Standard takes most soundings away.
Base shows only the minimum amount of information on the C-Map
chart.
Show Light Info
The light information can be switched on or off.
Show Generic Text
The names of ports and areas can be switched on or off.
Show Other Text
Additional text such as names of features can be switched on or off.
Anti Cluttering
Switch override suppression (C-Map's anti-cluttering engine) on or off.
Show Chart Boundaries
The red chart boundaries in the display can be switched on or off.
Use C-Map Filters
C-Map filters are not user definable. Contact RESON B.V. in case
special requirements for C-Map filters are needed. This function
enables or disables the filters.
C-Map Filter Name
At the moment three filters are available:
- No Buoys
- No Buoys and Beacons
- No Buoys, Beacons and Piles
These filters remove the filtered items from the chart.
The option ‘Install Sentinel driver’ should be selected when the Tresco
charts are installed for the first time and no Sentinel driver is installed
yet.
The other three options are not needed for a proper installation of the
Navigis software.
Click on to continue.
The selected folder should be identical with the folder that is selected
for the Navigis software in Figure 3-44 on page 39.
Click on to continue with the installation.
Don’t select the option ‘Install Sentinel driver’ because the driver is
already installed during the installation of the Tresco Navigis software.
Click on to continue with the setup.
d. In the next page the installation of the kernel can be started.
The Tresco kernel needs to know the width of the screen to calculate
the scale to display the charts in the correct scale on the screen.
Click on after the right screen width is entered and the
installation will be finished. Click on to finish the installation of
the kernel.
When no detailed information on the Tresco chart is displayed it is
possible that the file TE.PMT, which has to be used in conjunction with
the dongle, is not installed on the right location. Check if the file is present
on the DVD, if not contact RESON BV or Tresco about this problem. If the
file is present copy the file to the folder ‘C:\Navichart\S57’.
Display Detail
For the details of the Tresco chart the options are:
Full shows all the soundings, texts etc.
Standard takes most soundings away.
Base shows only the minimum amount of information on the Tresco
chart.
Show Geographic Names
The geographic names can be switched on or off.
Show Names For Position Reporting
The labels for the position reporting can be switched on or off.
Show Buoys and Beacons
The buoys and beacons can be switched on or off. The light for the
buoys and beacons can be switched on or off with the option ’Show
Lights’.
Show Lights
The light and the labels can be switched on or off.
Show Light Descriptions
The labels for the lights can be switched on or off.
This option will only work when the option ‘Show Lights’ is on.
Show Full Length Sector Lights
The full length for some of the sector lights can be switched on or
off. Most of the lights don’t have a full length option.
This option will only work when the option ‘Show Lights’ is on.
Text Resolution
The size of the text on the charts can be defined in dpi.
Symbol Resolution
The size of the symbols on the charts can be defined in dpi.
4.1 Introduction
PDS2000 is designed with a Windows ‘Look and Feel’. On top of that
PDS2000 has some additional features.
Docked
The view is fixed in one of the dock areas (see below).
Floating
The view is docked but movable. Floating views can be located
outside the window.
MDI Child
‘Multiple Document Interface’ child. The view behaves like any other
view in a Windows application.
Docked to
When pressed, the choice is given to dock a view to any of the four
dock areas (see below).
As shown above, the client area has four dock areas: top, bottom, left and
right. Each dock area can have multiple views.
With the option Displays the Displays window can be opened in which
views can be added, modified or removed from the module. The option
Add Display is a quick method to add a new view to the module. Check
one of the existing views and this view will appear in the module. When a
5.1 Introduction
The Control Center should From the Control Center every module of PDS2000 can be started. But
always be running while before one of the modules is started a project, an application type and a
PDS2000 is used. configuration have to be created or selected. The Control Center does not
start when no project is available.
5.1.1 Project
A project can be an area to be surveyed, a harbor to be made, a river that
has to be dredged to a navigable depth, etc. It may require the
employment of one or more vessels (survey vessels, dredgers, work
ships, excavators) and each vessel can have a special task in the project.
A project has the information on the method of measuring and all the
information necessary to do the measurements.
PDS2000 stores all the details of a project in one folder.
5.1.3 Configuration
A configuration describes the way an application type is carried out. It
contains the used vessel(s), the layout used for the Acquisition and (if
present) Presentation(s), how events are used and alarms are managed.
Multiple configurations are possible for all application types.
Any object that carries sensors is defined as a vessel in PDS2000. Some
application types can handle multiple vessels, and each vessel can have
multiple sensors. This makes it necessary to have a set-up for each
vessel in an application type. The vessel set-up is called the Vessel
Configuration (see page 91).
Project 1 Project 2
Configuration Configuration
1.n x.n
Figure 5-1 Project structures
information from the vessel will be copied from the ‘Projects Common
Files’ map. The changes made in the vessel configuration will be copied
back the common information in the ‘Projects Common Files’ map.
See also the Project The common information contains the following items:
Common tab in the
Explorer (see page 214). Geometry information.
Vessel contours, vessel wireframes and 3D studio models.
Equipment setup.
These common information files are not stored in the project folder
anymore. For existing projects the files are not updated in the project
folder, but are stored in the ‘Projects Common Files’ map. For projects
created with the PDS2000 3.2.0.0 version or later the files are only
available in the ‘Projects Common Files’ map.
Figure 5-2 Select Project window with the option Run the New Project wizard
checked
On the first page a choice has to be made, start from scratch with an
empty project or use an existing project as template. When an existing
project is selected, all relevant files from the existing project are copied
into the new project. The logdata subfolders, grid models, CUBE models,
dtm XML files, logdata file sets and sound velocity profiles files are not
copied to the new project. The new project can then be checked and
changed with the wizard.
As this is a wizard, each dialog window has that will close the
current page and will open the next one. The last page will have .
It is recommended to step through all pages of the wizard. Click on
to stop the wizard at that page without writing the required files
into the project folder. So it is advisable not to click on but to
finish the wizard even without entering data in the pages. That way a
project is made and data can be entered at a later stage.
The Project Configuration With both choices in the previous page, the next page gives the Project
can be modified with Edit > Configuration window. When a project was copied the inputs fields
Project Configuration from contain data from the old project, when an empty project was started
the menu bar or with these fields contain default values.
from the toolbar in the
Control Center. In both cases it is advised to check each possible input and the
corresponding input fields. All possible inputs with their input fields are
detailed below.
5.4.1.1 Description
The project and all computations in the project use the selected units.
These units are only for display purposes; PDS2000 has its own internal
units for logging the data.
5.4.1.4 Formats
Check the items that have to be in the log file name. The order of the
items in the log file name can be changed by using or .
Select the item that has to be moved and use one of the buttons to move
the item upwards or downwards.
Between the different items in the log file name a separator is needed.
Selected for the option Separator the right separator (- _ . ,).
At the bottom the option Replace all dots in the log file name will replace
the dots with a dash (or an underscore when a dash is selected as
separator. This means that all the dots, also in the name of the runline,
will be replaced.
With the log file name will be reset to the default log file setting.
In the Acquisition it is possible to change the name of the log file name. If
the option is active in the Acquisition and a new logdata file is created the
user can specify a different log file name (see page 257).
Historical data can be stored in the ‘Backup’ folder in the project. For all
the file types that are checked in the list a copy is made when a new
logging file is opened. The copy will only be made if the file is changed
after the last backup.
Check the option Keep history of files for Replayer and Editing if the
backups have to be made. The backups are used in the Replayer (see
page 389) and in the Editing (see page 395) when a log data file is
opened. The log data file will use the available files from the backup to
show the information. For instance when the color table is changed after
the data is logged; the color table that was used during the logging will be
used if ‘Color Tables’ is checked for a backup.
To avoid that the backup folder will be overloaded with backups, a
maximum number of days can be set. If a backup is older it will be
removed from the backup folder.
Figure 5-11 Set when the oldest log data files have to be deleted
than because if the number of days is too high then it is possible that the
hard disk is full before the oldest log data files are deleted. A full hard disk
will stop the system.
It is very important to backup the old log data files before one of the
options becomes valid; otherwise the log data files are lost.
5.4.1.9 Options
This page will show options that can be important to display or compute
data.
Show multibeam beams with no bottom detection
In PDS2000 the beams that have no bottom detection get a 0 (zero)
for the beam Z. By default the zero beams will not be displayed in the
views of PDS2000. When the user wants to see the zero beams then
he can check this option.
Lat/Lon on Local Spheroid – Lat/Lon on Satellite Spheroid
The user can select by selecting one of these options which latitude
and longitude are displayed in PDS2000.
This page will show the settings for the GPS time parameters. At the
moment only one setting is available.
st Leap Seconds
From 1 of January 2013 The leap seconds for GPS receivers with a GPS time. The leap
the number of leap
seconds is 16.
seconds are used to correct the GPS time to UTC time.
The leap seconds as set here will be used through PDS2000.
Figure 5-15 Sonar Targets file selection and list with classifications
Select or create in this page the active sonar targets file which can be
used in the Acquisition, Presentations, Replay and Editing.
The sonar targets can be classified. The user can make his own list of
classifications which can be used to classify the sonar targets. It is always
possible to classify a sonar target with a classification that is not in the list.
For more information about the sonar targets see the Sonar Targets view
in the Chapter Views (see page 376).
Select or create in this page the active icon images file which can be used
at the moment only in the Acquisition, Presentations, and Replay.
For more information about the sonar targets see the option Add Icon
Image in the chapter Plan View – Toolbar and Context Menu on page
352.
From the list of application types, select the one that describes the project
the best. The type and number of possible sensors and computations that
By checking Run the configuration wizard the wizard goes over in a menu
where the configuration can be saved. When a name is given, click on
and the wizard will continue with the configuration name and the
vessels page (see below).
Is Run the configuration wizard not checked then by clicking on
the wizard will be finished and the configuration will not be saved. A new
configuration has to be made with the menu option Acquisition > New >
Configuration….
Remote
Vessels which are created on another location, that means for
instance on another ship, can be added or edited. This other ship can
be monitored by reading the data from that ship. To get a connection
with the other ship the Control Center on the remote vessel has to be
running.
Give the hostname or the IP-address of the remote vessel. The port
704 will be used to get the vessel configuration from the remote
vessel. Do not change this port number!!
During the acquisition the sensor data from the remote vessel can be
read, but because of the data load an update rate can be set. Check
the option Use limited data update rate and set the update rate (in the
example above on 5 seconds).
Click on to download the vessel configuration from the remote
vessel.
If the vessel configuration on the remote vessel is changed or the
update rate has to be changed, click on under ‘Remote’ to
download the new vessel configuration or modify the update rate.
5.4.5 Layout
The layouts page shows where the real time modules are displayed. The
module Control Center is by default on the local computer. The
acquisition server and presentations can be on the local computer or on
another computer in the network.
Click on to add new presentations to the list. Select one of the
modules and click on or just click on to go to the Layout
dialog.
If the layout is not running on the local computer (main PDS2000) but on
a remote computer, give the name of the remote computer or select with
the computer in the network.
The name of the layout can be selected. Click on to create a new
empty layout. This empty layout can be filled with views in the Acquisition
or Presentation. It is better not to use the same name for the layout in the
Acquisition and in the Presentation.
The UI (User Interface) profile is always the default. The user can defined
a UI profile where his own toolbar and ‘shortcut keys’ settings are saved.
Click on , give a new name for the profile and make the module
according the wishes of the user. A new UI profile starts always with the
default settings for the shortcuts and the toolbar.
5.4.6 Events
On this page the events can be defined. Three automatic eventing modes
In the real time mode are available, conditions can be set and an event string can be defined.
manually eventing is
possible with F6.
For more detailed information about events see chapter ‘Events’ on page
155.
On the alarms page real time alarms can be defined. The alarms are
related to the configuration and will be active for each vessel in the
configuration.
Vessel specific alarms can be set in the vessel configuration (see page
129).
When an alarm is added a Conditions window, similar to the one in the
Vessel Alarms on page 129, is opened. In this window the alarm can be
defined.
If the condition for an alarm is not known yet leave the alarms page
empty. When an alarm is required on a measurement it is easy to make a
condition in the Acquisition with Edit > Alarms (see page 254). That way,
alarms can be checked immediately.
Click on in the alarms page to close the wizard and once more on
in the ‘Wizard is Finished’ page.
6.1 Introduction
In PDS2000, a coordinate system database is available where for the
most common countries the standard coordinate systems are predefined.
It is also possible for the user to add new coordinate systems to the
database.
The active coordinate system has to be selected in the Project
Configuration (see page 58).
A new coordinate system can be created in the Project Configuration and
in the PDS2000 tab of the Explorer (see page 215). The new coordinate
systems will be stored in a separate database, where all the user defined
coordinate systems are available.
In the PDS2000 tab of the Explorer two different databases are available,
It is not possible to modify the pdsgeodatabase and the pdsusergeobase. The pdsgeodatabase is
the predefined coordinate the database with all the predefined coordinate systems and the
systems. pdsusergeobase is the database with all the user defined coordinate
systems.
In this chapter will be discussed how to select, to create and/or modify a
coordinate system through the Project Configuration. For creating and/or
modifying a coordinate system in the ‘Explorer – General’ the same
dialogs and windows will be used.
Select in the Control Center the menu item Edit > Project Configuration or
click on in the toolbar and select in the Project Configuration window
the option ‘Coordinate System’.
Figure 6-2 New Coordinate System page of the Coordinate System Wizard
Give a name for the new coordinate system and check the option Based
on existing coordinate system if an existing coordinate system has to be
used as a start for the new coordinate system.
Click on to go to the next page of the wizard.
If the option Based on existing coordinate system is checked the next
page is the Select Coordinate System page (see below) to select from the
list an existing coordinate system.
If the option is not checked the user can select a satellite and local
ellipsoid from the list in the Ellipsoids page (see page 75).
Figure 6-3 Select Coordinate System page of the Coordinate System Wizard
The base of an existing On this page the user can select one of the existing coordinate systems
coordinate system is as a base for the new coordinate system. All the coordinate systems as
always both ellipsoids. The defined in both databases (pdsgeodatabase and pdsusergeobase) are
other settings of the available in the list of coordinate systems.
system can be modified.
If an existing coordinate system is selected, click on to go to the
next page of the wizard. The next page will be the Datum Transformation
Parameters page (see page 78).
This page will be opened if the user create a new coordinate system that
is not based on an existing coordinate system.
It is not possible to create Click on to select a satellite ellipsoid and a local ellipsoid from the
a new ellipsoid. list of ellipsoids.
Figure 6-5 Select an ellipsoid from the list of available ellipsoids in PDS2000
On this page only the datum transformations that are possible between
the two selected ellipsoids of the new coordinate system will be available.
If one of the datum transformations is selected, click on to go to
the next page of the wizard. It will depend on the selected option in the
Datum Transformation page (see page 76) what the next page will be.
If the option Use existing datum transformation was checked the next
page will be the Geoid Model page (see page 79).
For the other options the Datum Transformation Parameters page (see
page 78) will be opened.
This page will be opened if in the Datum Transformation page (see page
76) the option New datum transformation is checked. If also the option
Based on existing datum transformation is checked, first the Select Datum
Transformation page (see page 77) is opened before the Datum
Transformation Parameters page will be opened.
Name
Specify a new name for the to be created new datum transformation.
Method
At the moment the only available method is the Bursa/Wolfe method.
Shift X, Y and Z
The translations in the X, Y and Z direction, to translate from the
satellite ellipsoid to the local ellipsoid.
Rotation X, Y and Z
The rotations around the X, Y and Z axis, to rotate from the satellite
ellipsoid to the local ellipsoid.
Scale factor (ppm)
The scale factor between the two ellipsoids in parts per million (ppm).
Prime meridian shift Greenwich (deg)
This option is not available for the Bursa/Wolfe method.
File name
This option is not available for the Bursa/Wolfe method.
Description
The user can enter a short description for the new datum
transformation.
If all the parameters are entered, click on to go to the next page
of the wizard. The next page will be the Geoid Model page (see below).
In this page a geoid model can be selected for the coordinate system.
The geoid model will correct the satellite ellipsoid height to a local height.
The methods available at the moment are:
Belgium hBG03/xyGridLb72
The latest geoid model for Belgium.
DeMin
An old geoid model for The Netherlands.
Denmark DVR90
The latest geoid model for Denmark.
EGM2008
The Earth Gravitational Model 2008 is a spherical harmonic model of
the earth’s gravitational potential.
Grid Model (Grid coordinates)
If this option is selected, a geoid model grid model can be selected
The geoid model grid model with grid projection coordinates (easting and northing).
has to be created in the grid
model editor (see page 524). Grid Model (Satellite coordinates)
If this option is selected, a geoid model grid model can be selected
with satellite ellipsoid coordinates (latitude and longitude in WGS’84).
Norway
For Norway the latest geoid model file is available: HREF2008a.
Null Model
A geoid model with a 0 (zero) correction. This model can be used to
get the GPS antenna height as a local height.
Select an unit that will be used for the projection parameters. Because
this unit is used for the projection it will become the system unit for the
project.
Click on to create a new unit type and the New Unit dialog will be
opened.
Name
Specify a clear name for the to be created unit type.
Meters per unit
Enter the number of meters per one new unit.
Name suffix
Give a suffix for the new unit type, like a ‘m’ for meters.
If the right unit is selected or create, click on to go to the next
page of the wizard. The next page will be the Projection page (see
below).
This page will be opened if in the Projection page (see page 82) the
option New projection is checked. If also the option Based on existing
projection is checked, first the Select Projection page (see page 83) is
opened before the Projection Parameters page will be opened.
Name
Specify a clear name for the to be created projection.
Unit
The unit that will be used cannot be changed on this page. If the unit
has to be changed click on to go back to the Unit page (see
page 81).
Method
In PDS2000 several projection methods are available.
Cassini-Soldner
Hotine Oblique Mercator (A)
Hotine Oblique Mercator (B)
Lambert 1 Parallel
Lambert 2 Parallel
Mercator
RD (is only valid with the unit Meters)
Transverse Mercator
Stereographic
Universal Transverse Mercator (is only valid with the unit
Meters)
The number of parameters on this page will depend on the projection
method that is selected. The values of the parameters False Easting and
False Northing have to be in the unit, which is mentioned on this page.
It is possible that a position calculated on the local grid not match with the
actual X, Y and Z for that point. With a post correction this point can be
moved so it match with the actual grid coordinates. This post correction is
only applied when a calculation is done from the local ellipsoid to the local
grid or vice versa.
On this page two ways to add a post correction are possible, manual or
with a model. The manual post correction is always a fixed shift in all the
X, Y and/or Z coordinates, while with post correction with a model for
each point a different shift can be used.
The models available at the moment are:
Belgium hBG03/xyGridLb72
The latest post correction model for Belgium.
Denmark DVR90
The latest post correction model for Denmark.
HARN
The latest correction model for the United States.
If HARN or OSTN02 is In theory is HARN a correction on the local latitude and longitude and
selected, PDS2000 will correct not on the grid coordinates, but in PDS2000 the only place for a post
the local ellipsoid coordinates correction is on the X and Y coordinates.
before the coordinates are
projected on the grid.
OSTN02
The latest post correction model for England, Scotland and Wales.
In theory is OSTN02 a correction on the local latitude and longitude
and not on the grid coordinates, but in PDS2000 the only place for a
post correction is on the X and Y coordinates.
Figure 6-16 Save Coordinate System page of the Coordinate System Wizard
On this page an overview is given of all the settings for the new
coordinate system.
Click on to check the new coordinate system by entering a
known point in the Geo Calculator (see page 194).
If the new coordinate system is accepted, click on to save the
coordinate system in the group as selected by the user. If one of the
settings in the overview is not right, click on to go back the
relevant page in the wizard to change the settings. It is also possible to
save the coordinate system and use the Edit option (see below) to
change the coordinate system.
Figure 6-18 Select Coordinate System window with only the user defined
coordinate systems
Figure 6-19 Edit Coordinate System window with an user defined coordinate
system
the datum transformation not, then when the coordinate system is saved
with the datum transformation is also changed in the coordinate
systems where the same name for the datum transformation is used.
There is also a relation between the selection of the projection and the
unit. Because the parameters of for instance the Easting and Northing in
the projection are specified in the unit that is selected for the coordinate
system.
7.1 Introduction
PDS2000 always needs a vessel configuration before the Acquisition can
be started. The vessel configuration will contain all the settings which are
necessary to do all the measurements.
Before a vessel configuration can be made a project has to be setup as
discussed in chapter ‘Starting PDS2000’ on page 53.
A new name for the vessel configuration has to be entered. The user can
choose to create a complete new vessel configuration or to use an
existing vessel configuration as template.
When the option Use existing vessel as template is checked, the user can
select from all the vessel configurations that are available in the Projects
Common Files map.
Click on to continue with the wizard. It can take a while before the
next page of the wizard will be opened. The reason is that PDS2000 first
check if the new vessel configuration name exists or not. If the name
already exists an error message will appear and the user can enter a
different name.
The next pages of the wizard will be explained with the separate tab
pages below.
The first page in the vessel configuration is the vessel geometry with the
vessel visualization, vessel draught, vessel turn radius, sea level, vertical
position and the offsets on the vessel.
Visualization mode 2D
Select as 2D vessel contour a vessel contour (made in PDS2000) or a
vessel Wireframe; after that select the file for the selected
A vessel wireframe is a 3D visualization.
drawing of the vessel and
can be used in the 3D
Click on to create a new vessel contour in PDS2000 or click
views in PDS2000. It is on to open the selected vessel contour. In both cases the
also possible to display the vessel contour editor will be opened (see page 95). For a survey
wireframe in the standard vessel usually only a top view is entered.
2D views. These Select the active shape (vessel contour) that will be displayed in the
wireframes should be 3D Acquisition.
DXF files.
Visualization mode 3D
Select as 3D vessel contour a vessel Wireframe or a 3D Studio file;
after that select the file for the selected visualization.
Vessel
Draught
The draught is the distance from the waterline to the deepest point
on the vessel and is always positive. It is used in computations
such as depth below keel.
-X +Y
Port Bow
CRP
X=0
Y=0
Z=0
-Y +X
Stern Starboard
-Z
Bottom
Figure 7-3 Vessel coordinate system
The options in the right top panel of the vessel contour editor are:
Name: Point(x)
Add the X and Y value for point(x) in the vessel coordinate system.
Type
Point. Select this type if point(x) is not a start of line or a start of
polygon.
Start of Line. Select this type if point(x) is the first point of the line. Until
a new start of line or start of polygon is selected all points after this
point will be part of the line.
Start of Polygon. Select this type if point(x) is the first point of the
polygon. Until a new start of line or start of polygon is selected all
points after this point will be part of the polygon. The polygon will be
solid.
The buttons and options on the right side in the editor are:
Add a new point to the contour. The added point comes always at the
end of the list.
Insert a new point above the location of the cursor in the list.
Select the view side of the vessel contour; top, bottom, left, right, front
and back.
,
Zoom Extents, Zoom In / Out.
Click on to save the vessel contour and to close the vessel
contour editor.
7.4 Equipment
Figure 7-7 Navisound Control Center to set the port(s) and check the
communication with the echo sounder
This view will be opened when in the Equipment one of the Navisound
Graphical Trace devices is selected and on or is
clicked.
is grayed out The user selects the required computations from the left window and adds
when a computation is not these with to the list of defined computations. By default the given
possible (anymore) for the computation name will be used and the properties of the selected
chosen application type. computation will be opened.
The properties of the added computations can be opened by selecting the
computation in the defined computations list and click on to
access the properties of that computation.
Multiple conditions can be set on any data source. If one of the conditions
is ‘true’ it will lower the rank of the source, provided automatic switch is
checked in the Data Sources page.
7.7 Guidance
Guidance is a method of assisting a vessel to sail along pre-defined
tracks or towards a pre-defined location or area. The guidance methods
are:
1. Route
2. Runlines
3. Waypoints
4. Design Model
5. Cutter Dredge
6. Work Areas
7. Restricted Areas
8. Vessel Placement
9. Dredge Instruction
10. Object Distance
The number of guidance methods that is available is depending on the
selected application type.
7.8 Tools
The Tools page is skipped in the vessel configuration wizard. If the vessel
configuration is opened outside the wizard always the interval logging tab
is available.
For several applications like (Rope) Excavator, Cutter, Trailing Suction
Hopper, Maggy Survey and Multibeam Survey extra tabs are added to the
Tool page.
The different tabs in the Tools Page are:
Anchor Definition (see below)
Crane Configuration (see page 107)
Cutter (see page 109)
Dredge Logging Settings (see page 110)
Interval Logging (see page 111)
Magnometer Dialog (see page 113)
Pipe Configuration (see page 114)
Production Parameters (see page 115)
Trip Registration (see page 116)
Figure 7-14 Tools page with the Anchor Definition page of the cutter dredge
application
In the Anchor Definition page the anchor definitions for the vessel
(pontoon) and the handling tugs can be specified.
Figure 7-15 Tools page with the Crane Configuration page of the excavator
application
Figure 7-16 Tools page with the Rope page of the rope excavator application
This Tools page is valid for the Rope Excavator application to setup the
crane configuration for a rope excavator with a backhoe.
On the three subpages the offsets for the boom, the rope and the tool
have to be entered. In the Acquisition the angles and/or offsets for the
boom and rope can be calibrated (see page 258).
For more information about this Tools page see the manual for the ‘Rope
Excavator’ application in the manuals folder of PDS2000.
This Tools page is valid for the Cutter Dredge application to setup the
cutter configuration.
For more information about the Cutter see the manual for the ‘Cutter
Dredge’ application in the manuals folder of PDS2000.
Figure 7-18 Tools page with the Dredge Logging Settings page of the
excavator application
This page is to setup the logging conditions for the grid model logging
with a (rope) excavator, cutter or hopper.
In the Logging page the grid model logging should be setup as explained
on page 119. Next to that setup the option Enable grid model logging
should be checked otherwise there is no grid model logging in the
Acquisition.
Figure 7-19 Tools page with the Interval Logging page of a cutter dredge
application
In the Logging page the interval logging format have to be checked before
an interval log file is created (see page 123).
Item to log
Double click on a field and the Select Data window will be opened. In
this window the item from one of the available computations can be
selected.
When an item is selected automatically the row is filled with the default
settings.
User name
Double click on a field and the text in the field can be modified.
This name will be visible in the Interval Logging view in the Acquisition.
Period
At the end of a period the actual value will be logged to the interval log
file.
By default the period is set on 00:01 (1 minute). Select the field and
the user can modify the period.
Reset
The reset is for the methods averaging and cumulating.
Yes. The calculation starts again when a new period starts.
No. The calculation continues after a new period is started.
In the Acquisition the interval logging can be monitored in the Raw Data
view and in the Interval Logging view (see page 302).
When in the Logging page the Interval Logging Format is checked (see
page 123) then the data will be logged in the file xxxx_Interval.log-
yyyymmdd.csv in the Logdata directory of the project, where xxxx is the
vessel name.
Figure 7-20 The Tools page with the Magnetometer Dialog page of the maggy
survey application
This Tools page is valid for the Maggy Survey application to setup the
offsets for a multi-channel magnetometer.
The number of channels that will setup by default will depend on the
magnetometer device driver that is selected in the Equipment.
Figure 7-21 Tools page with the Pipe Configuration page of the trailing suction
hopper application
This page is valid for the Trailing Suction Hopper application to setup the
pipe segments.
In the Pipe Configuration page the configuration for a suction tube with a
bend, an upper pipe, a lower pipe and a draghead (suction head) has to
be setup. When the trailing suction hopper has a starboard and port
suction tube two Pipe Configuration pages are available in the Tools
page.
For more information about this Tools page see the manual for the
‘Trailing Suction Hopper’ application in the manuals folder of PDS2000.
Figure 7-22 Tools page with the Production Parameters page of the trailing
suction hopper application for two bunkers
Figure 7-23 Tools page with the Trip Registration page of the trailing suction
hopper application
How the logging is done is defined in the Logging page. The dialog sets
the file formats, manages log space and sets the log conditions. The
layout of the Logging page depends on the selected application type and
on the selected logging formats.
On top of the page it is possible to change the log directory. Select an
existing directory or enter in the box a new log directory. This is same
option as in the Log Files page of the Project Configuration (see page 59).
Figure 7-25 Log File Index in the logging page for PDS2000 format
Index file after logging means that direct after the log file is closed an
index file of the log file is created. This will save time when the log file is
opened in for instance the Editing.
Figure 7-26 Backup log in the logging page for PDS2000 format
Backup log becomes available when the option Use backup log directory
is checked in the Project Configuration (see page 59). Check the option
Enable Backup log to log the PDS2000 logdata file also in the backup log
directory which is specified in the Project Configuration.
File name: Vessel name[application type]_runline name-date-time.PDS
The runline name is for a (rope) excavator application replaced by the
project name and for the dredge applications by the trip number.
This file name mentioned above is the default file name. With the option
user defined log file names in the Project Configuration a user-defined file
name can be defined (see page 59).
From PDS2000 version 3.6.0.0 onwards, the sonar image, side scan and
snippets data in the PDS2000 log file is compressed to reduce the size of
the log files. When this PDS2000 log file is opened in an earlier version
(3.5.0.x or older) the data of the sonar image, side scan or snippets
cannot be opened anymore!
From multibeam data all the pings will be logged in the PDS2000 format,
even the pings that are out of order. The pings with a bad time stamp will
only be logged when they are newer than the ping before and when they
meet the data rate criteria.
Select the grid model file name. If no file exists click on and give a
new file name. Select one or more data types and enter a cell size.
The grid model is filled with data from the added device in Data for grid
model logging.
File name: Name of the grid model.DTM
The tolerance is the minimum difference of the Z-value with the previous
Z-value. If the difference is more than the tolerance (e.g. 0.05 m) the data
point is added to the file.
The width of a sway is defined as 100%. By setting a minimum distance
(e.g. 10%) a point at every 10% of the width of the sway is added to the
file.
File name: Vessel name[application type]_runline name-date-time.XYZ
This is the same type of menu as for the PDS2000 Grid Model (see page
119).
File name: Name of the Grid Model.DTM
By setting the sampling rate the logging interval is defined (e.g. 30 sec).
File name: Vessel name[application type]_year_month_day.TRK
Figure 7-32 Grid model input for backscatter grid model logging
This is the same type of menu as for the PDS2000 Grid Model (see page
119) but with an extra layer for the backscatter data.
The old backscatter grid models (created with the Sidescan sonar format
in the PDS2000 versions before 3.4.0.0) can still be used for logging the
side scan sonar or snippets data). Only in these old grid models is no Z
Average available to show the data in a 3D view.
File name: Name of the Grid Model [Backscatter-Model].DTM
Check the option Reduce on nadir filter if not all the data has to be
logged. The data that is rejected by the nadir filter (see page 328) will not
be logged.
Figure 7-34 Backup log in the logging page for S7K format
Backup log becomes available when the option Use backup log directory
is checked in the Project Configuration (see page 59). Check the option
Enable Backup log to log the S7K file also in the backup log directory as
specified in the Project Configuration.
At the moment the following records, if available, will be logged:
1003 - Position
The position is the position of the vessel reference point.
The height is the height of the vessel reference point
relative to sea level when height source is ‘None’,
otherwise the height is relative to chart datum.
1008 - Depth
Depth of the vessel reference point relative to sea level.
1010 - 7K Sound Velocity Profile
1015 - Navigation
The position is the position of the vessel reference point.
The height is the height of the vessel reference point
relative to sea level when height source is ‘None’,
otherwise the height is relative to chart datum.
1016 - Attitude
7000 - 7K Volatile Sonar Settings
7004 - 7K Beam Geometry
7006 - 7K Bathymetry Data
The along track and across track values are related to the
vessel reference point and not to the sonar reference
point. The depths are relative sea level when the height
source is ‘None’, otherwise the depths are relative chart
datum.
7007 - 7K Backscatter Image Data (Side Scan Data)
7008 - 7K Beam Data (Snippets Data)
7009 - Vertical Depth
7027 - 7K Bathymetry Data new style
The along track and across track values are related to the
vessel reference point and not to the sonar reference
point. The depths are relative sea level when the height
source is ‘None’, otherwise the depths are relative chart
datum.
7028 - 7K Beam Data dB (Snippets Data)
The default and standard format is FAU 1 with the beam angle. There is
no difference in the file name between both formats.
File name: Date_time_1_vessel name_runline name.FAU
The number 1 mentioned the first multibeam system from the equipment
list. If more multibeam systems are logged simultaneously then the
second gets a 2, the third a 3, etc.
When the number of beams is changed during the logging the actual file
will be closed and a new FAU file will be created. In a FAU file the number
of beams is placed in the header of the file.
At the moment some fields in the header of the file are not filled in due to
varies reasons. The fields that are not filled are TimeOffset,
SensorValsEdited, SwathNtPosJump, MaxNonLinearity, Major, Minor,
Autoflags, RotRectValid and BB_Tilt. All these fields will have a value 0.
Figure 7-36 Uncorrected or fully corrected multibeam data selection for the
GSF logging
Select Uncorrected when the raw multibeam data has to be logged in the
GSF file. Select Fully Corrected when the corrected multibeam data has
to be logged in the GSF file. The corrected multibeam data in the GSF file
is computed according the multibeam xyz computation in the multibeam
device data.
File name: Date_time_1_vessel name_runline name.GSF
The number 1 mentioned the first multibeam system from the equipment
list. If more multibeam systems are logged simultaneously then the
second gets a 2, the third a 3, etc.
Below is a short explanation of the current implementation of GSF File
Logging in PDS2000:
The GSF logging is based on a modified version of the GSF 2.09
library provided by SAIC.
The logger uses CF_MBXYZREL PDS data blocks as a starting point.
Only fully computed results are stored in the GSF File.
Sonar specific data is only written for sonar models: 8101, 8111, 8124,
8125, 8150 and 8160.
Multi-head sonar data is logged into two separate GSF files.
Single beam sonar’s are not supported.
The following GSF types are written to the GSF file:
GSF header
GSF Processing Parameters
GSF Sensor Parameters
GSF Comment
GSF MB Ping
GSF Attitude
in place. The checks for that system are 1% on the system disk with a
minimum of 500 MB and 100 MB on the data disk.
The logging will stop when one of these two limits is reached. One
hour, 30 minutes and 15 minutes before these limits are reached a
message will be reported.
Minimum free disk space warning
Give the amount of disk space that should be kept free at all times, in
MB.
Allowed log space warning
The maximum space to be used by PDS2000 for logging purpose, in
MB.
The log space management system is not active when the minimum free
disk space and/or the allowed log space are zero.
PDS2000 will generate a warning signal when the limit for the minimum
free disk space or the allowed log space is reached and it will continue to
log the data.
A maximum size of the log file can be set. This means that when the file
exceeds the file size a new log file will be created.
Another option is by setting a time limit on logging in one file. If the time
limit is reached a new log file will be created.
On this page the simulation parameters can be set. The simulator is build-
in for training purposes.
Vessel position
Enter the grid position where the simulator will start.
Heading
The initial heading of the vessel.
Vru
Maximum values of the VRU simulator, Max. Heave in project units,
Max. Roll and Max. Pitch in degrees.
Depth
For each channel a depth value. Depth channel 1 is also used to
simulate a multibeam echo sounder.
Speed
Initial speed of the vessel. Depending on the chosen project units, in
knots or meters/second.
Simulate using runlines
Check Use Runlines to have the simulator running over the runlines.
Check Automatic Mode and the simulator will select the next runline
automatically.
Multibeam noise factor
Adds noise to the simulated multibeam swath, giving a more realistic
effect.
Figure 7-41 Alias page in the vessel configuration with an alias for NMEA
GGA
Aliases are used to give multiple sensors of the same type distinguished
names. E.g. when there are two GPS sensors both using the device
driver ‘Standard NMEA GGA’, these sensors will have the same name in
the program. To give those sensors aliases such as ‘GPS1’ and ‘GPS2’ it
is more clear to the user.
Aliases are used throughout PDS2000 wherever the device name comes
forward.
The alarms that can be set in this page are vessel specific or device
specific alarms and will be valid only for the vessel that is setup in this
vessel configuration.
Check the option Enable Alarm when the alarm has to be active.
Check the option Sound Alarm when the alarm should give a sound when
the alarm becomes valid. Each Severity (Low, Intermediate or High) gives
a different sound for the alarm.
With or a Condition dialog will be opened where the
selected condition can be modified or added. In this dialog an attribute
from the equipment or computation list can be selected and a condition
with a value for this attribute can be defined.
The vessel alarm file will be placed in the ‘Explorer - Project’ (see page
219), but cannot be edited through the explorer. It is only possible to
modify a vessel alarm file in the vessel configuration.
8.1 Introduction
Guidance is a method of assisting a vessel to sail along pre-defined
tracks, towards a pre-defined target or in/out pre-defined areas.
The number of guidance methods available in PDS2000 depends on the
application type that is selected. At the moment the different guidance
methods shown below are available through the different application
types:
1. Route (see page 132). A route is a sequence of points connected
with lines. The lines are straight lines between tangent points, or
circle segments when a center point is given. Routes are often used
in rivers and channels, but can also be used to follow a pipe or a
cable.
2. Runlines (see page 138). Runlines are straight lines or route wing
lines which can be grouped in blocks. A number of block methods are
available.
3. Waypoints (see page 141). A waypoint is a location towards the
vessel is moving.
4. Design Model (see page 143). A selection can be made between a
3D model and a grid model as guidance for dredging.
5. Cutter Dredge (see page 146). A work route for a cutter dredger.
6. Work Areas (see page 147). A work area is an area where the work
takes place. A work area can be a rectangle or a polygon area.
7. Restricted Areas (see page 148). A restricted area is an area where
it is not allowed to come or work. A restricted area can be a polygon
or an area on both sides of a route (e.g. a pipe or a cable route).
8. Vessel Placement (see page 149). A vessel placement is a location
with a heading towards the vessel is moving.
9. Dredge Instruction (see page 151). A dredge instruction gives the
dredge area with the depths for the dredger.
10. Object Distance (see page 152). Generate alarms when distance to
selected object become in alarm range.
Each method has its own definitions and computations and can have
many guidance files. In the Acquisition the user can change from
guidance file.
When a new route is created the user can select from three different
types of route; a generic route, a pipe route or a cable route. The generic
route is the standard route with Eastings and Northings. The pipe / cable
route has next to the Eastings and Northings also a Z-value or a depth.
This way a pipe / cable route can be used to show a pipe / cable with the
right depth.
The route editor can also A route is a number of points connected by lines. The route points can be
be opened in the Explorer - either tangent points (TG) or center points (CP). Tangent points can be
Project with the Track connected with a straight line or with a curve.
Guidance Routes option
(see in the ‘Project On the route page a route file can be selected and edited or a new file
Database’ on page 223). can be created. This opens automatically the route editor.
To check the fit of the curve against its adjacent tangent points. In
case a curve fit is not possible warnings are written in the ‘Status’ field
of the list.
From the menu bar some extra functions can be selected:
Route > Properties…
Figure 8-3 Route Properties for the standard route (left) and for the pipe /
cable route (right)
Start KP
Enter a Start KP for the (pipe / cable) route.
Pipe Diameter
Enter a pipe / cable diameter for the pipe / cable route.
KP calculation mode
Select the mode for the KP calculation, Grid distance or True
distance.
Grid distance. Calculate a distance between two tangent points on
the Easting – Northing plane.
True distance. Calculate a distance between two tangent points on
the local ellipsoid.
First curve turn
Select the direction of the first curve in the route, Clockwise or
Counter clockwise.
Manual KP handling
When a tangent point on the route is defined with a manual KP, this
option becomes valid.
in the import file is not a manual KP. Select then in the import wizard
‘KP’ for the KP column and ‘Man KP’ for the column with ‘1’.
Route > Export
An ASCII file with the route information will be created.
Figure 8-5 First page of the ASCII Import Wizard for a route
If an import configuration The ASCII file with the route information has to be selected. If the file is
file is used, click on selected the user can use an existing import configuration file or continue
to import the with the wizard to configure the import. If the user continues with the
ASCII file. wizard there is a possibility to save the import configuration file, so the
next time the configuration file can be used to import a route. Click on
to continue with the import wizard.
Figure 8-6 Second page of the ASCII Import Wizard for a route
Select the file type for the ASCII import file; the data in the file is delimited
with a character (like a comma, a tab, a space or user defined) or the data
is presented in fixed columns. Click on to go to the last page of
the import wizard.
On the last page of the import wizard the delimiter and the columns have
to be defined.
Delimiter
Select a character as delimiter between the data columns. The options
are comma, tab, space or custom. With custom a user defined
character can be added.
Extra
The extra option is used to skip the header lines of the ASCII import
file. First check the option before a number can be filled in.
Select Column Names
Click with the right mouse button on a column and select one of the
available field names for the selected column. On the right top side of
the page a column number will be added to the selected field name.
If the right delimiter is selected, the right number of header lines is
skipped and all the columns are selected, which are needed for the route,
click on to import the ASCII file.
If on the first page of the import wizard the options ‘Save configuration as’
is checked and a file name is given, the settings made on the second and
third page of the wizard will be saved in the import configuration file and
can be used the next time when an ASCII import for a route has to be
done.
The runlines editor can A runline can be a straight line or a route wing line. It is possible to have
also be opened in the several groups of runlines in a runlines file.
Explorer - Project with the
Runlines option (see in the On the runlines page a runlines file can be selected and edited or a new
‘Project Database’ on page file can be created. This will automatically open the runlines editor (see
222). page 139).
Lead-in Lines
When the option Show lead-in lines is checked, PDS2000 computes a
lead-in line from the current vessel position to the start point of the
next runline. The lead-in curve is based on the lead-in line length and
the ‘Vessel turn radius’ as set in the vessel geometry (see page 93).
The lead-in line length is the length of the straight line that is in line
with the next runline.
Check Use lead-in lines to compute off-line distances; distance to go
and traveled distances along the lead-in line.
Next line selection
In the next line selection the runline retrieval method needs to be set.
Normal. Each subsequent line is taken from the list with as start and
end of line the coordinates as defined in the runlines file.
Reverse. Each subsequent line is taken from the list with as start and
end of line the end and start coordinates.
Alternate. Each time a next line is selected from the list, the start and
end coordinates are alternately as normal or reversed. This allows
sailing line-by-line in a continuous way.
Enter or choose a number of lines to skip each time a next line is taken
automatically.
Check the option Automatic next line and click on to set a
condition to discard the current line and goes to the next runline in the
list. The condition editor is equal to the one described on page 104.
Online condition
This condition is used for logging purposes. Check the Offtrack limit
and give a value for the offtrack limit. When a vessel is further away
from the selected runline than the offtrack limit, logging stops if the
appropriate check marks are set in the ‘Condition Check’ in the
Logging page of the vessel configuration (see page 126).
For each runlines file one or more line types can be defined in this editor.
For blocks of lines the first line is entered and the computation of the
coordinates for the other lines is done automatically.
Click on under the ‘Full Name’ to create a new set of runlines.
Select from the Add Runline window a runline type to add. Each selection
gets a different line entry window on the bottom left-hand side of the
runlines editor.
Single line (rectangular)
Enter a line name, a line number and the start and end coordinates.
Single line (polar)
Enter a line name, a line number, the start coordinates and a line
length and bearing to the end coordinates.
Parallel lines (rectangular)
Enter a name for the runlines, the start and end coordinates for the
first line, a start number for the first line, the number of lines, the
number interval and the line spacing (= the distance between adjacent
lines).
Parallel lines (polar)
As above but instead of end coordinates for the first line a line length
and bearing to the end coordinates.
Grid
Enter a name for the runlines, choose an origin where the grid box
starts, the coordinates of the origin, the width and height of the grid
box and a rotation for the grid box.
Enter the start numbers, the number interval and the line spacing for in
the X and Y direction of the grid box.
Perpendicular lines
Creates a block of lines perpendicular to a centerline.
Enter a name for the runlines, for the centerline the start and end
8.4 Waypoints
The waypoints editor can Waypoints are target points or points of interest. Around a waypoint
also be opened in the tolerance circles can be drawn. In the Acquisition a wayline can be drawn
Explorer - Project with the from the current vessel position to a waypoint, indicating distance and
Waypoints option (see in bearing from the vessel to the waypoint.
the ‘Project Database’ on
page 224). On the waypoints page a waypoints file can be selected and edited or a
new file can be created. This will automatically open the waypoints editor.
Click on to add a new waypoint to the list. The details of the new
waypoint are displayed in the upper right corner of the waypoints editor.
Name
Enter a logical name for the waypoint. By default the name will be the
‘Waypoint’ with between brackets the date and time when it was
created.
Default tolerances can be set. For a new waypoint the user defined
tolerances in the top right corner are replaced by the default tolerances
set in here.
Options > Electronic Chart…
Select a PDS1000 electronic chart as background.
Options > Grid Properties…
Select the grid to be shown in the plan view: Grid Crosses, Solid Line
Grid, Dotted Line Grid or Scale Bar. The grid can be with or without a
grid annotation.
Options > Import from ASCII…
An ASCII Import Wizard will be started to guide the user through the
import settings. This import wizard is the same type of import wizard
as discussed on page 136. The ASCII file should contain at least a
waypoint name, the X and Y co-ordinate. The two tolerance circles are
optional.
Right clicking on the plan view window opens a context menu with the
zoom functions, which are also on the right side in the editor.
Z Shift
When checked, an offset to the Z-value of the design model will be
applied.
Z lower limit
When checked, the new Z-value for the design model.
Underdredge limit
The value is an offset perpendicular to the design model and is shown
in the different Profile – Realtime Design views just as an indication
(see ‘Profile – Realtime Design Antwerpen View’ on page 367). At the
moment no alarm is set or checks are done with this limit.
Overdredge limit
Same as for the ‘Underdredge Limit’.
After the check the errors are visible in the plan view of the editor. Zoom
in to one of the errors and click on the error to open a Fix window to solve
the error. After the error is fixed, click on again to check if the error
is gone. Continue to solve all the errors. Click on or to save
the model, this is only possible when there are no errors left. As
mentioned in the info box the non-flat and overlapping areas cannot be
fixed.
If an error is fixed but the result is not what the user wants then with
the modification made to the error can be undone.
The 3D model can be exported to a 3D-DXF file. When it is not possible
to solve all the errors in the model, like the non-flat and overlapping
areas, the only option is to export the data to a DXF file and try to solve
the errors outside PDS2000 e.g. in AutoCAD.
Right clicking on the plan view window opens a context menu with several
functions. The most of these functions are also in the toolbar.
Zoom functions ( )
Zoom In, Zoom Out, Zoom Window and Zoom Extents.
Pan ( )
Toggles the pan option on/off. When pan is active, keep the left mouse
button in and move the mouse to pan through the data.
The pan option can also be switched off by clicking on the right mouse
button.
The route editor can also A cutter dredger uses a work route as guidance. A work route is the same
be opened in the Explorer - as a route in ‘Route’ on page 132.
Project with the Track
Guidance Routes option Work route
(see in the ‘Project On the cutter dredge page a (work) route file can be selected and
Database’ on page 223). edited or a new file can be created. This opens automatically the route
editor (see page 133).
Work offset
An offset can be given to the work route. This offset route becomes
then the guidance route for the cutter dredger.
Swing limits
Angular swing limits
The maximum swing of the cutter to port and starboard side in
degrees.
Use also distance limits
Check this option to make it active.
A work area can be a dredge or dump area, and each area has a name
that can be descriptive and shown in the plan view.
With the option Only allow In the Acquisition one or more work areas can be selected and becomes
single area selected in the the active work area(s). A line is drawn from the current vessel position to
Acquisition only one work the active work area or the center of active work areas. That line stays on
area can be selected and the vessel’s tracking point while the vessel moves, guiding the vessel
will be active. toward the active work area.
The work areas editor can A work areas file can be selected or created with . Different work
also be opened in the areas can be kept together in one work areas file in the work areas editor.
Explorer - Project with the There is no limit to the number of areas in one file.
Work Areas option (see in
the ‘Project Database’ on Click on to create a new work area. Two work area types are
page 224). available:
Polygon Area
Select an existing clipping polygon from the project as work area.
Rectangular Area
Enter a name, the center coordinate, the width, the height and the
rotation of the work area.
Alternatively, work areas can be created by importing ASCII files, click on
and converts these files to work areas. The ASCII file should be a
comma separated file with the format <Name>, <Center X>, <Center Y>,
<Length>, <Width>, <Rotation>.
The placement points A vessel placement is a target location with a heading. In the Acquisition
editor can also be opened a line will be drawn from the current vessel position to a placement point,
in the Explorer - Project indicating distance and bearing from the vessel to the placement point.
with the Placement Points
option (see in the ‘Project On the vessel placement page a placement point file can be selected and
Database’ on page 222). edited or a new file can be created. This will automatically open the
placement points editor.
On the left side of the dredge instruction editor all the information can be
added or modified. This information will be shown directly in the plan view
on the right side.
This option is available for the (rope) excavator and grab crane dredge
applications will only work when 3D shapes of the crane are used.
Figure 8-25 Views in the Acquisition that have an alarm frame with text
9.1 Introduction
Before events can be viewed in the Messages – System Messages view
in the Acquisition, the event and the conditions to show the event have to
be defined. At the same time when an event is shown in the Messages –
System Messages view the information is logged in the PDS2000 log file.
The Events page can be opened in two different ways:
1. Through the New Project wizard. Select File > New Project… from the
menu bar of the Control Center to open the wizard (see page 68).
2. With Acquisition > Configure from the menu bar or with on the
toolbar of the Control Center the Configuration window will be opened.
Click on the tab Events to open the Events page.
On this page the eventing interval, the conditions and the event definition
have to be set.
The option Enable eventing has to be checked if the user wants events in
the Acquisition.
When the option Follow Logging Enable is checked the event logging is
started and stopped with the PDS2000 logging. This option overrules the
9.2.1 Mode
Select one of the three interval modes for the eventing:
Time
Set a time interval, e.g. 60 sec. Every 60 sec an event is generated.
Distance
Set a distance interval, e.g. 100 m. Every 100 m sailed an event is
generated.
Line
Set a line distance interval, e.g.100 m. Every 100 m sailed along a
runline, a route or a wayline an event is generated.
9.2.2 Conditions
Click on to define the conditions for the eventing.
In this example select for ‘Start character’ 23 for the X or 40 for the Y
and for ‘Field length’ in both cases 12 to add the two data items.
For the explanations of the other options in the fixed field see the ‘Field
Selection’ below.
Click on to select from the Select Data dialog the data item for the
relevant data source.
Set a start number for the first event number and set the number
increment to the next event numbers. If the counting of the event numbers
is decreasing, check the Count down checkbox.
10.1 Introduction
When PDS2000 is started always the Control Center will be opened.
From the Control Center all modules of the program can be started.
Before the Control Center of PDS2000 is started PDS2000 will do a check
Help Topics
It will open the Help file of PDS2000 which contains a copy of all the
PDS2000 manuals. The Help file can also be open with the F1-key.
Download PDS2000 Updates
The FTP site of PDS2000 will be opened to download the latest
version of PDS2000.
PDS2000 On The Web
The PDS2000 site on the RESON website will be opened.
PDS2000 On Twitter
The PDS2000 twitter site will be opened where the latest information
of PDS2000 is available.
View Release Notes
The release notes of PDS2000 will be opened in the default PDF
reader.
Send Feedback To RESON
Via email
The default email editor will be opened to send an email to the
helpdesk of PDS2000 (pds2000@reson.nl).
Via the web
The Support page on the RESON website will be opened.
Show Support Phone Numbers
The telephone numbers for the PDS2000 support in The Netherlands
and for the RESON support in Denmark and USA will be given.
External Clock Synchronization
Check this option to activate the clock synchronization.
With double click on in the taskbar the Clock Sync window will be
opened. This is the same window (Clock Sync – System messages) as
when on is clicked in the Clock Synchronization window (see
page 166). The only difference is that in the menu bar the option Edit is
added.
Click with the right button of the mouse on and a context menu is
opened with the options Show and Exit. With Show the same window as
with the double click on the icon is opened and with Exit will disappear
from the taskbar but the clock synchronization will not be inactivated.
10.5 Interfacing
On the Equipment page an IO port has to be set when a sensor is added
to the device list (see page 96). When in the Equipment page on
is clicked only the communication ports for that specific
device driver are available and not all possible interfaces can be selected.
In the Interfacing window which can be opened in the Control Center all
the different communication ports are available.
Select from the menu bar the option System > Interfacing or click on in
the toolbar to open the Interfacing window.
By default only the serial communication ports COM1 – 16 are displayed
in this window. If in the Equipment page for a specific device driver
another communication port is added then this new communication port
will be visible in the Interfacing window.
10.5.1.1 XSE
This type of communication port is only used for an Elac system. A
network port has to be entered and on the right side in the Interfacing
page an IP-address has to be entered for the XSE server.
10.5.1.2 Socket
This type of communication port is a network connection and can be used
for receiving and/or sending data through a network connection.
The ‘empty’ mentioned above in the table can also be replaced by ‘host IP
address’ when only the data from the host address has to be accepted.
10.5.1.3 Serial
This type of communication port is a serial connection, called COM port,
and can be used for all the sensors with a serial connection.
If more than one COM port has to be used, serial extender cards have to
be installed. See in the chapter ‘Installation’ on page 17 for more
information.
The Base Port Number is by default set on the right number (2020), do
not change this!!
Select the sensor type that matches with the selected device.
See for a detailed explanation the manual Interface Setup chapter Odom
ES3 (the file Interface Setup.pdf in the folder ‘manuals’).
10.5.1.5 RGL
The RGL communication port is a network connection and is specific for
the laser scan devices Riegl and Riegl Vline. The port cannot be selected
it will automatically selected when one of these laser scan types is
selected as device.
Host Address
The IP address is always from the Riegl laser scan.
10.5.1.6 R7KI
The R7KI communication port is a network connection and is specific for
the RESON SeaBat 7K systems. This communication port is identical with
the Socket port as described above.
Host Address
The host is always the 7K data server and, when it is running on the
same computer as PDS2000, the address is 127.0.0.1. If the 7K data
server is running on another computer then the address is the IP
address of the other computer.
Protocol
The protocol has to be UDP/IP.
This port can be used for all 7K drivers that need information from the 7K
data server, like the multibeam, the side scan sonar and the snippets, or
send information to the 7K data server, like the output to 7K.
10.5.1.8 OPC
The OPC communication port is a kind of network connection. The port
cannot be selected it will automatically selected when an OPC device is
selected.
Figure 10-13 OPC server has to be selected for the OPC communication
10.5.1.9 NCC
This type of communication port is needed for the Navisound echo
sounders. The port is a dummy port which is used in PDS2000 to
communicate with the Navisound. The actual port and settings are
defined in the Navisound Control Center (see page 99).
The NCC port is automatically created when a Navisound echo sounder is
selected in the Equipment. So it is not necessary to add a NCC port, but
when by accident the port is deleted while the Navisound is already
selected then the port can be added. It is not needed to define the baud
rate, etc. because this will be done in the Navisound Control Center.
There can be only one NCC port in the Interfacing available.
10.5.1.10 Edgetech
The Edgetech communication port is a network connection and is specific
for the Edgetech side scan sonar system. This communication port is
identical with the Socket port as described above, only the Local port and
the multicast are disabled.
10.6 Import
On several places in PDS2000 data files can be imported and converted
to information that can be used in PDS2000. The different import
possibilities will be discussed in the different modules of PDS2000.
The import in the Control Center is made to convert data files to PDS2000
log data files.
If the Select Tool dialog is
not visible, select File > Select from the menu bar the option Tools > Import or click on in the
New from the menu bar or toolbar to open the PDS2000 Import Utility. When the PDS2000 Import
click on in the toolbar Utility window is opened it will be an empty window with the Select Tool
to open the dialog. dialog on top of it.
Select in the Select Tool dialog the type of import for which a new import
configuration has to be created or select an existing import configuration.
An existing import configuration can also be opened with File > Open from
the menu bar or with from the toolbar.
If a new import configuration has to be created it is also possible to use
an existing import configuration file as a base. Check the option Copy
from existing config file and select the file that has to be used as a start.
At the end of the configuration the new import configuration can be saved
by clicking on in the toolbar or select File > Save As… from the menu
bar.
If there is already an import configuration that can be used with the import
files check the option Open existing and select the right import
configuration.
At the moment the PDS2000 Import Utility can import the following data:
Single Beam XYZ (see below)
XTF (see page 183)
S7K (see page 184)
SZ (see page 186)
Simrad EM3000 (see page 187)
This page will appear for all three formats. The number of columns on this
page depends on the selections in the pages before.
Click on to add a data file to the file selection. If in the runline
options page (see page 176) the option Pick runline from project is
checked and/or in the ASCII file options page (see page 176) the option
Timetag generation from start time and ping rate is checked, an Edit
Import File Settings window will be opened after the selection of the
file(s).
Import file
The added data file from the File Selection page.
Runline File
Select with an existing runline from the project.
This option will be shown if the option Pick runline from project in the
run line options page is checked (see page 176).
The next three fields will be shown if the options Timetag generation from
start time and ping rate in the ASCII file options page (see page 176) is
checked or the ASCII (X,Y,Z) data file with or without an ID is selected.
Start date
Click on next to the date and select in the calendar the right start
date.
Start time
Set the right start time of the first XYZ in the data file. Select the hours,
minutes or seconds with the mouse, type in the right value or use the
up and down arrows to change the numbers.
Ping rate (Hz)
Set the frequency for the XYZ data; how many times per second is the
XYZ data presented in the data file.
Click on in the Edit Import File Settings window to go back to the
file selection page. With in the file selection page, the Edit Import
File Settings window can be opened to check or modify the import file
settings. will only be active if a runline, date or time can be set.
If all the data files are added and the runline, date and time are set, click
on .
To click on behind one of the options will start the wizard for the right
settings of the selected option. It depends on the selection of the ASCII
data file and on the selections made in the pages before which parsing
options will be available on this page.
The different parsing options can be:
1. Parsing Of Date, Time, X, Y, Z for Channel 1 or Channel 2
2. Parsing Of X, Y, Z for Channel 1 or Channel 2
3. Parsing Of X1, Y1, X2, Y2 For Runline
Option 1 and 2 starts with the parsing of the XYZ data (see below). After
that option 1 will continue with the parsing of the date and time (see page
182) and option 2 will be finished. Option 3 is a separate parsing option
(see page 183).
If the parsing of one of the options is finish a checkmark ( ) will be
placed before the option. If all the parsing is done will become
active. Click on and the first page of the import utility will be
opened again.
On this page the settings for the XYZ data are set, so that on the next
page the right columns with XYZ data can be selected.
File
The filename displayed in the file box is the first file from the file
selection page. At the bottom, in ‘Preview Data’, the data of that file is
shown.
Original data type
Delimited. Check this option if the data is separated with a delimiter,
such as a comma, a tab or a space.
Fixed Width. Check this options if the data is aligned in columns with
spaces in between.
Skip lines
Check this option if the first line(s) of the data file(s) contains
information that is not runline data or XYZ data.
Give a number for the number of lines that have to be skipped.
Line ID
Give an ID for the lines that have to be extracted from the data file. If
an ID is given, the preview data will change and will only show the
lines in the data file with the given ID. In the example shown above,
the ID for the XYZ data is ‘EC’ and for the runline ‘RT’.
If all the settings are set, click on to go to the second page for
parsing XYZ data.
This page will appear when Delimited is checked on the first page of
parsing XYZ data. If Fixed Width is checked the page will be similar as
the page for parsing the date and time, only the sub items will be X, Y, Z
and optional date and time (see page 182).
On this page the delimiter and the columns have to be defined.
Delimiter
Select a character as delimiter between the data fields. The options
are comma, tab, space or custom. With custom a user defined
character can be added.
If in the ASCII file options Fields
page (see page 176) the If a column is selected in ‘Select Column Names’, a column number
option Timetag parsing is will be added to the selected field name.
checked, also the date and
the time column have to be Select column names
selected. Click with the right mouse button on a column and select one of the
available field names for the selected column.
If all the columns which are necessary for the import are selected, the
button will become active (only for parsing XYZ data). Click on
and go back to the first page of the import utility.
If the parsing contains a date and time, the ASCII Parsing Wizard will
continue with parsing date and time (see below).
The locations of the year, month and day in the date column are defined
with a start and end position in the column.
Double click in ‘Column For Field Name:’ on year, month or day and an
edit window will be opened.
Start Position
Set the start position of the item; in the example above the month
(here 02) starts at position 5.
Stop Position
Set the stop (end) position of the item; in the example above the
month (here 02) stops at position 6.
Factor
The multiplication factor should be 1.
Offset
An offset can be added to the selected item value to get the right
value. If for instance the year is presented in the data file as 05, then
with an offset of 2000 the year becomes 2005.
If the year, month and day are set, click on to go to the page for
parsing the time. This page works similar as the page for parsing the
date, only here are the items hour, minute, second and millisecond. If the
hour, minute and second is set (millisecond is optional) becomes
active.
Click on to select the XTF file for the import. It is possible to add
more XTF files before the import is started.
Check one of the options Import sidescan data, Import snippet data or
Import tide data if side scan data, snippets or tide data is available in the
XTF file(s) and have to be imported.
Click on to start the import of the XTF file(s).
Click on to select the S7K file for the import. It is possible to add
more S7K files before the import is started.
For bathymetry data at least the following records should be logged in the
S7K file:
For Position :1003; or 1015
10.6.3.1 Offsets
When in the S7K file(s) the record 7030 is missing, automatically an
offsets dialog will be opened. The offsets for the Position, Attitude,
Multibeam and Sealevel can be added manually or loaded from a file.
In the file all the items in the dialog should be mentioned with the terms as
displayed below in the text file.
Check the option Apply to all files when for all the S7K files in the import
the same offsets have to be applied.
Click on to select the ALL files for the import. It is possible to add
more ALL files before the import is started.
Check the option Apply imported sound velocity profile to PDS2000 file
when the imported sound velocity profile data from the ALL file has to be
applied to the created PDS2000 logdata file. When more ALL files have
the same sound velocity profile only one sound velocity profile file is
created in PDS2000.
Click on to start the import of the Simrad EM3000 file(s).
Survey data
A XYZ file have to be selected with . From this XYZ data file a grid
model will be generated and that grid model will replace the grid model
in the plot template.
The Name Prefix is automatically generated when the XYZ data file is
selected. The user can modified the prefix if he wants. The prefix
name will be used in the plot file and in the DXF file.
Check the option XYZ file contains Depths when the Z values in the
XYZ data file are depths. This is necessary because the depths in the
grid model are negative heights. So the Z values from the XYZ file get
a minus sign when the option is checked.
DTM
The generated grid model will Set the cell size for the grid model that have to be generated from the
be store with the name of the XYZ data file. The cell size doesn’t have to be the same as in the XYZ
XYZ file in the project. data file.
A Batch Plot setup file (BPP file) can be opened. This file contains all
the information to set all the items in the Batch Plot dialog.
Saves the setup and specify the name for the BPP file.
Prints the generated plot to the printer that is selected in the Print
Setup dialog.
Creates a plot file with the prefix name, date and time in the selected
plot project.
Creates a DXF file with the prefix name, date and time in the project
folder.
Closes the Batch Plot dialog without saving the setup in a BPP file.
Figure 10-33 Quick Profile Plot with a plot project and a plot template selected
In the tabs Filesets, DTM, Design and Text the right files for the profiles
plots can be selected and also the right text can be specified.
Under Select Runlines the runlines files or a set of runlines can be
selected which will be used to generate the profile plots.
10.8.1.1 Filesets
If in the profile panel of the plot template log data is specified as a layer
then with this tab the file set for the profile plots can be specified. Click on
to select an existing log data file set in the project for the
selected layer.
10.8.1.3 Design
If the setup with the file selections is saved, the saved setup can be
opened again. Before
selected.
is used the plot project has to be
If the setup with the file selection is finished, the setup will be saved
with the name of the plot template.
If the setup with the file selection is finished, the setup will be saved
with a name specified by the user.
For each runline that is selected in the Select Runlines box a preview
of the plot will be displayed. Click on in the preview file plot to
close the preview and continue with the preview of the next selected
runline. The preview can be stopped by closing the file plot preview
with .
For the selected runline in the General tab a preview of the plot will be
displayed. Click on or to close the preview.
For each runline that is selected in the Select Runlines box a profile
plot will be generated with the setting as specified in the different tab
pages. Each profile plot will be placed in the plot project as a separate
plot file with the name of the plot template and a sequence number.
After the plot files are generated they will be printed.
For each runline that is selected in the Select Runlines box a profile
plot will be generated with the setting as specified in the different tab
Before the DXF file can be created the plot files has to be generated
as discussed above in the option .
After the plot files are generated for each plot file a DXF file will be
created and will be placed in the plot project directory.
If a lot of DXF files has to be created, it can take a long time before the
creation of all the DXF files is finished. Move the cursor over the plot
icon ( ) in the taskbar and a display will tell the user how many tasks
(DXF files) still have to be processed. In the example below still 176
DXF files has to be created.
The Quick Profile Plot will be closed and the setup will not be saved.
The two default user accounts, Administrator and Basic Operator, do not
have a password yet. If the user wants a password to protect these two
accounts, select a user account and click on to open the User
dialog to add a password.
Enter the password in the field Password and repeat this in Retype
password. With the option Show password the actual text of the password
is displayed, if this option is unchecked only dots will be displayed (see
above).
At the moment are two access level present. With a new
access level can be added or an existing user level can be modified (see
below).
Figure 10-46 Manage user level access window with the two default access
levels, Administrator and Basic Operator.
In this window the menu options from the Control Center, the Acquisition
and the Presentation that can be switched on/off are displayed. The menu
options that are accessible in all different access levels are not displayed.
Check the option Make copy of access level if an existing access level
has to be used as base for the new one. If the option is unchecked all the
menu options in the new access level will be switched off (set on No).
Figure 10-48 Manage user level access window with new user level
Click on a Yes or No in the window and the selected menu item can be
changed. So is in the figure above the menu item Logging/Logging
Settings in the Acquisition changed to Yes.
Figure 10-49 New user account with the new user level
On the top right side in the application the user account can be changed.
Select the option and select one of the available user accounts. If for the
user account a password is added, then the user has to enter the
password before the selected user account becomes active.
10.11 Language
At the moment, next to the English language, the other languages that are
available in PDS2000 are Deutsch (German), Français (France), Italiana
(Italian), Nederlands (Dutch), Russian and Chinese.
If PDS2000 is running in a not English language it is possible that not all
items in a menu or in the text of the menus are in the right language. The
translation is made for a specific version of PDS2000, so if software
modification took place after that version the new items or text will be in
English.
Select from the menu bar of the Control Center the option Tools >
Options…and in the Language tab select a different language for
PDS2000.
Figure 10-52 Message to restart PDS2000 to made the new language active
Restart PDS2000 and the selected language will be the active language
for PDS2000.
The message is only a warning that the performance can be better if the
advice as mentioned in the message is followed.
When one of the checks failed the following text will be displayed.
Select the user general folder and automatically the selected folder will
become the folder used in the User General tab in the Explorer.
11.1 Introduction
PDS2000 uses different types of data files to store the relevant
information and settings. All these data files are accessible through the
Explorer.
It is also possible to use The Explorer is one of the windows that is available in the Control Center.
the context menu of the If the Explorer is not present in the Control Center, select View from the
Control Center to add or menu bar and check Explorer. To remove the window from the Control
remove the view. Center uncheck Explorer.
In the Explorer the information is divided in seven databases.
Projects Common
The settings and data files from the ‘Projects Common Files’ folder in
the PDS2000 Projects directory (see page 214).
PDS2000
General settings that can be used by all the applications and projects
in PDS2000 (see page 215).
Project
Project related settings and data files (see page 219).
Log Data
All available types of project related log data files (see page 244).
Multimedia
The multimedia files in PDS2000; the AVI, BMP, JPG and (Geo)TIFF
files (see page 246).
Report
The report files in PDS2000; CSV and PDF files (see page 248).
Sonar Targets
The sonar targets files with the GeoTIFF images of the targets (see
page 248).
Icon Images
The icon images files with the BMP and JPG images for the icons (see
page 248).
In the Explorer a directory structure is made with a separate folder for
It is possible to drag files each data type. The folders with in front of contain data files. Click on
and folders from for or double click on or the folder name to open the folder and make the
instance Windows Explorer data files accessible. With double click on one of the data files the specific
to the PDS2000 Explorer. editor for that data file will be opened. Notice that not all the data files
have their own editor.
At the moment for some data files a preview is available. Select a file and
on the right side in the Explorer, if possible, the data will be displayed. If
which contains the communication settings for COM and NET ports, and
the CustomActions[<module>].ini file, which contains actions defined
by the user.
When using the RESON 7k distribution module, the R7KDistribution.ini
file should be added to the backup.
Care must be taken when restoring project backups, since the backup
New File
For some files the New File A new file for the selected file group can be made and the editor of that
and/or the Add Files file group will be opened.
options are not active,
because there is no editor Add Files
available or it is not Add files to the selected file group. Files can be selected in a standard
possible to add files. dialog window. The file type is set to the file extension for the selected
file group.
Backup
A backup of the selected file group will be made. All the files in the file
group will be compressed to a ZIP file, which can be stored on any
location on the PC.
Refresh
Refresh the view in the Explorer.
Edit
For some files the Edit Will open the editor belonging to the selected file. In the editor the file
and/or the View options can be checked and/or modified.
are not active, because The editor can also be opened with a double click on the file.
there is no editor available
or it is not possible to view View
the file in Notepad. Will open the selected file in Notepad where the file can be checked
and/or modified. It is better to use the editor to modify the file.
Delete
Use the Ctrl key and the Delete the selected file(s) from the file group. It is possible to delete
Shift key to select multiple
files.
more files at the same time.
Also the ‘Delete’ key on the keyboard can be used to delete the files.
Rename
Change the name of the file.
Duplicate
Make a copy of the file. The copy will be placed in the same file group.
displayed. The message ‘No proper chart scale level available’ will be
displayed in the contour of the charts and the location of the charts is
hatched.
The file group context menu has other options than the standard
context menu:
Set as default database – With this option the selected database can
be set as default, which means that the selected database will be used
in the C-Map layers in PDS2000. It is also possible with the Chart
Manager from C-Map to set a default database.
Unregister database – The selected database will be unregistered
from the available databases in the Chart Manager.
C-MAP Filters
There are three C-Map filters available; for not showing the buoys, the
buoys and beacons and the buoys, beacons and piles in the C-Map
layer (see page 36).
Color Maps
The four different display modes (light conditions) which are available
in the Control Center, the Acquisition and the Presentation (see page
165).
Coordinate System Databases
A new coordinate system The different databases for the coordinate systems. The
that is created through pdsgeodatabase is the database with the coordinate systems as given
New File, will be stored in by PDS2000 and the pdsusergeobase is the database with the
the pdsusergeobase. coordinate systems made by the user. see page 71 for more
information about the coordinate system database.
Devices
The devices which are available in the Equipment page (see page 96).
Display Support Files
The files with setup information for different modules in PDS2000.
Dredge Status Configurations
The configuration files with dredge settings special made for Boraciet.
In these configuration files are defined which button are available in
the Manual Input – Dredge Status view (see page 304) and how the
flow will be displayed in the Dredge – SCADA view (see page 290).
These configuration files are only available for Boraciet application
types.
Formats
The formats as defined in the project configuration (see page 59).
PDS2000 Bitmap (BMP) Images
The BMP files as used in the views in PDS2000.
Presentation Definitions
The views which can be opened in the Control Center, in the
Acquisition and/or in the Presentation.
System Files
The system files as used by PDS2000.
Units
The units as defined in the project configuration (see page 58).
Wave Sounds (WAV)
The WAV files for the alerts sounds as specified in the Alert Sounds
page of the Project Configuration (see page 62).
Processing
Information will be displayed for each converted file.
For each file conversion a log file is generated with the conversion
information, warnings and errors. With this button the list with log files
becomes available.
11.4.1.1 Updates
The original file has When updates for the S-57 charts are available then the updates and the
extension 000, while the original S-57 file have to be converted at the same time. The update files
updates have 001, 002, need the original file to do the conversion to the C-Map database.
etc.
The original file cannot be the old original file that is converted before;
there should be a new one next to the update files. The new original file
knows how much update files are available and need them to make the
new database.
It is possible that the update is only a new original file. Then convert only
the new original file. Keep in mind that when the conversion is started the
folder with the existing database is replaced by a new database. So for an
update of some files all S-57 files have to be converted again to create a
new C-Map database.
database when the module is started. If modifications are made to the
files in the project database, the module have to be closed and started
again before the modifications are visible in the module.
The different file groups of the project database will be mentioned below.
The groups or the editors of that group that are not discussed in other
chapters of the manual will have a detailed explanation.
3D Models
The 3D models that can be used as a guidance in the project (see
page 143).
3D Objects
The 3D Objects file with the objects as added to the 3D Object
Manager in the Acquisition (see page 255). There will be only one 3D
Objects file per project.
Don’t rename the file otherwise the objects aren’t visible anymore in
the 3D view.
Alarms
The alarm files as created in the vessel configuration. These files can
only be edited in the tab Alarms of the vessel configuration (see page
129).
BSB Charts (KAP)
The raster (navigational) charts in BSB file format. The extension for
the BSB charts is KAP.
Import from DXF files is an extra option in the file group context menu
of the clipping polygon. A DXF file can be imported with the restriction
that the data in the DXF file contain only one polygon.
Export to DXF file is an extra option in the file context menu of the
clipping polygon. A clipping polygon file can be exported to a DXF file
and will be stored in the project.
It is possible to import multiple DXF files and also to export multiple
clipping polygons in one time. Each DXF file that is imported becomes
a clipping polygon file and each exported clipping polygon file
becomes a DXF file.
Color Tables
The color tables that can be used for the grid models, the 3D views, in
the plotting, etc (see page 226).
Configurations
The different configurations that are created in this project. The active
configuration can also be opened with Acquisition > Configuration from
the menu bar or with in the toolbar of the Control Center.
Import from DXF is an extra option in the file group context menu of
the runlines. From the DXF file only the lines that contain two points
(straight lines) can be converted to runlines. The lines have to be of
the linetype ‘Line’ One runlines file will be generated with all the lines
from the DXF file.
Figure 11-16 File group context menu of the Track Guidance Routes
Import from DXF is an extra option in the file group context menu of
the track guidance routes. From the DXF file only the polylines can be
converted to track guidance routes. For each polyline a separate track
guidance route will be generated.
User Interface Profiles
The UI Profiles which are used for the Control Center, the Acquisition
and the Presentation(s). These profiles contains the settings of the
toolbars used in the three windows. When the user changes one of the
toolbars it will be saved and the next time the new toolbar layout will
come up. Delete in the Explorer the UIP file of a window, if the user
wants to go back to the original (default) toolbar for that window.
User Maps
The user maps are files with user objects that can be created in the
plan views. The different user objects are lines, rectangles, circles,
polygons, text and symbols (see pagexxx).
User Presentation Defaults
There is only one file available, the file ‘EditorView’ and it contains all
the defaults for the editors. When in the context menu of a view the
option Save as Default is selected, the file ‘EditorView’ will be created
or updated.
Export Waypoints to Geo is an extra option in the file context menu of
the waypoints. The waypoints will be exported to an ASCII file
containing the waypoints with their geographical coordinates.
Work Areas
The created work areas that can be used as a guidance in the project
(see page 147).
added in the upper right corner of the editor. Click on to select the
coordinate type, grid or geographical coordinates. Click on to
insert a point above the selected point in the table and click on to
delete the selected point in the table.
In the menu bar some extra functions are available:
Options > Electronic Chart…
Select a PDS1000 electronic chart as background.
Options > Grid Properties
Select the grid to be shown in the view of the editor: Grid Crosses,
Solid Line Grid, Dotted Line Grid or a Scale Bar. The grid can be with
or without a grid annotation.
Options > Import from ASCII…
An ASCII import wizard will be started to guide the user through the
import settings. This import wizard is the same type of import wizard
as discussed on page 136. The ASCII file should contain the X and Y
coordinates of the clipping polygon.
Options > Import from DXF…
Select a DXF file with a polygon and the polygon will be imported in
the Clipping Polygon editor.
Figure 11-19 Color Table generator with a color table added (between 0 and -5)
to the existing color table
Add the values for the maximum and minimum range, select the number
of colors or the step size and click on to create a color table. With
a color table can be added to the existing color table.
If the option is selected the generator will use the whole color spectrum
to generates the colors. It will start with the selected color for the
maximum value and will stop with the color of the minimum value. With
the option only the two selected colors will be used to generate the
color table. The color starts with the selected color for the maximum value
and will stop with the color of the minimum value and for the intermediate
values the colors will run into one another.
With this option the whole spectrum will be used to go from the
color of the maximum value to the color of the minimum value.
Select one of the colors on the left side and click on . A Color
Table Entry dialog will be opened where the color and the minimum
value for the selected color can be changed. Click on to
confirm the change and a star will be placed in the edited color as an
indicator (see below).
Will show only the color table, there will be no buttons to generate a
color table.
Will show the Color Table generator again. This button appears when
is used to show only the color table.
In this color table only the colors and the text of the labels can be
modified. Click on if it is needed to reset the colors and text to the
default settings.
Double click on one of the colors and the Color Table Entry dialog will be
opened.
Figure 11-25 Color Table Entry for the bottom classification color table
For the values between the minimum and maximum value as displayed
on top of the dialog a different color can be selected and another text can
be entered.
It is not possible to modify the range and the steps for this type of color
table.
The dredge differential color table generator has three section; above
underdredge limit, below overdredge limit and between the two limits. For
each section the number of colors and maximum/minimum color can be
set. The edges between the section are defined by the underdredge limit
and overdredge limit.
In the Acquisition the underdredge limit and overdredge limit will be
automatically synchronized with the settings of the design model. So
when the limits for the design model are specified as 1 and -1 then the
limits in the color table will be changed from 0.5 to 1 and from -0.5 to -1.
The color scheme stays the same.
See the 3D View – Online Dredge on page 274 for an example of the
dredge differential color table.
If a new contour definition has to be generated, the left side will be empty.
Start then with or generate a contour definition with the option
or .
A contour line can be added to the list on the left side. A Contour
Properties window will be opened, where the settings for the line can
be set.
Add a value for the level and select a color for the contour line.
For the line style three options are available; a continuous, a dashed
or dotted line.
Give a line width for the contour line.
If a label with the depth value has to be plotted, check the option
Show labels.
Will edit the selected contour line. The Contour Properties window will
be opened (see above).
A color table will be used to generate the contours. Each value from
the color table becomes a contour line with the color from the color
table.
Create a new template. Give a name for the new template and add the
offsets and heights.
Click on to add a new exclude area to the list. Check the option
Polygon or Route and select the right clipping polygon or route with a
tolerance. The clipping polygon or route should exist in the project.
The selected template can be edit. The Add to Design Model window
will be opened (see above).
Before a design profile template can be added the right track guidance
route has to be selected. After that a template can be added with
. An Add to Design Model window will be opened where the
template can be selected.
The selected template can be edit. The Add to Design Model window
will be opened (see above).
When a new sound velocity profile is created the editor will be empty. The
table of the profile can be filled manually or an ASCII file with sound
velocity data can be imported with the option . Before this button is
opened to select the type of import the user has to select which part of the
data has to be imported; the upcast, the downcast or both.
The units for the four columns are not depending on the settings in the
project configuration (see page 58). The depth is always in meters, the
velocity is in m/s, the temperature is in °C and the salinity is in parts per
ton (ppt).
To add a SVP value to the table, fill in a depth value on the empty place
at the bottom of the depth column. When the next column is selected the
depth values will be automatically sorted.
A depth value can be deleted by selecting one of the values in a row and
click on . The whole row will be removed from the table. With
the Ctrl-key multiple values can be selected and with multiple
rows can be deleted.
If the data density is too dense, a reduction of the data is possible with
Before the tide station can be used, the tide station has to be setup. Click
on to setup the information for the tide station.
If more than one tide station will be used the location (Easting and
Northing) has to be entered. The ‘Station ID’ is only relevant if multiple
tide gauges are used with a tide gauge driver that supports multiple tide
gauges. With the ID, PDS2000 can relate the tide data from the incoming
message to the right tide station.
The gaps between two tide values in the predicted tide data will be
interpolated as long the gap between two tide values in the predicted tide
data is smaller then the specified maximum gap. The value for the
maximum gap has to be entered in seconds.
The maximum extend is the time in seconds that PDS2000 will
extrapolate the tide data after a tide value. This can happen after the last
tide value in the file or when the gap is bigger than the maximum gap.
After the tide station information is set, it will depend on how the tide
station is used in PDS2000 what the next step will be. If in the Acquisition
online tide gauges are used the editor can be closed. If predicted tides will
In the table new entries can be made at the bottom of the table. After
added an entry the tidal data will be order according the date and time.
By double clicking on a cell in the date column the date can be
modified. The cell will change to and the date can be
change with the arrows on the right or manually. Also by double on the
cell in the time column the time can be modified. The data in the tide
column can be modified when the cell is selected.
The time can be entered as hours (hh), hours minutes (hh:mm) or as
hours minutes seconds (hh:mm:ss). Below is displayed what can be
entered in the cell of the time column and what the time will be in the
column.
Entered value Displayed time
1 00:01:00
12 00:12:00
123 01:23:00
1234 12:34:00
12345 12:34:05
123456 12:34:56
Please read the attention in the dialog, the time used in the tide station
file is always the local time.
Enter the date for which a tide values have to be added. Enter a start
time, end time and an interval (increment). Click on to accept
the settings. In the table the time is already filled in according the
start/end time and increment from the dialog. Only the tide values have
to be entered manually.
With one or more rows in the table can be deleted. Use the
Ctrl and Shift key to select more than one row. It is also possible to
drag with the mouse over the rows to select the rows that have to be
deleted.
Import Tide Values ( )
Import tide data from ASCII files.
Select the long date/time format and give the order of the data by
selecting the date, time and tide with the separator between the data
fields. For the date and time a format and a separator have to be
selected. If everything is set, click on to import the ASCII data
and the data will be displayed in the editor. In the group ‘Tide Values’
of the Explorer one or more PDS2000 tide files are added with the
name of the station, the year and the month. PDS2000 will create for
each tide station a separate PDS2000 tide file per month.
When in a file the GPS has Import PDS Log Tide Values ( )
been in RTK mode for at Import tide from PDS data files. PDS2000 will find all PDS data files in
least one minute, and over the current project from all log data folders. Make a selection of the
20 valid real time Z values
are available in that
PDS files to extract tide data from. Next select the device that has tide
minute, then the tide list is values, e.g. the GPS RTK positioning system.
appended with one mean Generate Report ( )
tide over the minute.
Generation of a tide report. When the option View report is checked
the report is opened in the PDS2000 Reporter where it can be saved
with an user defined name. If not checked the report will be saved as a
PDF file with a default filename in the ‘Reports’ folder of the project.
Enter a start and an end date and when View report is checked, the
report is opened automatically after generation. The width and height
of the images (graphs) can be set in the appropriate windows.
Channel Properties
The Properties window for the active tide station data will be opened.
Properties
The Properties window for the Tide Station editor will be opened.
Next to the information that can be available in the file name, two extra
items are available: PDS2000 version and File version. The different file
versions are:
File version PDS2000 version Reason modification
1.0 Before 3.4.0.0 Original
2.0 3.4.x.x & 3.5.x.x User defined log file names
2.1 ≥ 3.6.0.0. Compression of side scan, snippets
and sonar image data
In the file context menu (see page 213) is next to the standard options an
extra option, Show log info, available. This option is only available for the
PDS2000 logdata files.
Figure 11-46 File group context menu of the Tagged Image File Format
(GeoTIFF) Images
Import From BSB Charts is an extra option in the file group context
menu of the Tagged Image File Format (GeoTIFF) Images. A BSB
Chart with the extension KAP can be imported and will be converted to
a GeoTIFF image.
The only way new files can be created is through the option New File in
the Explorer. After a filename is given the user can import a TIFF or a
JPG file to create a GeoTIFF file.
In the Raster Editor are two methods available to create from the
imported file a GeoTIFF file.
Tiepoint/Scale Mode
If one of the corners of the image is known in local grid coordinates
enter the pixel X and Y and the grid coordinates directly in the left
pane.
If not, select one location in the image that is known in local grid
coordinates. Use the zoom in and zoom window functions to get a
clear picture of the location, double click with the mouse on the
location and enter the right grid coordinates for that location.
Figure 11-48 Enter the local grid coordinates for the selected location
After that enter a scale X and scale Y in m/pixel to define the size of
the image.
Calibration Point Mode
For this mode two points have to be known in the image with local grid
coordinates. Enter the grid coordinates directly in the left pane or
select the option Calibration Point 1, double click with the mouse on
12.1 Introduction
The Acquisition in PDS2000 takes care of reading the sensor data, doing
the necessary computations, and data logging. The data and the
computations are visible through a number of views, which can be used to
get information over the processes and to control the survey. Some other
views are designed to guide the vessel.
The Acquisition can be started in a simulation mode and in a realtime
mode. The simulation mode can be used to setup in the office the
different layouts for the survey and the realtime mode is the online mode
where the actual survey can be monitored and logged.
12.2.1 Simulation
When the equipment is not yet connected to the PDS2000 computer the
Acquisition in simulation mode can be used to setup the different layouts
for the survey. The Acquisition in simulation mode can be opened from
the Control Center of PDS2000 with:
12.2.2 Realtime
The Acquisition in the realtime mode can be started when the project and
a vessel configuration is created. The Acquisition in the realtime mode
can be opened from the Control Center of PDS2000 with:
12.3.1 Layout
When the Acquisition is started for the first time, it will have only one view,
the Messages – System Messages view (see page 307).
In the Displays window the necessary views can be added to the layout.
There are several ways to open this window:
Select View > Displays from the menu bar.
Click on in the toolbar.
Select Displays in the context menu.
In the Displays window the views can be checked on or off. This means
that the checked views will be displayed on the screen. The views that are
checked off are not removed from the layout file. It only means that these
views are not shown on the screen. A view can be removed from the
layout file by using in the Displays window.
There are also some fast methods to add views to the layout in the
Acquisition.
Select View > Add Display… from the menu bar.
Click on in the toolbar.
Select Add Display in the context menu.
After all the wanted views are selected and placed on the right place in
the Acquisition window, with or without docking, the layout can be stored.
Use File > Save Layout As… from the menu bar to save the new layout.
To open another layout use File > Open Layout… from the menu bar and
select one of the created layouts.
With File > Save Layout As Preset the layout can also be saved as a
preset to one of the four layouts.
Select the location on the bucket from where the measurement has to
start (for example the left side of the bucket, see above), click on
and in the Measure dialog the information under ‘From’ is
entered. Move the bucket and select the same or a different location
on the bucket, click on and in the Measure dialog the
information under ‘To’ is entered. Now the distance, bearing and
elevation between the two point is calculated.
Tools > Start Next Trip
For a trailing suction hopper application the next trip will be started.
Tools > Add Waypoint by Coordinate ( )
The options Add Waypoint A waypoint can added to the plan view with its satellite ellipsoid
by Coordinate and Add coordinates, its local ellipsoid coordinates or its grid coordinates.
Symbol by Coordinate are Tools > Add Symbol by Coordinate ( )
only available in the
A symbol can added to the plan view with its satellite ellipsoid
‘Boeilog’ application.
coordinates, its local ellipsoid coordinates or its grid coordinates.
In a plan view (see page 343) an other runline can be selected by clicking
on an other line. That line should be one of the lines in the runline file that
is selected in the layer Active Runlines. The button in the plan view
toolbar should be on before it is possible to click on a runline in the plan
view.
12.5 Logging
There are three logging methods:
The logging formats and 1. Logging of RAW data in the predefined formats. (off), (on) or
the logging filenames are (conditional logging).
selected in the Logging
page (see page 116). In the Acquisition the data logging can be switched on and off with:
F4 key on the keyboard.
from the toolbar.
(Un)check Logging > Enable Data Logging from the menu bar.
Click on or on (or ) in the frame indicator in the right
bottom of the Acquisition view to start or stop the data logging.
Switching from log file can be done with:
from the toolbar.
Select Logging > Switch Log File from the menu bar.
12.6.1 F-Keys
There are two methods to attach an action to a F-key, through the Button
Properties window and through the ‘Attach to Button’ option.
The Button Properties window can be open in the Commands page of the
Customize window.
Select the category User Buttons and the F-keys will be displayed on the
right side in the page. If the selected F-key has already a shortcut it will
be displayed at the bottom under ‘Description’. With the selected F-
key can be modified in the Button Properties window.
Select the device or the related computation on the left side and the
properties will appear on the right side. Select one of the attributes in the
properties and click on . The selected attribute action can be
attached to the F-key in the Button Properties window as discussed on
page 263.
In the Acquisition are for the ‘Attach to Button’ option two ways possible to
open the properties of the equipment, through the Raw Data view and
through the Select Data window.
With double clicking on one of the items in the Select Data window the
related properties window will be opened. Select in this properties window
the attribute for the F-key, click on and the Attach to Button
window will be opened (see below).
Select the attribute of the device data that can be used fore the manual
input. and click on .
Attach this manual input action to a F-key in the Button Properties window
as discussed on page 263.
Click on and select in the Select Layer window the layer from
which an attribute has to be selected.
Figure 12-21 Select View Attribute window to select an attribute in the view
Add an attribute from the layer properties by opening the Layers window
of the view in the Acquisition through the option Layer Control in the
context menu or with in the toolbar of the view. Select in this window
the layer from which an attribute has to be selected. Open this layer by
double clicking or by clicking on . Select in the Properties window
of the selected layer the attribute for the F-key and click on . The
Attach to Button window will be opened to attach the attribute to the right
F-key (see page 266).
Add an attribute from the view properties by opening the properties of the
view in the Acquisition and select the attribute for the F-key. Click on
and the Attach to Button window will be opened to attach the
attribute to the right F-key (see page 266).
Select one of the macro’s from the list and click on and a window to
enter a new shortcut key will be opened.
12.7 Presentations
A Presentation can have the same views as the Acquisition, but it gets the
information from the Acquisition. In other words, a Presentation is
connected to the Acquisition and send requests to the Acquisition to send
data for showing in the views.
That is the reason a Presentation cannot control data logging and further
system settings. The only selections that can be done in a Presentation is
selecting the active runline, selecting the active waypoint, create a new
waypoint and the Man Over Board option.
Multiple presentations can be connected to an Acquisition. Presentations
can run on the same computer as the Acquisition (Local computer) or
over a network on a remote computer. To connect to a remote, see page
22 where the installation and running of a remote presentation is
described.
13.1 Introduction
To show all the survey information in the Acquisition and in the
Presentation(s) several views can be used. These views together are
called a layout.
There are two ways to create a layout and to add the views to that layout.
See ‘Data Visualization’ on page 252 to add a view to the layout.
In the Acquisition or Presentation with File > New Layout… from the
menu bar.
By changing an existing layout in the Acquisition or Presentation. Save
the changed layout with File > Save Layout As... from the menu bar.
In this chapter all the possible views for the Acquisition and the
Presentation will be discussed in alphabetical order. It will depend on the
application type if a view is available in the Acquisition and in the
Presentation.
At the moment following views are available in the Acquisition and in the
Presentation:
1. 3D Views (see below)
2. Alerts View (see page 278)
3. Compass View (see page 280)
4. Device Configuration Views (see page 280)
5. Dredge Views (see page 286)
6. Dredge Status View (see page 290)
7. Echosounder Graphical Trace View (see page 291)
8. Helmsman View (see page 299)
9. Icon Image View (see page 301)
10. Interval Logging View (see page 302)
11. Laser Scan Control View (see page 302)
12. Manual Input View (see page 304)
13. Messages Views (see page 305)
14. Multibeam QC Views (see page 307)
15. Multibeam Video View (see page 334)
16. Numerics View (see page 335)
17. Obstacle Avoidance (see page 338)
13.2 3D View
In the Acquisition are two 3D Views available.
3D View – Online (see below)
3D View – Online Dredge (see page 274)
The views are nearly identical, the only difference is that the 3D View –
Online Dredge has as default a dredge layer instead of a vessel layer.
In the 3D View the standard 3D view navigation can be used (see page
50).
Figure 13-1 3D View – Online with multibeam and laser scan data
Figure 13-2 3D View – Online Dredge with a cutter dredger and an updated
active grid model
When the cursor comes close to the arrows of the measure line, the
line is highlighted and the cursor is changes in a ‘hand’. Grab the
arrow to move the end of the measure line.
When the cursor is away from the arrows of the measure line, the line
is dimmed and cannot be moved. Click on a new position and keep the
left mouse button pressed to draw a new measure line.
Click on the right mouse button to stop the measure option.
Show Grid Layer ( )
If this option is ‘on’, the coordinate axis system is shown in the center
of the view.
Color Table Layer ( )
If the option is ‘on’, the color table will be displayed on the right side in
the view. This is only valid when in the Properties a color table is
selected (see page 278).
Save Snapshot ( )
An image of the 3D View will be saved as a JPG or BMP file.
Create Sonar Target ( )
Draw a box around an area in the active grid model and the area will
be saved as a sonar target.
The symbol for the sonar target can be defined in the Active Sonar
Targets Layer which will be created when the first sonar target is
selected.
When the sonar Target symbol is drawn in the view a context menu
becomes available for that sonar target. A right mouse click on or in
the symbol gives some extra options. For more information see page
355.
Layer Control ( )
The Layers window of the view will be opened (see below). In this
window only the used layers will be displayed; layers can be added,
modified or removed.
Coverage Settings ( )
If a grid model is added to the view then the available data types of the
grid model with their color table will be displayed in the Coverage
Settings view. Select the data type and its color table for the display of
the grid model.
The transparency of the grid model can be defined, where 0 is no
transparency and 100 complete transparency.
The resolution of the grid model can be set in 5 steps from Very Low to
Very High. This means that when the grid model is zoomed out and
the resolution is Very High more detail of the grid model is shown than
when the resolution is Very Low. The resolution has no impact when
the view is zoomed on the grid model, because then the resolution is
always high.
Properties ( )
The Properties window of the view will be opened (see below).
The alarms can also be The alarms and timeouts are displayed in the Acquisition with the Alerts
displayed in the Acquisition view. In this view all active alarms and active timeouts are displayed with
and Presentation with the an indication if they are accepted. There is an option in the view to set the
Status – Alarms view (see view as a pop-up view with the option that the view will pop up when an
page 384). alarm is created. Click on in the top left side of the view and checked
the option ‘Auto-Show Alerts’ and the view will act as a pop-up view.
This view will stay on the screen until the user click on or
. With View > Alerts from the menu bar or by clicking on the alarm
Figure 13-8 Compass view with True Heading, CMG and Waypoint heading
In the Compass view the true heading will be displayed with the CMG
(course made good). It is possible through the properties in the context
menu to display the guidance heading (route or waypoint) as an extra
heading (see below).
In this page the Frequency, Range, Power, Max. ping rate, Gain, Pulse
Length and Pulse Type can be set. It will depend on the RESON SeaBat
7K type (f.i. 7101, 7125) what the values for each setting will be.
The different sonar settings are:
Frequency
The used frequency for the sonar will be displayed. If more
frequencies are possible for the used sonar then the user can select a
different frequency and the sonar will switch from frequency
automatically.
Range
The range setting determines how far the sonar will ‘see’.
Power
To increase or decrease the amount of power (acoustic energy)
transmitted into the water.
Figure 13-10 Ocean Menu for the Device Configuration – RESON-7K view
In this page the Absorption, Spreading and the Sound Velocity can be set.
The different physics settings in the Ocean Menu are:
Absorption
The absorption is the amount of loss expected through the ambient
water medium.
Spreading
The spreading is the amount of cylindrical and spherical spreading
loss that is expected through the ambient water medium.
This coefficient value is used in conjunction with the absorption loss
value to compute the TVG curve applied to the returned signal.
Sound velocity
The sound velocity is an external measured speed of sound through
the local water.
Figure 13-11 Data Recording for the Device Configuration – RESON-7K view
With this data recording page the recording in the related 7K Center can
be started and stopped.
It is not necessary to have this view open to get an active synchronization
with the PDS2000 logging. With the attribute Sync Sonar Data Recording
with PDS in the device driver of the Device Configuration – RESON
SeaBat 7K the synchronization can be enabled or disabled.
Recording Control
With and the user can manually start and stop the data
recording (=logging) in the 7K Center.
If the option Synchronize with PDS logging is checked both buttons are
inactive. Now when the logging is started in PDS2000 then automatically
the data recording will start in the 7K Center. If the logging is stopped in
PDS2000 also the data recording in the 7K Center will stop.
When the 7K logging is started with the default log file name will
be used, when the option Synchronize with PDS logging is checked the
log file name will be the default file name with ‘PDS’ added (as shown in
the figure above).
Recording status
Recording mode
When there is no logging the recording mode is set on Stopped.
When the logging is started the recording mode is set on Recording.
Directory name
Directory where the S7K file will be stored. This path has to be set in
the 7K Center.
Filename
When the data recording is started the name of the S7K file will be
displayed.
File size
Size of the S7K file will be displayed.
Free diskspace
Percentage that is free on the hard disk where the 7K Center is
running.
In this page the Range, Gain, Power Level, Pulse Length and
Minimization can be set. When for the first time the Acquisition is opened
the HydroBat will not be pinging.
The different multibeam settings are:
Auto pilot
With the option Auto pilot, default settings depending on the Range
setting will be used. The value for the Power Level and Pulse Length
are controlled by the auto pilot, the other settings can still be set by the
user.
When the auto pilot is off the Power Level is still depending on Range
and the Pulse Length. It is not possible to set the Power Level on
maximum when the Range is small and/or the Pulse Length is on
maximum.
Range
The range setting determines how far the sonar will ‘see’.
Gain
The amount of receiver gain applied to the returned sonar signal (in
addition to the calculated gain).
Power Level
To increase or decrease the amount of power (acoustic energy)
transmitted into the water.
In this page the Absorption and the Sound Velocity can be set.
The different physics settings in the Ocean Menu are:
Absorption
The absorption is the amount of loss expected through the ambient
water medium.
Sound velocity
The sound velocity is an external measured speed of sound through
the local water. See also Override sound velocity.
Override sound velocity
The sound velocity will normally be read from the sound velocity
sensor and therefore cannot be set in this page when the option
Override sound velocity is unchecked. Check this option and the slider
for the Sound Velocity becomes available. The user can now manually
set the sound velocity value and will overrule the data from the sensor.
The Dredge – Bars Horizontal view will display attributes from the
computations as a bar with the actual value.
A bar can be added to the view by opening the Layer Control in the
context menu of the view. Add an Up=Down Indicator Layer and select as
‘Source Item’ an attribute from the one of the computations.
The Dredge – Bars Vertical view will display attributes from the
computations as a bar with the actual value.
A bar can be added to the view by opening the Layer Control in the
context menu of the view. Add an Up=Down Indicator Layer and select as
‘Source Item’ an attribute from the one of the computations.
Figure 13-16 Dredge – Flow/Concentration Meter view for two suction tubes
Figure 13-17 Dredge – Load and Draught view with the Load page
By default are in the time series view the load, the hopper volume, the
TDS and the dredge status selected. In the numerics part of the view are
four pages by default defined; Hopper Sensor, Draught Sensor, Load and
TDS. In the view a context menu is available to setup the view or to add
extra items to the view.
It will depend on the settings in the dongle which pages are available and
which computations will be computed to display the data in the view.
See the application manual for the Trailing Suction Hopper for more
information about this view.
The Dredge – SCADA view In the Dredge – SCADA views the dredging processes can be displayed.
is at the moment special The view shows (the position of) the control valves, the pumps and the
made for Boraciet. piping. It is also possible to show the flow directions from the suction head
to the hopper.
When this view is opened the first time it will be empty. In the properties
of the view a filename representing a scada view with the data source has
to be selected (see below).
Figure 13-19 Dredge Status view with Sailing full as dredge status
The Dredge Status view is not a standard view which can be added
through the Displays window or the Add Display option in the context
menu of the Acquisition.
Select the option Tools > Equipment Control in the menu bar of the
Acquisition to add the Dredge Status view. Select the view in the Add
Equipment control display(s) window and click on to add the view
to the Acquisition. After the view is added the window can be closed.
Save Snapshot ( )
A snapshot of all the data from the start to the present time will be
stored in a temporary file, called ‘snapshot.log’. Click on in the
Information dialog and a Print window will be opened where the data
can be selected that has to be printed.
Use the slider to scroll through the data and set a start and end marker
in the window to select only a part of the data that has to be printed.
Click on to change to channel 3 & 4 (RT2), and vice versa.
In this page the port settings for Channel 1 &2 (Port 1) and, if applicable,
for channel 3 & 4 (Port 2) can be set.
In this page the graphics colors for the echo trace can be set.
There are 4 user defined possibilities for the color settings and one
default for the gray scale palette.
Graphic Level 1 is the background color; Graphic Level 8 has the highest
voltage level (strongest echo return) and Graphic Level 2 the lowest.
Click on to select for a graphic level a different color from the color
palette.
In the page of the settings nearly all the sounding related commands are
available. The most used commands are also available as buttons at the
bottom of the view.
The most important settings are:
Draft
The draft of the echo sounder transducer can be set. The draft is the
depth of the transducer below the water level. The draft is added to the
measured depth to get the total depth.
If the draft is entered here, the draft should also be entered in the
properties of the echosounder device in the equipment.
Frequency
The frequency of the transducer can be set.
Range
The range of the transducer can be set. The value should be more
then the actual depth below the transducer. The bigger the range the
slower the update rate of the data in the view will be.
In this page the settings for the paper or screen can be set.
Paper Range
The range (depth) as displayed on the paper or screen can be set.
The size of one pixel of the graphical trace is depending on the paper
range; the range is divided in 200 samples to present the graphical
trace.
At the moment PDS2000 supports only the 200 samples as the
presentation for the graphical trace.
Paper Offset
An offset on the paper of screen can be set. The offset will shift the
paper range down so the echo sounder data can be displayed more in
the middle of the paper.
In this page all the settings that are not placed in the other pages can be
modified.
If a heave sensor is connected to the echo sounder check the option Use
Heave and fill in the port settings for the heave.
A Helmsman needs to know the position of the vessel in relation with the
current line. This can be a runline, a route or a wayline. With the
Helmsman view the offtrack, different headings and different distances
can be displayed.
At the top of the view an offtrack indicator is displayed with a user
selectable scale. The offtrack limit, as specified in the runlines page of the
Guidance (see page 138), will be shown as triangles.
The offtrack lines in green and red are always displayed at an interval of 5
system units (for example 5 meter or 5 feet). The offtrack limit, if
specified, will be displayed as light blue lines.
On the bottom line of the view from left to right: vessel heading, line
heading, current line, heading to steer to next point of the line and
distance to next point on the line. The next point can be the end point of
the line, if it a straight line, or it can be the next tangent point in a route.
On the right side the bar graph (here in black) gives the distance traveled
form the start of the line. The actual value for the distance traveled is
displayed at the bottom next to the bar graph. At the top next to the bar
graph is displayed the distance to go to the end of the line.
Save Snapshot ( )
The picture of the view can be saved as a JPG or BMP file.
The Icon Image view is a view that will be created for each icon image
that is selected in the Plan View. The view shows the image with as extra
an icon image info table.
In the caption of the Icon Image view is visible in which icon images file
the image is stored. In the example above the icon images file is ‘test’ and
it is the first image in the file.
The Icon Image view can be opened from the Plan View – Survey
Coverage or Plan View – Navigation. Double click on an icon and the
image with the info table will be opened.
Only the Description in the icon image info table as displayed below the
view can be modified by the user. The other item are generated when the
icon image is created. Click on the field right of the item Description and
enter some text. After the description is modified click on to save
the modification to the icon images file. The name of the icon images file
can be set in the Project Configuration (see page 64).
To delete an icon from the Plan View and form the icon images file, open
the context menu of the Icon (right mouse click on the icon) and select the
option Delete Icon Image.
All collected icon images will be saved in the selected icon images file,
which is available in the Icon Images tab of the Explorer (see page 248).
The corresponding BMP and/or JPG files are also stored in the Icon
Images Database of the Explorer.
Figure 13-32 Interval Logging view with 2 items with the sampling method
The Interval Logging view displays the items as specified in the Interval
Logging page for a cutter dredge application (see page 111).
Figure 13-33 Laser Scan Control View for the MDL laser scan
Figure 13-34 Laser Scan Control View for the Riegl Z Series laser scan
The values in the control view will be populated with values obtained from
the laser scan.
Select for Frame Motion the option Continuous to get a proper working
with PDS2000.
Figure 13-35 Manual Input – Dredge Status view with all the dredge statuses
and delays
When the Manual Input – Dredge Status view is opened the first time it
will be empty. In the properties the configuration file for the right vessel
can be selected.
At the moment the order of In the view several dredge statuses can be selected during the dredge
the dredge statuses is operation. Not all the dredge statuses will be displayed at the same time
fixed according the as it is displayed in the example above. Only the dredge statuses that can
instructions of Boraciet. be possible as next status are displayed in the view. If it is necessary,
with the Undo (Ongedaan maken) button it is always possible to go back
several dredge statuses. The OK button is only visible when a trip can be
finished. After the user clicked on the OK button the next trip will be
started.
Next to the dredge statuses several delays (Verlet) types can be switch
on or off. There is no delay when the delay button is white and the delay
is active when the button is red. An active delay can continue over several
dredge statuses and will be finished automatically when the OK button is
selected.
In the main page the available sonar systems are displayed, normally it
will be only one as displayed above. Double click on the sonar name and
for the RESON HydroBat the Event page will be opened and for the
RESON SeaBat 7K the BITE page will be opened.
In the Event page the events (messages) from the sonar system will be
displayed.
In the BITE page the BITE messages from the RESON SeaBat 7K
system will be displayed.
This page is not available for the RESON HydroBat.
In the Messages – I/O Port view the incoming and/or outgoing data can
be displayed.
Select in the Properties window (available through the context menu) for
the item ‘I/O Port Selection’ an I/O port and in the view the incoming
and/or outgoing data on that port will be displayed.
Also the font and the color for the different types of text can be modified in
the properties.
Figure 13-41 Multibeam QC- 3D Seafloor view with the raw data in the
display mode Quality
Depth Dots
The multibeam data is displayed as dots. It is possible to show the
colors as the colors of the selected color table.
Figure 13-49 Multibeam QC – Backscatter Signal Strength Profile view with the
multibeam xyz computation and all four the multipings
Figure 13-50 Multibeam QC – Raw Profile view with the raw data in the
color mode Quality
Figure 13-51 Multibeam QC – Raw Profile view with the multibeam xyz
computation in the color mode Quality
Figure 13-52 Multibeam QC – Raw Profile view with one ping in the color
mode Detection Process
Sequence number
The RESON SeaBat 7K systems can be setup to output multipings.
This means that there are four different pings after each other and they
can be displayed in four different colors in the view.
When there are no multipings in the multibeam data, the data will be
displayed in black.
Figure 13-53 Multibeam QC – Raw Profile view with multipings in the color
mode Sequence number
Figure 13-54 Multibeam QC – Raw Profile + Total Propagation Errors view with
the color mode Quality and the vertical and horizontal TPE’s
Figure 13-55 Multibeam QC – Total Propagation Errors view with the vertical
and horizontal TPE’s and IHO errors
Total vertical
Total heave error Range error Angle error Pitch error Beamwidth error
reduction error
Angle measured
error:
Beam across
width error
(Amplitude/Phase)
Total GPS error Range error Heading error Angle error Pitch error Beamwidth error
GPS horizontal
error SV profile error +
Heading sensor Error due to Along
Range Angle error over Total pitch error
error over beam beamwidth over
measurement beam range over depth
range beam range
error
Total Latency
error
Figure 13-58 Multibeam QC – Vertical Waterfall view with the multibeam data
item Quality
The Multibeam Filters view can only be opened through the context menu
of the Multibeam QC views when in the properties the Multibeam Source
is set to Multibeam xyz computation (see above).
The filters are active when the filters are displayed in the window and the
checkmark ( ) is set. With , a not displayed filter can be added to
the list. Uncheck a displayed filter and it will be not active anymore.
Click on to see if the filter settings work accordingly. Click on
to accept the filter settings and to close the window. When the
window is closed the unchecked filters will be removed from the list of
active filters. When the Multibeam Filters view is opened again the
unchecked filters will not be displayed anymore and can be added again
with . When a filter is added again it will remember the last used
settings.
All the available filters for the Multibeam Filters view are:
Beam reject filter
The selected beams will be rejected.
The quality settings are the same for all the RESON multibeam
systems.
Quality 1 = Poor colinearity and Good brightness.
Quality 2 = Good colinearity and Poor brightness.
Quality 3 = Good colinearity and Good brightness.
Range filter
Reject the beams outside the given range limits.
The minimum and maximum depth relative to sea level. See Figure
13-60 on page 327.
Angle Nadir filter
Reject the beams outside the nadir angles.
The port and starboard angle from the nadir. See Figure 13-63 on
page 328.
The angle can be defined as the angle to the detection point or as the
angle as received at the transducer (see Figure 13-64 and Figure
13-65 on page 329).
Distance Nadir filter
Reject the beams where the distance from the nadir exceeds the given
distance limits.
The port and starboard distance from the nadir. See Figure 13-66 on
page 329.
Slope filter
Reject the beams where the slope angle exceeds the given slope
angle.
The maximum acceptable slope angle. See Figure 13-61 on page 327.
Intersect filter
Reject the beams where the intersection angle is smaller then the
given intersection angle.
The window size options are 3x3, 5x5 and 7x7 beams. See Figure
13-67 on page 330.
The strictness is from 1 (low) to 9 (high), where a setting of 1 has less
influence then a strictness of 9.
Smart filter
Reject the beams that are outside the filter band created with the
smart filter settings. It only available when an interferometry device is
used.
The size + border are the number of beams that will be used for the
filter. See Figure 13-62 on page 328.
IHO error filter
Reject the beams with higher IHO errors then the selected IHO error
filter.
The IHO orders are the special order, the order 1 to 3 and NL Norm A.
See for an explanation on page 330.
Custom error filter
Reject the beams with a higher vertical TPE as specified.
The user can enter a maximum vertical total propagation error. See for
an explanation on page 316.
With the option Swath reject a full sway will be rejected when the
percentage of rejected beams is more than the given percentage.
There are three methods to use sound velocity information in the
multibeam computation; No SV Profile, SV Profile File and SVP Sensor.
The option No SV Profile means no sound velocity profile will be used.
When the option SV Profile File is selected, a sound velocity profile can
be selected. The profile will be used in the multibeam computation.
When the option SVP Sensor is selected, the data from the sound velocity
profile sensor that is selected in the Equipment will be used in the
multibeam computation.
When sound velocity profile data is used, the option Use surface speed of
sound as first entry in the table become available. If this option is
selected, a thin layer is inserted in the sound velocity profile at the depth
of the sonar head. The inserted value is the same value as is measured
by the sound velocity probe at the sonar head. This option is useful when
the sound velocity profile is stable and it keeps the same type of shape.
‘Rejected’ means ‘marked as rejected’. The rejected beams are always
logged in the raw data file and not in cleaned data files. Changing the
filter settings in the Editing (see page 456) can bring back some of the
rejected beams.
Range
Filters Nadir
Depth
Filters
For the depth filter the points outside the depth limits will be rejected.
For the range filter the points outside the range limits will be rejected.
Intersection
Angle Nadir
Slope Angle
Figure 13-61 Intersection and Slope filters
The intersection filter checks the enclosed angle of 3 data points against
the given minimum angle. A smaller angle then the intersection angle will
reject the middle data point of the 3 data points.
The slope filter checks the angle between two adjacent points and the
plane against the given maximum angle. When the angle is larger than
the maximum angle, the beam will be rejected.
1 2 3 S 5 6 7 C
X
The flying object filter will reject each beam that is too high in relation to
the sea bottom.
In the figure above the size is 4 and the border is 3. This means 4 beams
from point A to the center (point C) gives point S and then 3 beams to
both sides. This will give 7 beams to check against point A. The flying
object filter will reject point A if one of the 7 beams is further away in X
direction from the center beam (point C) then point A. In this example is
point 1 and 2 further away than point A, so point A will be rejected.
Port Starboard
Angle Nadir Angle
The angle nadir filter checks if each beam is inside the port or starboard
angle and the nadir. Points outside the angle will be rejected.
Angle to
detection point
The incidence angle is the angle between the nadir and the received
angle at the transducer head. This is the angle on which the data is
received in the transducer head.
The angle to detection point is the angle between the nadir and the line
between the detection point on the seafloor and the transducer head. The
detection point is the point where the beam with ray-bending will hit the
seafloor.
Nadir
Port Starboard
Distance Distance
Figure 13-66 Port and Starboard Distance Nadir filter
The distance nadir filter checks if each beam is inside the port or
starboard distance and the nadir. Points further away from the nadir then
the limits will be rejected.
depth
A statistic filter checks each data point in a multibeam sway against its
surrounding data points.
Each point is surrounded by a window of points, depending on the
selection either 3x3, 5x5 or 7x7 points. The window will give 9, 25 or 49
observed depths. These values will be sorted and from the sorted points
the median value is taken. This median is used as a robust estimate for
the point under test. In case the point under test differs more than 3%
from the median value than the point is rejected immediately.
The point that passed the first test will be tested further. From the sorted
depths two quartile values are taken, at .25 and .75 from the number of
observations. The difference of those two points will be used in an
integration routine together with 9 previous (approved) differences. (10%
of each depth is taken). The result of this routine is a variation value.
The difference of the found median value and the absolute value of the
point under test are compared with a value set by the variation value and
a user definable ‘Strictness’. A strictness of 1 takes the variation value
times 10, and a strictness of 9 takes the variation value times 2. This
means that a strictness of 1 (low) has less influence than a strictness of 9
(high).
A point will be rejected when the difference between median value and
the absolute value is more than (variation value x [11 – strictness]).
The statistic filter is an acceptation filter that adjusts itself to the
roughness of the seafloor, because of the fluctuations in the variation
values.
It is advisable to use next to the smart filter a statistic filter (see page 330)
to remove the major spikes.
The most common settings for the smart filter parameters are:
Reliable sector - between 8° and 40° from the nadir.
Depth to width ratio – between 4 and 6.
Number of averaging clips – between 10 and 50.
For specific types of seabed different values are advised.
For a sandy-flat area between 10 and 15.
For a seabed with a slope between 15 and 35.
For a seabed with ripples between 20 and 50.
Nadir area – use the default value of 10%.
Vertical tolerance inside reliable – between 0.03 and 0.10m.
Vertical tolerance outside reliable – between 0.05 and 0.15m.
The item Reliable sector is the reliable angle sector which is the sector
between the nadir and the reliable angle. All beams inside this sector
should be used to determine the average sway depth (ASD). In the
example above with a reliable angle sector of 30° ASD is about
10.25m.
With the ASD and the item depth to width ratio the maximum sway
width (MSW) can be calculated. In the example the maximum sway
width will be ‘depth to width ratio’ x ASD = 4 x 10.25 = 41m.
Starting from the nadir beam, all the beams farther away than the
MSW should be excluded from the computation. So all the beams in
the Outer area will be excluded.
The area that is left (this is the MSW) can be divided in three other
areas; Nadir area, Reliable area and Unreliable area. A very common
distribution for the MSW is 10% for the Nadir area, 60% for the
Reliable area and 30% for the Unreliable area. The Nadir area is a
parameter of the smart filter. At the moment the distribution as
mentioned above will be used in the smart filter.
Figure 13-71 Interferometry data with the averaging clips and the average
depths
Around the average depths a vertical tolerance can be defined. For the
Reliable area the tolerance can be set with the item Vertical tolerance
inside reliable and for the Unreliable area with the item Vertical tolerance
outside reliable.
With these two tolerances an offset from the average depths can be set.
The area between the two tolerances (above and below the average
depth) is the valid area. All the beams outside the tolerance areas will be
rejected by the smart filter.
Figure 13-73 Multibeam Video view of the RESON SeaBat 8125 with a depth
filter
A Numerics – Standard view can be filled with the information that the
user wants to see. Each view can have several pages and each page can
have a descriptive name. On the left hand side of the view are the names
of the pages and on the right hand side the items belonging to the
selected page. Both parts have their own context menu.
The first time this view is opened the user has to create a Numerics view.
Select the option New from the context menu of the left pane and create a
name for the view. In the new view, pages can be added by using the
option Add New Page from the context menu.
Each page can have several items on the right hand side. Select in the
context menu of the right pane the option Edit Page to add items to this
page. It will open a separate window where the page configuration can be
defined.
The page can also be filled by using the ‘Drag & Drop’ method from the
Raw Data view (see page 374).
Set the alarm and select which actions should be taken when an alarm
occurs. The action Blink Numerics item will start flickering the field of the
item in the Numerics view.
When the alarm is set it can be disabled again with the context menu
option Edit alarm. The same dialog as above will open and just uncheck
the option Enable Alarm.
After the alarm is disabled it can be removed with the context menu
option Remove alarm. It is also possible to leave the alarm linked to the
item and with Edit alarm the alarm can be edited and enabled again.
When this alarm is set it and the same item is set in the Numerics Layer
of the plan view, the item in the plan view will start flickering when the
alarm occurs.
The Numerics – Sonar Targets view is a view with a table where the
information about the created sonar targets is displayed.
The displayed sonar targets are stored in the sonar targets file as created
or selected in the Project Configuration (see page 63). The sonar targets
file name is displayed in the caption of the view; ‘Sonar Targets 4’ in the
example above.
Double click on a sonar target will open the Sonar Targets View with the
GeoTIFF image and the information which can be modified (see page
376).
The user can select in the Properties which columns have to be displayed
in the view. The Properties can be opened through the context menu.
In the context menu next to the Properties two other options are available;
delete the selected sonar target or delete all sonar targets. The delete
implement that the sonar target(s) will be deleted in the views and from
the active sonar targets file. Along with the sonar target(s) the
corresponding GeoTIFF file(s) of the image of the sonar target(s) will be
deleted.
For more information about the sonar targets see the Sonar Targets view
on page 376.
Figure 13-79 Output Control view for the RESON SeaBat 8125
Before one of these views can be selected, the output control has to be
added to the equipment list in the Equipment page (see page 96).
Select the option Tools > Equipment Control in the menu bar of the
Acquisition to add the Output Control view. Select the right output control
in the Add Equipment control display(s) window and click on to
add the view to the Acquisition. After the Output Control view is added the
window can be closed. From now on the view is available in the Displays
window where it has to same functionality as all other views.
Every change of one of the slides is send directly to the control unit of the
multibeam system. Use for the range and depth filter to send the
filter settings to the control unit. With all the
settings will be send to the control unit to setup the multibeam system.
A context menu and a properties window are not available for an Output
Control view.
Figure 13-80 Pipe Lay – Pipe Angle view with the J-Lay tower, the criteria and
the pipe.
Figure 13-81 Pipe Lay – Pipe Position view with both multibeam systems and
the detected pipe for the Pipe Position Monitor application
The view for the application ‘Pipe Position Monitor J-Lay’ is completely
different. The view shows a plan view of the vessel with the J-Lay tower,
the overbend and sagbend criteria, the used beams and the computed
pipe.
Figure 13-82 Pipe Lay – Pipe Position view with both multibeam systems and
the detected pipe for the Pipe Position Monitor J-Lay application
Figure 13-83 Pipe Lay – Sonar Video view with the pipe position for the Pipe
Position Monitor application
The view will be different for both application types, for the application
‘Pipe Position Monitor’ the display is from a RESON SeaBat 6012, while
for the application ‘Pipe Position Monitor J-Lay’ the display is from the
RESON SeaBat 8125.
In this view a plan view with 3 panes (bars) are displayed. The panes can
be used to display values that are useful for the survey, like the distance
to a waypoint or the offtrack.
Use the context menu in the panes to open the Layer Control to select in
the Up Down Indicator Layer the Source Item that have to be displayed.
In the pane any value available can be monitored. Default only one item is
displayed. It is possible to have more than one item displayed, just add for
each extra item an extra up-down indicator layer to the pane.
In this view the grid model, the 3D model, the dredge polygon, the
At the moment the dredge
disposal area and the historical tracks from the dredge instruction will be
instruction as a guidance is displayed.
only available for Boraciet, The Plan View – Dredge Instruction shows the location where the dredge
so also this Plan View can activity has to take place. In this view nothing has to be added, because
only be used for Boraciet.
all the relevant information is already loaded and displayed through the
dredge instruction.
When the vessel received a dredge instruction it can be selected in the
guidance as the new dredge instruction. Select from the menu bar in the
Acquisition the option Guidance > Guidance Settings or select from
the toolbar to open the Guidance window to select a new dredge
instruction.
A quick way to select a new dredge instruction is with the option
Guidance > Select Dredge Instruction… from the menu bar or with
from the toolbar in the Acquisition. A preview window will be opened
where all the available dredge instructions can be viewed and the new
dredge instruction can be selected.
Figure 13-86 Plan View – Dynamic Positioning with a bull’s eye and a waypoint
Figure 13-87 Plan View – General Dredge Operation with an updated grid
model
The Plan View – General Dredge Operation can be used for general
dredge operations where the active grid model will be updated
immediately after the bottom is dredged.
This view can be used in the Acquisition in conjunction with one or two
Profile – Realtime Design views (see page 366) to get a complete
monitoring of the dredge activity.
The Plan View – Navigation can be used for the navigation of the vessel.
For the background several options like C-Map or a DXF chart can be
used. All the options to navigate the vessel, like the different guidance
options, are available in this plan view. It is not possible to show any
survey data in this plan view.
With the view can be used as a Plan View – Dynamic Positioning (see
page 346).
The information from the C-Map background is available with the two
extra buttons ( and ). This option makes this plan view very useful
for a buoy laying vessel.
In the Plan View – Navigation an image layer of the wedge of a forward
looking sonar can be added. In this wedge sonar targets can be selected.
The Plan View - Production can be used to show the production with a
production grid model. This production grid model is the grid model that is
selected in the Logging page of the vessel configuration with the file
format ‘Production Format’ (see page 116).
The display and the options of the view are similar to the Plan View –
Survey Coverage (see below).
Figure 13-90 Plan View – Survey Coverage with an active grid model
The Plan View – Survey Coverage can be used to show the update of the
grid model. This grid model is the grid model that is selected in the
Logging page of the vessel configuration for the file format ‘PDS2000 Grid
Model’ (see page 116).
In this plan view the coverage of the survey can be shown, not only for a
multibeam survey but also for a single beam survey.
The Plan View – Survey Coverage can be used to display the sonar
targets as created in this view or in the Sonar Views.
Figure 13-95 C-MAP Object Information window with a radio calling point
Figure 13-96 Context menu in the Edit Mode and without user maps
Click on the active route or clipping polygon and the route or clipping
polygon can be edited. The way of editing the route or clipping polygon
will be identical as editing an object of the user maps (see below).
Before the user maps object can be viewed, added and/or edited, the
User Map Layer has to be added in the Layers window. If a file with user
maps objects exists, it can be selected in the properties of the layer.
After one of the user maps options is selected the cursor will change in a
cross. With the cross the location(s) for the user map object can be set in
the view. The way the different objects can be drawn will be explained
below.
Line
Click with the left mouse button on the locations for the line. Click on
the right mouse button to accept and finish the drawing of the line.
Rectangle
A rectangle can be drawn by selecting two opposite corners of the
rectangle with the left mouse button.
Polygon
Click with the left mouse button on the locations for the polygon. Click
on the right mouse button to accept and finish the drawing of the
polygon.
Circle
The circle can be drawn by selecting the center point and a point on
the circle with the left mouse button.
Text
Click with the left mouse button on the location where the text has to
be located and enter in the Name dialog the text.
Symbol
Click with the left mouse button on the location where the symbol has
to be placed and select a symbol from the list in the Select User
Symbol window.
For each selected symbol a symbol text can be entered. For the
symbol ‘Obstruction’ also the least depth can be entered. The text will
be displayed next to the symbol and the least depth in the symbol.
Figure 13-98 Select a symbol from the list in the Select User Symbol
window
Redo
Only available after an Undo and this option will reverse the last undo
action.
Undo
Reverse the last action.
Insert Point
Insert on the cursor location a point to the object. This is only available
for the Line and Polygon and also for the active route and the active
clipping polygon.
Delete Point
The point that is selected with the cursor will be deleted from the
object. This is only available for the Line and Polygon and also for the
active route and the active clipping polygon.
Delete
The edit mode for the active user map object will be closed and the
active user map object will be deleted. This is not possible for the
active route and the active clipping polygon.
Save
The edit mode for the active object will be closed and the changes
made in the object will be saved.
Cancel
The edit mode for the active object will be closed and the changes
made in the object will not be saved.
With new layers from the Add Layer window can be added to the
list of used layers in the plan view.
The layers are the items that are shown in the plan view, e.g. Run Lines,
Grid Model and Color Table. In the window the layers can be switched on
or off by checking or unchecking the specific entry of the layer.
Click on or double click on the selected entry to open the
properties of the selected entry. The properties are different for each layer
and the attributes in the properties can be for example file selections, line
styles, colors and computation selection.
The layer order can be changed by using and . The layer on top of
the layer window will be drawn first. The layers lower in the list will be
drawn on top of the layers that are above it in the list. If some information
in a layer is important and have to be shown in the plan view, move that
layer as far down as possible with the down arrow.
The entries in the ‘Active’ layers cannot be removed by the user. Most of
these active layers are linked to the selection in the Logging page (see
page 116) or the Guidance page (see page 131) of the vessel
configuration. For example, the layer Active Route Layer gives the route
that is selected in the Guidance page.
A special layer in the Layer Control is the AIS Layer. This layer will only
be available when in the Equipment a device driver from the group
Automatic Identification System is added to the equipment list. The
Automatic Identification System (AIS) is a short range coastal tracking
system used on ships and by Vessel Traffic Services (VTS) for identifying
and locating vessels by electronically exchanging data with other nearby
ships and VTS stations. Information such as unique identification,
position, course, and speed can be displayed in the plan view.
In the Properties window the ‘Follow Vessel’ mode and the Off-Center
option can be defined. These options are not available in the Plan View –
Dynamic Positioning view.
It is also possible to enter manually a fixed skew value for the orientation
of the plan view.
Below the relevant items in the properties will be explained.
Follow Vessel
The ‘Follow Vessel’ mode can be switched on and off.
Position Source
Any position source or position computation can be selected as
‘tracking point’ on the vessel for the follow vessel mode.
Follow Mode
The follow mode is by default Relative Motion; the vessel is always
displayed in the center of the view. Another option for the follow
mode is True Motion; the vessel will not stay in the center but the
view will update when the vessel is nearly leaving the view.
Vessel Radius
Vessel radius is the minimum distance from the vessel to the
edge of the view.
When the vessel comes in the minimum distance from the edge
of the view and with the follow mode on True Motion, the view
will be updated and the vessel will be placed in the center of the
view.
The vessel radius can also be used in combination with the off-
center (see below).
Off-Center
When the follow mode is set on Relative Motion the vessel can be
displayed out of the center of the view.
This option can be used when the user wants to look forwards for
Figure 13-102 Plan View with an off-center of -100% (left) and +100%
(right) with a vessel radius of 10
Orientation Mode
One of the three modes can be selected; North Up, Heading Up or
Fixed Skew (see page 354).
Fixed Skew value
A skew for the plan view can be entered. This is only valid when
the orientation mode is set on Fixed Skew.
Next to the view properties, all the attributes of the selected layers of the
Layer Control are available.
In the Coverage Settings window the color table for only the Z values (Z
Average, Z Minimum and Z Maximum) of the active grid model can be
selected. Also for the active grid model difference the color table can be
selected. Through this window it is easy to switch between the two grid
models and also easy to change a color table. The settings in the relevant
layers will be updated automatically.
The color tables for the other data types are automatically generated by
PDS2000 when the data type is selected through the grid model color
mode ( ).
If the active grid model has to be shown in the plan view, check the option
Grid Model at the top of the window.
Next to the color table, the sun illumination can be set. This will work only
for the active grid model and not for the grid model difference.
The sun illumination for a 2D grid model works similar as the spotlight
option in the 3D views. Move the yellow dot in the circle to set the azimuth
and the elevation. With the contrast bar the contrast can be set. It is also
possible to set all three the items manually. Check the option Enabled to
make the sun illumination active.
The sun illumination will not work directly when the yellow dot is moved.
grid model shown in the Plan View is then relative to sea level. It is pure a
visualization, it will not be logged. The information for relative sea level
will be extracted from the tidal information or, when RTK is used, from the
computed tide. When computed tide is used the sea level offset has to be
defined in the Geometry page (see page 93).
If an active grid model difference is available in the plan view and instead
of the active grid model an active grid model difference has to be shown,
check the option Difference. Select the right color table to present the
differences.
The grid model difference is computed with the data type that is selected
for the grid model.
Check the option Show color table if the color table has to be displayed at
the right side in the plan view. Can also be switch on/off with the option
Show Color Table ( ).
If multibeam data is available, check the option Show multibeam profiles
to show the data of the multibeam system. This is only valid for the Plan
View – Survey Coverage view and the Plan View – Production view.
Figure 13-105 Profile – Grid Model view derived from the ‘Draw Profile’ option in
the plan view
The Profile – Grid Model view shows a profile over a route or runline. The
profile can be from a grid model or from a design model.
The profile view is not an active view; the data will not be updated.
Therefore it will only be used in combination with the option Draw Profile
from the context menu of the Plan View – Survey Coverage, the Plan
View – Production or the Plan View – General Dredge Operation (see
page 353).
If the view is closed it will disappear from the list in the Displays window.
If the Profile – Grid Model view is added to the Acquisition through the
Displays window or with Add Display in the context menu, it will stay
empty.
Figure 13-106 Profile – Multibeam view with an active grid model profile
The Profile – Multibeam view can be used to compare the multibeam data
or the scanning profiler data online with a (active) 3D design model profile
or a (active) grid model profile.
When this profile view is created the active grid model profile layer and
active design model profile layer are already set. The active grid model
profile can be compared with the (active) design model profile if the
quality of the multibeam data is not so good.
The depths rejected by the filters will have a different color in the profile
view. The rejected depths are always logged in the raw data files, but not
in the cleaned data files.
Figure 13-109 Profile – Realtime Design view with a right view of a suction
hopper and the design difference as up/down indicator
The Profile – Realtime Design view can be used for a dredge application
to show the vessel with a drag head and the grid model and/or design
model. The view can be from the left, the right, the front or the back side
of the vessel.
The profile view can also be used in the (rope) excavator application to
show the (rope) excavator with grab or bucket and the grid model and/or
design model.
In the up/down indicator pane any value available can be monitored.
Default only one item is displayed. It is possible to have more than one
item displayed, just add for each extra item an extra up-down indicator
layer to the up/down indicator pane.
Figure 13-110 Profile – Realtime Design view with a left and a back view for an
excavator
Figure 13-111 Profile – Realtime Design 3 Bars view with a design model
The Profile – Realtime Design 3 Bars view can be used if more than one
indicator is needed in the profile view. In this example the left and right
indicator display the height of the left and right side of the structure above
the design model. The bottom indicator displays the difference between
the two other indicators.
If in a Profile – Realtime Design view two indicators are necessary, for
instance the absolute depth and the height above the design model, then
this profile view can be used. The bottom indicator can be slide away from
the view if necessary.
In the up/down indicator pane any value available can be monitored.
Default only one item is displayed. It is possible to have more than one
item displayed, just add for each extra item an extra up-down indicator
layer to the up/down indicator pane.
Figure 13-112 Profile – Realtime Design Antwerpen with an active grid model, an
active design model, dredge limits and level contacts
Default only one item is displayed. It is possible to have more than one
item displayed, just add for each extra item an extra up-down indicator
layer to the up/down indicator pane.
Figure 13-113 Profile – Realtime Design Cutter view with a grid model and a
design model
Default only one item is displayed. It is possible to have more than one
item displayed, just add for each extra item an extra up-down indicator
layer to the up/down indicator pane.
Figure 13-114 Profile – Realtime Design Pipe view with a top and side view of
the trailing suction hopper with a drag head
The Profile – Realtime Design Pipe view can be used for a trailing suction
hopper application to show the vessel with a drag head in a top and in a
side view.
The top view is a basic plan view where the relation between the heading
of the drag head and the suction hopper can be displayed.
The side view is identical with the Profile – Realtime Design view (see
page 366).
In the up/down indicator pane any value available can be monitored.
Default only one item is displayed. It is possible to have more than one
item displayed, just add for each extra item an extra up-down indicator
layer to the up/down indicator pane.
The Profile – Realtime Design Pipe Vertical view can be used for a trailing
suction hopper application to show the vessel with a drag head in a top
and in a side view and is identical with the Profile – Realtime Design Pipe
view (see above).
The top view is a basic plan view where the relation between the heading
of the drag head and the suction hopper can be displayed.
The side view is identical with the Profile – Realtime Design view (see
page 366).
Default only one item is displayed. It is possible to have more than one
item displayed, just add for each extra item an extra up-down indicator
layer to the up/down indicator pane.
Figure 13-116 Profile – Sound Velocity view of the active sound velocity profile
The Profile – Sound Velocity view is not an active view; it will not update
the sound velocity profile in the Acquisition. It shows the selected sound
velocity profile that is used to correct the depth readings of the multibeam.
The three of the four Profile – Realtime Design views have the same
Properties window, only the Profile – Realtime Design Cutter view has
less items. Some of the items are available for the Profile – Grid Model
view, Profile – Multibeam view and Profile – Sound Velocity view. The
Profile – Projected Runline view has different properties to define the
graph display.
The most relevant items in the Properties window of the profile views will
be explained below.
Follow Vessel
If Enabled, the selected attach point will always be in the center of the
view. For the Profile – Multibeam view the center beam will be in the
center.
Position Source
Any position source or position computation can be selected as
‘tracking point’ on the vessel for the follow vessel mode.
For the Profile – Realtime Design view, the Profile – Realtime Design 3
Bars view and the Profile – Realtime Design Antwerpen view the
position source has to be Drag-head Absolute Position.
For the Profile – Realtime Design Cutter view the position source has
to be Cutter Absolute Position Computation.
For the Profile – Multibeam view the position source has to be
Multibeam xyz computation.
Attach To
The position source can be attached to the Dredge Point or the Sensor
Reference Point.
Vertical Auto Ranging
If Enabled, a vertical zoom extents will be active.
Scale Mode
The display of the profile view has different scaling options; Fixed
Aspect Ratio, Fixed Vertically, Fixed Horizontally and Scale Freely.
The Raw Data view has in the left pane the tree with all the sensors, the
computations and the data sources. In the right pane the data of the
selected item as it is received from the sensor or is calculated in the
computation.
If there are no problems with the data all the items have the sign . If the
connection is lost the last data will still be shown in the view, but the sign
before ‘Data Buffer’ will change to . Also the Alerts view (see page 278)
will appear on the screen with the alarm messages. If the received data is
corrupted the sign for the ‘Data Buffer’ becomes and for all the items
the sign becomes . If some of the data items have the sign then that
data is not received or cannot be calculated.
The right hand side has a context menu with the options Properties and
Statistics. With the option Statistics the user can collect data over a self
defined period and it will calculate the mean, the standard deviation, the
minimum and the maximum of that collected data.
Only possible when the Double click on a data item on the left hand side will open the Properties
logging is switched off window of that data item. This Properties window is the same window as
in the Equipment page or Computation page of the vessel configuration.
Figure 13-119 Data item ‘GPS mode’ can be moved with the ‘Drag & Drop’
method
There will be three ways to enter a reference point for the Scatterplot
view:
1. The reference point can be entered manually in the fields ‘Ref. x’, ‘Ref.
y’ and ‘Ref. z’.
2. Click on to select the current position as the reference point.
3. With a double click on one of the available waypoints in the list the
selected waypoint becomes the reference point.
With ‘Tolerance 1’ and Tolerance 2’ tolerance circles will be drawn around
the reference point. They become visible as red circles in the bull’s eye
display.
The left side of the Scatterplot view has the following fields:
Reference x, y, z
The entered reference position.
Current x, y, z
The currently computed position.
Diff x, y
The difference between the reference position and the current position.
Average x, y, z
The average of the computed position.
DRMS
The Distance Root Mean Square value of the computed position. This
value is the radius of a circle into which the position will fall with a 68%
probability. Only useful for a stationary position.
Average diff x, y, z
The average of the difference between the reference position and the
computed position.
Sample no.
The number of current samples. If the option Limit is checked and a
value is entered the number of samples will stop when this limit value
is reached.
Bull’s eye
If checked, the bull’s eye circle will be displayed in the right top
display. The interval and number of circles depends on the scale in the
display.
Tolerance circles
If checked, the tolerance circles in red will be displayed in the right top
display.
DRMS circle
If checked, the DRMS circle as a dashed line will be displayed in the
right top display.
Figure 13-122 Three Sonar Targets views with sonar targets created in three
different views
All collected sonar targets will be saved in the selected sonar targets file,
which is available in the Sonar Targets Database of the Explorer (see
page 248). The corresponding GeoTIFF files are also stored in the Sonar
At the moment a set of sonar targets consist of one or more sonar targets
files and all the corresponding GeoTIFF files. Don’t forget to copy the
GeoTIFF files when a copy is made of the sonar targets. When no
GeoTIFF files are available no picture is available anymore.
Measure ( )
To measure a distance and a bearing in the plan view. On the first use
the measure starts at the vessel’s tracking point. With a mouse click
the start of the measurement can be at any location in the view. The
measure window shows start and end coordinates as well as distance
and bearing between the two locations.
Figure 13-124 Sonar – Sidescan view with for color palette rust and gray
For information about the toolbar and context menu of the Sonar –
Sidescan view see Sonar – Toolbar and Context Menu on page 379.
Figure 13-125 Sonar – Snippets view with for color palette rust and gray
For information about the toolbar and context menu of the Sonar –
Snippets view see below Sonar – Toolbar and Context Menu.
Contrast ( , )
Increase and Decrease the Gain.
TVG ( , )
Increase and Decrease the TVG (see page 380).
Auto Scaling ( )
Toggles between Auto Scaling Off (Out) and On (In) (see page 380).
Lambert’s Law Corrected ( )
Toggles between a Lambert’s Law correction Off (Out) and On (In)
(see page 381).
Ping Selection ( )
Select one of the four pings or all the pings to be displayed in the view.
Lines/Dots ( )
Toggles between Dot view (Out) and Line view (In).
Speed Correction ( )
Toggles between Speed Correction Off (Out) and On (In) (see page
380).
13.27.3.1 TVG
The Time Varied Gain applies a variable gain to the sonar data. The TVG
can make the color difference smaller or bigger between the data near to
the sonar and the data further away.
For example: If is out, increasing the TVG makes the data further
away lighter than the data near the sonar.
When zoomed in, press the left mouse button when the cursor is inside
the view and the cursor will change to a small hand. With the left mouse
button still pressed it is possible to pan through the view.
When a second Sonar – Bathy view is opened and the user zooms in on
the data then the outlines of this view will be visible in the first Sonar –
Wedge view.
The Act ping rate in the info layer on the left side in the view is showing
an average over at least 10 pings and 3 seconds.
The Status – Alarms view will show the alarms which are set by the user
in the configuration (see page 69) and/or in the vessel configuration (see
page 129). All the conditions in the alarm files are shown and the alarm
can be on ( / ), off ( ) or disabled ( ).
The Alarms dialog can be opened with Edit > Alarms from the menu bar
or with from the toolbar. Through this way only the existing alarms in
the configuration can be changed or new ones can be added to the
configuration.
With a double click on one of the alarms in the view directly the
Conditions window can be opened. Through this way also the alarms in
the vessel configuration are accessible.
The Alarms dialog and the Condition window are identical with the dialog
and window as explained in the Vessel Alarms on page 129.
Figure 13-129 Status – Equipment view with no data for some equipment
The Status – Equipment view displays the status of all sensors or outputs
created in the Equipment page of the vessel configuration. The view will
be red when at least one of the sensors has no data input ( or ). The
reason will be displayed in the ‘Input’ or ‘Output’ column, ‘Timeout’ or ‘---’
(no data). If all the sensors are working properly, all the data is received in
the system and have in front of the sensors, the view will be green.
This is only when the user has set the status color in the context menu.
The Status – Logging view displays the information about the data logging
such as file name, file size and logging rate. The view will be green when
logging is on and it will be red when the logging is switch off. If logging is
on and conditions are checked in the Logging page (see page 126) the
view becomes yellow if the condition is not true and the logging will be
suspended. This is only when the user has set the status color in the
context menu.
If the view is green it is obvious which file is logged and in which directory.
A Tide Manual Input view is not a standard view which can be added
through the Displays window or the Add Display option in the context
menu of the Acquisition. With this view a manual input for the tidal
information can be given.
Before the view can be selected, a manual input device for the tide gauge
has to be added to the equipment list in the Equipment page (see page
96).
Select in Acquisition the option Tools > Equipment Control in the menu
bar to add the Tide Manual Input view. Select the right device control in
the Add Equipment control display(s) window and click on to add
the view to the Acquisition. After the view is added the window can be
closed. From now on the view is available in the Displays window where it
has to same functionality as all other views.
If the option Force Manual Tide is checked the manual input becomes the
primary data group in the data sources for the tide computation (see page
103). A modified tide value in the view will be directly used in the tide
computation.
A context menu and a properties window are not available for the Tide
Manual Input view.
On the right side in the view the actual value of the data channel is
displayed with below the value the text ‘1/div’. This means that the
distance between two horizontal lines in the graph is 1 unit of the data
item. On the bottom the total length of the X-axis is displayed in hours,
minutes and seconds.
When this view is selected for the first time in the Acquisition by default
one channel is already added to the view.
If more than one graph is displayed as in the example above, the graph
where the text is underlined is the active graph. To make a graph active
just click with the mouse in that graph.
A data channel can also be added by using the ‘Drag & Drop’ method
from the Raw Data view( see page 374).
14.1 Introduction
Data recorded in the PDS2000 logging format can be replayed in this
module. By changing the vessel configuration before a replay is started,
the data will be recomputed with the new vessel configuration settings.
Replayed data can be recorded again into new log data files. To
distinguish replayed log data from the original files, the replayed file gets
an ‘R’ and the date and time of the replay in the file name.
The three options to start the replay from the Control Center are:
If the Replayer is open it is also possible to change the file set selection.
For a project with more vessels, instead of a file set bar, a vessel bar can
be displayed. Select from the menu bar the option View > Vessel Bar to
get the vessel bar in the toolbar. With the option View > File Set Bar the
above displayed toolbar comes back.
When a logdata files are loaded in the Replayer, automatically the layout
used in the first logdata file will be opened.
When no external layout is used, the option Keep same layout when
playing files should be checked to use only one layout during the replay of
the log data files.
15.1 Introduction
The goal of a survey usually is a presentation of the results in the form of
tables, charts and files. Before the presentation is finalized the data is
normally checked for anomalies, outliers and measuring faults.
Sometimes it is also necessary to correct a survey for influences that
could not be measured in real time, e.g. tides.
16.1 Introduction
In the Editing, the user can check the data for outliers, anomalies and
measuring faults. If necessary, it is possible to remove or correct the data.
Each view is an editor and each editor takes its data from the PDS2000
data files. The data can be edited in the data files (see page 416 for an
explanation) and the corrected data is directly available after editing.
In contrast with other programs, a separate processed data file or
database is not been made. Indexing and caching takes place in the
PDS2000 data files. That means that the file size increases significantly.
The advantage lies primarily in having both original (raw) and processed
data in one file. This allows the user to revert to original data when
needed.
Please note that only the data from PDS2000 data files can be edited with
these editors.
Select Processing > Editing from the menu bar or click on in the
toolbar of the Control Center to start the Editing.
Check the files to edit and click on . If the files are opened for the
first time, an index and cache will be created. This may take some time;
progress will be shown in the Progress dialog.
Figure 16-5 Displays window to add, to switch on/off or to remove views in the
Editing
In the Displays window, the editors can be checked on or off. This means
that only the checked editors will be displayed on the screen. The editors
that are checked off are not removed; it only means that these editors are
not shown on the screen. An editor can be removed by using in
the Displays window.
After all the wanted editors are selected and moved to the right location in
the Editing the layout can be stored. Select File > Save Layout As… from
the menu bar to save the new layout. To open another layout use File >
Open Layout… from the menu bar and select one of the created layouts.
16.2.4.1 Jumping
Click on or and the red indicator (red stripe) in the data bar will
jump to the previous or next file in the file set. A click in the data bar
brings the red indicator to a specific record in the file. Cursors or locators
in all open editors will go exactly to that point.
The Find window can also The Find window ( ) has, depending on the active editor, a maximum of
be opened with Edit > Find three find detectors; high value, low value and spike. In the Position
from the menu bar.
Editing and in the Line-Based Editing the spike detector checks the angle
and the amplitude. In the Time-Based Editing, the spike detector checks
the deviation and the deviation per second.
Click on to add the values for the selected detector. The detector
can be activated by checking the checkbox before the detector. All the
detectors will be active in the current data file or in the entire file set. Click
on or to search for the exceptional data points.
When an anomaly is found, one of the two actions, Delete or Interpolate,
is possible. Click on to activate the selected action.
The last Vessel in the list is the active vessel configuration. Select a
different vessel configuration and click on to accept. Then this
Figure 16-11 Vessel Selection Dialog with an invalid active vessel configuration
The method to fix this problem is to use the Repair File option (see page
414).
Figure 16-12 Dialog when active vessel configuration is different from the other
vessel configurations
In the list above it is possible that not all files from the File Set are
displayed. The settings of the missing files are identical with the leading
(active) vessel configuration.
Click on to apply the settings of the leading (active) vessel
configuration to the listed vessel configurations in the File Set.
Select a computation mode and one or more tide stations. For multiple
tide stations along a route select at ‘Selected route’ the appropriate route.
Click on and the tide data is applied to the logdata files in the file
set. If there are problems with applying the tide data, a data error window
appears. This window shows the cause of the data error(s) and to which
data files no tide data is applied.
There are several methods to check if the tide data is applied correctly to
the file set.
Check the height method used in the reference point computation.
Select Tools > Edit Vessel from the editing menu. On the tab
Equipment select under the positioning system the computation ‘
Reference Point Computation’ and click on to open this
computation. The item ‘Height Source’ should show Tide and the item
‘Tidal Data Source’ should point to the tide computation.
Open in the Time-Based Editing – Standard view (see page 495) from
‘ Reduced depths’ the data channels ‘Depth ref. Sealevel’ and
‘Depth ref. Chart Datum’. Overlay the two graphs in the editor and the
difference between the two data channels should be the applied tide.
It is also possible to view the applied tide data in the editor. Select
from the ‘ Reference Point Computation’ the data channel ‘Applied
Tide’.
Open the Tide Station – Viewer (see page 493). This viewer shows the
applied tide data for the selected file set.
Select in the data source selection page the data source that have to be
switched. Below the list of data sources one of the two options have to be
selected.
Select option Set for whole file when the data source switch has to be
applied to the active logdata file. Click on to select the order in the
data groups.
Figure 16-17 Data groups page of the Data Source Switch Wizard
Select in the data groups page the order of the computations. Click on
to apply the first computation from the list as the primary data
source to the active logdata file.
When in the data source selection page the option Advanced editing is
selected, it is possible for the user to set his own data source switches on
Figure 16-18 Data elements page of the Data Source Switch Wizard
Select in the data elements page the item that has to be opened in the
Data Source Switching view. In the view a channel is created for each
data group of the selected data source. Next to these channels, also an
extra channel is created with the data source switch. At the bottom of the
view the primary data is displayed; this is the data from the primary parts
of the different data groups. See for an explanation of the Data Source
Switching view on page 428.
Click on this button to create a new empty cable route; the as laid
cable route. This file will be automatically selected as the as laid cable
route in the above option.
Cable diameter
The cable diameter will be used to calculate the depth of the cable.
Sample interval
The interval along the cable route where the cable will be generated.
Average length
Over the average length on the sample interval location one position
and depth will be calculated and added to the as laid cable route.
Cable burial method
This is the method that is used or will be used to detect the burial
depth of the cable. In the ‘ Dredge Absolute Plough Knife’ of the
Dredge Positioning System the depth can be calculated from the
Position or from a Model.
Realtime selected is the method (Position or Model) that is selected
during the Acquisition.
Reject detection exceeding offtrack to a planned route
Check this option when the detection has to be rejected if the offtrack
to the planned route is more than the entered Maximum offtrack.
Click on this button if only from the selected file the cable has to be
generated.
Click on this button if from all the files in the selected file set the cable
has to be generated.
Report Style
At the moment only one report style for the statistics report is
available.
Show Report
If this option is checked then the report will be displayed in the
PDS2000 Reporter.
It is very important that the SBET files contain UTC time (not GPS time).
The SBET and SMRMSG files have to be named in a special way. The
file name must contain the start date of the data in the following format:
sbet_YYYYMMDDxxx.out
smrmsg_YYYMMDDxxx.out
Select Tools > Import Post-Processed GPS Data > POSPac… from the
menu bar to open the Open dialog to select the SBET file(s) for the
import. This dialog will only open when PDS2000 logdata files are loaded
in the Editing. It is possible to select one or more SBET files in the dialog.
The position is the latitude, longitude and the altitude of the position
device. The attitude is the roll, pitch and heave of the VRU device. The
heading is the heading of the compass device.
Before the import is started, PDS2000 will check if for the position in the
PDS2000 logdata files a POS MV device driver is used. If this is not the
case, the import will not be done.
All dependent computations will be recached when necessary. It is always
possible to revert to the original data by using the Revert to Original
option ( ).
It is very important that the PTS files contain UTC time (not GPS time).
Select Tools > Import Post-Processed GPS Data > TerraPos… from the
menu bar to open the Open dialog to select the PTS file(s) for the import.
This dialog will only open when PDS2000 logdata files are loaded in the
Editing. It is possible to select one or more PTS files in the dialog.
All dependent computations will be recached when necessary. It is always
possible to revert to the original data by using the Revert to Original
option ( ).
To see the impact of the changes in the dialog it is advisable to have the
Multibeam Area Editing – Standard view open.
Device
Select for which multibeam or laser scan device the calibration values
have to be displayed.
Click on this button to get for the roll, pitch and yaw the original values,
as stored in the files.
Roll, Pitch and Yaw
Move the sliders to change the values. The changes will be directly
visible in the Multibeam Area Editing – Standard view.
With these changes, the user can see if the actual values are valid for
the data set.
Calibration setting
When the values for the roll, pitch and yaw are set then it is possible to
apply these to a data set; to log data files, to a file set or to the vessel
configuration. For each option, a dialog will be opened to select the
right data set or vessel configuration.
Click on to close the quick calibration dialog.
If more than one multibeam is available in the view select the multibeam
for which the TPE results has to be computed.
For the error model two options are available:
CUBE implementation; horizontal error without the fore-aft
beamwidth error
CHS implementation; horizontal error with the fore-aft beamwidth
error
Check the option Use Multibeam Uncertainty when the real-time
uncertainty values have to be used. Uncheck the option when the range
error has to be computed.
Click on to generate the TPE text file. The text file is saved
in the project folder and can be found as text (TXT) file in the Explorer. In
the filename is composed from the ping number, date and time of
generation.
The text file can be opened with the special created Excel sheet that is
available in the PDS2000 folder and is called ‘TPEview.xslm’. When the
sheet is opened click on the button, select the right text file and the table
and graph are automatically generated. Below an example of a table and
graph.
Click on to recache all the data files of the file set or click on
to recache only the selected data file. Click on if it is
not necessary to recache the data file(s).
Click on to revert to the original data only for the selected data
file or click on to revert to original data for all the data files in the
file set. Click on if it is not necessary to revert to the original
data.
Click on if the repair has to be done only for the active logdata
file or click on if the repair has to be done for all the files of the
file set. Click on if no repair has to be done.
When the edit mode is ‘Normal’ ( ) then a right click on the selected
When the edit mode is point(s) gives a context menu with edit possibilities:
‘Delete’ ( ), selected
Delete: Delete the selected points.
points are deleted Undelete: Undelete the deleted points in the selected area.
immediately. If the mode is Interpolate Cubic: Between the start and end point of the selection an
interpolation with a curve is done.
‘Undelete’ ( ) the
selected deleted points Interpolate Linear: Between the start and end point of the selection a
come back. linear interpolation is done, so a straight line will be result.
Fill Gap: When there is a gap in the position data (for instance surveyed
under a bridge), the gap will be linear interpolated using a constant
heading and speed.
Smooth: The selected points will be smoothed.
Move: The selected points can be shifted; a dialog gives the possibility to
enter a shift in X and Y direction.
Edit: The selected points will have a new position; a dialog gives the
possibility to enter a new position for the first point in the selection, the
other points will be relocated with the difference as before.
Info: Give the data block info view. Double clicking on a single point will
immediately give the data block info.
The points can be moved by dragging them. Points once edit get a
different shape, a dot instead of a small cross. This is to indicate that edit
actions have taken place on that point.
The data points from the inactive layers, which are related to the data of
the active layer, are automatically updated when the data points are
edited.
The editing of the multibeam data in the 3D Box view is similar as the
editing in the other 3D views (see page 416).
The data in the 3D Box view will not be updated when in the Multibeam
Area Editing – Standard view a new grid model or CUBE model is added.
When the 3D Box view is closed in the Editing it will not be available
anymore as a view in the Displays window (see page 398).
again without unfiltering the data.
This option will make all selected data valid again, except the manual
rejected data. Draw a polygon around the data that have to be valid
again and all the data becomes valid. The data can be recognized by
its own filter color (Ignore Filters).
Clear Ignore Filters ( )
The ignore filters setting will be undone. Select the data by drawing a
polygon, which have to be bigger than the ignore filters area, and all
the selected data gets their own filter setting back.
Multibeam – Export Multibeam Points To ASCII…
The XYZ of the multibeam data as displayed in the view will be
exported to a file with extension ASC.
16.5 3D View
The 3D View – Standard is only a viewer, it is not an editor. Next to the
multibeam data from the file set, it can show a grid model or a 3D design
model in 3D with some extra information.
equipment list and the first multibeam is uncheck then no multibeam data
will be displayed in the view. Open with the Layers window, add a
Multibeam Layer and select in the properties of the layer for the
‘Multibeam Data and Position Source’ the ‘Multibeam xyz computation’ of
the active multibeam system.
If no color table is available or selected, PDS2000 automatically
generates a color table based on the depth values in the data.
The multibeam areas that are covered by the edit circle will be displayed
in high-resolution, all other data is shown in low-resolution with the right
colors.
Show Spotlight ( )
The light intension does Toggles the spotlight window on/off. It is also possible to toggle with
not work on the multibeam the key ‘o’.
data. With the spotlight window, the light intension and light source location
in the viewer can be modified.
Click on the yellow ball and move it around in the circle. How further
away from the center how less intense the light will be. The location of
the yellow ball in the circle gives the location of the light source.
Save Snapshot
The display of the view can be saved as a JPG or BMP file.
Grid Axis Layer ( )
Toggles the cross on/off.
Show Color Table ( )
Toggles the display of the color table on/off.
Multibeam Layer ( )
The multibeam data can be switched on/off in the view. If the button is
active, extra buttons will be added to the toolbar.
Beam Color Mode ( )
The multibeam data can be show in different color modes to help to
analyze the data. See page 425 for more information about the beam
color mode.
Background Color
The background color of the view.
Color Table Name
Select a color table and all the relevant layers in the view will use it.
Follow Vessel
If the follow vessel mode is Enabled the view will follow the others
editors in the Editing.
Scale Factor
The scale factor of the Z-axis. Scale factor > 1 will enlarge the data in
the Z direction.
All other options in the Properties are similar with the options in the
toolbar and in the context menu (see page 422).
After the properties, the selected layers in the Layer Control are available
in the Properties window. It is not necessary to open the Layer Control to
modify something in one of the layers.
This layer has to be added to the Layers window before the multibeam
data can be shown in the view. Before any data can be displayed, the
‘Multibeam Data and Position Source’ has to be selected.
In the Layers window only the used layers will be shown, any new layer
has to be added to the list in the window. The layers that can be added to
the layer control are:
This editor cannot be created through the standard editor selection in the
Editing (see page 398). This editor can only be opened with the option
Tools > Data Source Switching… from the menu bar of the Editing. After it
is created, it will be available in the Displays of the Editing. See the
chapter Data Source Switch on page 405 how to setup the Data Source
Switching editor.
Select the data group that has to become the primary data source and
use to move the selected data group to the top. Click on and
the data source switch will be inserted on the selected location. If the data
of the different data groups is different than in the lowest channel the data
will be changed from the selected location onwards.
On the location where a data source switch is inserted a cross will be
visible in the data. The size of the cross can be modified in the channel
properties of the data source switching channels by changing the value
for the dot size.
The data shown in this view is limited to the items that are defined in the
Dekdienst Channel Manager ( ). With the user can decide to
show the selected data item only in the graph (grafiek), only in the text
(tekst) at the bottom or in both.
Figure 16-42 Dekdienst Channel Manager with the items for the Dekdienst view
Figure 16-43 Line-Based Editing – Standard, with two stacked data channels
The Line-Based Editing – Standard view can also show data from a
second file set with the restriction that the data was surveyed over the
same runline. This data is only for comparison and cannot be edited.
Select the ‘Properties’ in the context menu and give a name for the
second file set.
To show this data select the ‘Channel Properties’ in the context menu and
enabled the option Enable under the name ‘BkgndLineDL’. This has to be
done for the each view (= channel) in the editor.
Figure 16-44 Properties (left) and Channel Properties (right) to select and
enable a second file set
Figure 16-46 Line-Based Editing – Standard; with second file set and a profile
of a grid model
Figure 16-47 Line-Based Editing – Multiline, with three surveys over the same
runline
Zoom Window ( )
With dragging a window in the active channel a part of the channel can
be zoomed in.
Zoom Extents ( )
Show all the data for all the channels.
Selector ( )
Toggles the ‘Selector’ on/off.
Channel Partition
If more then one line with offtrack data or selected data is displayed it
Figure 16-48 Messages – System Messages view with information for the
Editing
The Multiple Area Editing – Standard view will by default always display
multibeam(1) when it is opened for the first time. This is the first
multibeam system in the Equipment list. When multiple multibeam
systems are selected in the equipment list and the first multibeam is
unchecked then no multibeam data will be displayed in the view. For the
CUBE and Grid Model control open with the Layers window, add a
Multibeam Layer and select in the properties of the layer for the
‘Multibeam Data and Position Source’ the ‘Multibeam xyz computation’ of
the active multibeam system. For the Multibeam Filter and Multibeam
Calibration a different multibeam system can be selected.
In the Multibeam Area Editing – Standard view are the following modes
available:
CUBE Model mode (see below)
Grid Model mode (see page 446)
Multibeam Filter mode (see page 456)
Multibeam Calibration mode (see page 459)
Pipe Detection mode (see page 460)
CUBE model will be opened. When the file set is identical with a CUBE
model that is generated before no new CUBE model has to be generated.
Just click on in the toolbar of the view and the existing CUBE model
will be displayed.
Figure 16-49 Multibeam Area Editing – Standard view with a CUBE model and
multibeam data both in depth color mode
16.10.2.1 CUBE
In the traditional multibeam echo sounders processing method all
measured data points are treated with the same accuracy. However, in
reality each data point has a different accuracy. The question is then how
can the different accuracies of the data points be determined, how can
the possible errors be measured, what is the impact of the errors on the
Figure 16-50 Create page for a CUBE model in the Multibeam Area Editing –
Standard view
In the Create page for the CUBE model in the Multibeam Area Editing –
Standard view the cell size for the CUBE model can be defined and areas
likes wrecks or along a route can be excluded from the creation of the
model.
Cell size
Default an automatic setting of 10% of the depth of the multibeam data
is used as the cell size. It is also possible to enter a cell size, where
the user has to realize that the smaller the cell size the longer it will
take to generate the CUBE model.
If the density of the multibeam data is high, a small cell size can be
entered. However if the cell size is too small, gaps in the CUBE model
will appear.
If the cell size is too big, it is possible that the CUBE model is not
presenting the right model. This is due to the relation between the IHO
order and the cell size to determine what the best surface is for the
CUBE model.
IHO Order
The IHO order will be used to filter the data that is used for the
creation of the CUBE model. If the vertical and horizontal total
propagation error of a beam is bigger than the IHO error then the
beam will not be used for the CUBE model. See for an explanation of
the IHO order on page 330, for the vertical TPE on page 316 and for
the horizontal TPE on page 317.
Figure 16-51 Info page for a CUBE model in the Multibeam Area Editing –
Standard view
In the Info page for a CUBE model in the Multibeam Area Editing –
Standard view the information of the CUBE model and one selected cell
of the model are presented.
Model
The cell size and the number of hypotheses of the CUBE model is
given.
Current surface
The current surface as presented in the view will be displayed, in the
Figure 16-52 Edit page for a CUBE model in the Multibeam Area Editing –
Standard view with one of the edit modes selected
In the Edit page cells can be removed from the main surface or data from
It is always possible to other hypotheses can be select for the main surface.
rotate and shift the view
The cells can be selected by drawing a polygon around the cells or by
using the mouse wheel as
a button. selecting one cell with the Ctrl key and a mouse click.
When one of the edit modes is selected, the Edit tab will have a red box
to indicate that one of the edit options is active (as shown in the example
above). Even when the user switches to a different page in the editor it is
still clear that one of the edit modes is active.
The edit mode can be switched off by selecting the edit mode None or
click with the right mouse button in the view.
Figure 16-53 Filter page for a CUBE model in the Multibeam Area Editing –
Standard view
the CUBE model. The filters only work on the CUBE model that is
displayed in the view. The main criterion is the vertical distance between
the multibeam data and the CUBE model.
Filter
Select one or more of the following options to reject points.
Distance from CUBE surface exceeds the standard deviation
A beam will be rejected when the vertical distance between the Z of
the beam and the CUBE surface is larger than the standard
deviation of the CUBE model cell multiplied with 1.0, 2.0 or 3.0.
Distance from CUBE surface exceeds uncertainty
A beam will be rejected when the vertical distance between the Z of
the beam and the CUBE surface is larger than the uncertainty of
the CUBE model cell multiplied with the factor as is entered here.
Distance from CUBE surface exceeds
A beam will be rejected when the vertical distance between the Z of
the beam and the CUBE surface is larger than the value as is
entered here.
Don’t filter problem areas
The beams which are related to a CUBE model cell with a strength
> 0 will not be filtered.
Click on to start the filtering of the multibeam data.
Unfilter
Click on to add all the beams, which were rejected by the
CUBE/grid model filter, back to the multibeam data.
Instead of unfiltering all the beams, it is possible to select manually
the beams that have to be unfiltered. Check the option Enable
selection mode and select with the mouse the beams that have to
be unfiltered.
Figure 16-54 Export page for a CUBE model in the Multibeam Area Editing –
Standard view
Figure 16-55 Sync page for a CUBE model in the Multibeam Area Editing –
Standard view
The CUBE synchronization will update the CUBE model after deleting or
undeleting multibeam data in the view.
When the option Auto sync CUBE model is checked, the CUBE model is
automatically updated only after each delete or undelete operation in the
Multibeam Area Editing – Standard view.
When multibeam data is deleted with the delete mode ( ) or undeleted
with the undelete mode ( ) and the option is unchecked then the button
becomes active. Also in the tab of the Sync page, a red box
will appear to show that the multibeam data is modified (see above). Now
the CUBE model can be synchronized with the multibeam data by clicking
on . The red box stays in the Sync tab until the CUBE model is
synchronized, even when the user switch over to a different page.
If the option Auto sync CUBE model is unchecked and the Multibeam
Area Editing – Standard view or the Editing is closed or a different file set
is opened, then a prompt will be shown to ask the user if he wants to
update (synchronize) the CUBE model with the modified multibeam data.
Figure 16-57 Create page for a grid model in the Multibeam Area Editing –
Standard view
When the cell size is set and the cell data is selected click on
to create the grid model from the multibeam data as loaded
in the view.
When the grid model is created, the name of the grid model will be
displayed above the tabs in the left pane.
Figure 16-58 Info page for a grid model in the Multibeam Area Editing –
Standard view
In the info page the information of the grid model and of the selected cell
is displayed. Also a report of the grid model can be generated.
Grid model
The cell size and the available statistical information of the grid model
will be displayed.
Cell size
The size of the cells in the grid model.
Used cells
The total number of cells used in the grid model.
Used area
The total used area, i.e. the number of used cells multiplied by the
cell size.
Edit cell
The cell information of a selected grid model cell. The cell can be
selected by double clicking on the cell. When the cell is selected it is
possible to edit the values.
Click on to clear all the values in the selected cell.
Select a data type and the value can be modified, click on to
set the new value.
Figure 16-60 Edit page for a grid model in the Multibeam Area Editing –
Standard view
In the Edit page the data of the grid model can be edited. Cells can be
deleted and interpolated if necessary.
None
The Edit mode is switched off.
Delete
The selected cells of the grid model will be deleted.
There are three methods to delete one or more cells:
1. Delete one point by clicking on the cell with the cursor in
combination with the Ctrl key.
2. Delete more cells by placing the cursor on the right location. Keep
the left mouse button pressed in combination with the Ctrl key and
move the cursor over the grid model data. It looks like erasing the
data.
3. A different method to delete more cells is by drawing a polygon
around the points that have to be deleted. All the data that is
present inside the polygon will be deleted. The polygon can be a
polygon with line segments or it can be a free drawn polygon
(lasso).
Interpolate circular
Interpolate the gaps in the grid model with the circular interpolation. In
this interpolation all the Z data types (the Z Average, the Z Maximum
and Z Minimum, if available in the grid model) will be interpolated.
Figure 16-61 Filter page to remove spikes in the grid model in the mUltibeam
Area Editing – Standard view
In the Filter page the settings can be set to find and remove spikes in the
grid model and the removed cells will be interpolated with a circular
interpolation.
Ignore Area Options
Select clipping polygons which cover areas of the gird model that
ignored when PDS2000 is searching for spikes. This can be used to
ignore wrecks from the spike detection.
Figure 16-62 Spikes previews in Red on Green (left) and in User color
Filter Options
Evaluation area size
Select an evaluation area size; for each type of area a different size
for the despiking is needed. For each area a mean is calculated
and with the threshold a spike can be detected in the area.
Threshold
The threshold is a kind of standard deviation for each area.
For an irregular area a small threshold (f.i.0.5) will give more spikes
than a threshold of 5. How bigger the threshold the more
irregularity is accepted as no spike.
Selection area
The despiking can be done for the complete grid model with the
options Entire Model’. The spikes are found after on
is clicked.
With Select area select an area of the grid model by drawing a
lasso around the area with spikes. The spikes are found when the
lasso is drawn.
or
The ‘Find Spikes’ button is only active when as selection area the
entire model is selected.
Click on the button to find the spikes in the grid model.
The ‘Find & Remove Spikes’ button is only available when the option
Show Preview is unchecked; the detected spikes will be removed
immediately after they are detected.
When Show Preview is checked the spikes become visible in the view.
Click on the button to remove the spikes. The spikes will be replaced
by interpolated data from the cells around the spike(s).
Figure 16-63 Beam Filter page for a grid model in the Multibeam Area Editing –
Standard view
In the Beam Filter page the settings can be set to filter the multibeam data
with a grid model. The main criterion is the vertical distance between the
multibeam data and the grid model.
Filter
Distance from grid model exceeds standard deviation
A beam will be rejected when the vertical distance between the Z of
the beam and the grid model is larger than the standard deviation
of the grid model cell multiplied with the factor as is entered here.
Separate values can be entered for above and below the grid
model.
Distance from grid surface exceeds
A beam will be rejected when the vertical distance between the Z of
the beam and the grid model surface is larger than the value as is
entered here.
Separate values can be entered for above and below the grid
model.
The filtered data will be visible in the view with the color of the
CUBE/grid model filter, if the Beam Color Mode is set on Filter.
Unfilter
Click on to add all the beams, which are rejected by the
CUBE/grid model filter, back to the multibeam data.
Instead of unfiltering all the beams, it is possible to select manually
the beams that have to be unfiltered. Check the option Enable
selection mode and select with the mouse the beams that have to
be unfiltered.
Figure 16-64 Export page for a grid model in the Multibeam Area Editing –
Standard view
The mean beam Z deviation of all the beams relative to the grid model
can be exported to a CSV file. For each beam the mean beam Z deviation
for the four multipings (if available), the single ping and the beam angle
will be exported. Click on to start the export.
Figure 16-65 Sync page for a grid model in the Multibeam Area Editing –
Standard view
The grid model synchronization will update the grid model after deleting or
undeleting multibeam data in the view.
Multibeam
Before the multibeam filters can be added or modified, select the right
multibeam at the top of the page. If more than one multibeam is
available in the Equipment list then one of these multibeam systems
can be selected. By default always the first system in the Equipment
list is selected.
Figure 16-67 Calibration mode with a Multibeam Area Editing – Standard view
and the three Profile views
Figure 16-68 Pipe Detection mode in the Multibeam Area Editing – Standard
view with a detected pipe
Figure 16-69 Create page to create a pipe route in the pipe mode of the
Multibeam Area Editing – Standard view
Pipe route
Select an existing track guidance pipe route that represents the as laid
pipe route; this pipe route will be overwritten with new pipe route data.
Or create a new pipe route with . This new file will
be automatically selected as the as laid pipe route.
As Planned pipe route
Select a track guidance pipe route that represents the planned pipe
route.
Pipe detect diameter
The pipe diameter, which will be used in the correlation filter. With the
pipe diameter, also the depth of the pipe can be calculated.
Use Correlation Filter
If checked, the correlation filter will be used. The correlation filter is
looking for a shape in the multibeam data like shown below.
Correlation factor
In general, the correlation factor will be between 20% and 80%.
Click on this button if only in the selected file the pipe has to be
detected.
Click on this button if in all the files from the selected file set the pipe
has to be detected.
Show pipe detection
The detected pipe will be shown in the view.
Figure 16-71 Edit pipe option in the Multibeam Area Editing – Standard view
When the view is opened, in the data of the Multibeam Area Editing –
Standard view a profile is drawn on the current record location. In the
Multibeam Area Editing – Standard view the profile can be modified if
needed. A new profile can be drawn with from the toolbar of the Svp
Edit Profile view.
Next to the current sound velocity profile, a second sound velocity profile
can be selected with the option that it can be edited. Both sound velocity
profiles will be displayed on the left side in the view. In the sound velocity
profile view on the left side, the small boxes can be selected and dragged
around in the view to modify the sound velocity profile.
In the left pane in the view some actions/options can be selected.
Edit file name
Select a sound velocity profile that has to be edited. This can be the
same sound velocity profile as the current sound velocity profile or it
can be a different sound velocity profile.
The selected sound velocity profile is displayed in red with small boxes
which can be moved.
The selected sound velocity profile will be directly assigned to the data
shown in the profile. The user can see immediately what the influence
is of the sound velocity profile on the multibeam data.
Use Surface Sv
Select this option when the surface sound velocity has to be used in
the editable sound velocity profile.
The location of the surface sound velocity is displayed as a white dot
in the sound velocity profile.
Preview Mode
Each modification of the sound velocity profile will update the
The editable sound velocity profile can be saved and a new filter
position will be added with the new sound velocity profile.
The editable sound velocity profile can be saved and the current
filter position will be updated with the new sound velocity profile.
Show Spotlight ( )
Toggles the spotlight window on/off. It is also possible to toggle with
the key ‘o’.
The light intension does
not work on the multibeam
With the spotlight window, the light intension and light source location
data. in the viewer can be modified.
Click on the yellow ball and move it around in the circle. How further
away from the center how less intense the light will be. The location of
the yellow ball in the circle gives the location of the light source.
Pan ( )
Keep the left mouse button pressed to pan through the data in the
view.
Measure ( )
A distance can be measured in the view. Click on a point in the view
Figure 16-74 CUBE model with the main surface strength as color mode
Hit Count
The CUBE model is displayed with the colors that will present the
number of hit counts per cell, with green for a hit count of 1 to red
for the maximum number of hit counts in the CUBE model.
Figure 16-76 CUBE model with the hit count as color mode
Figure 16-78 Hypothesis 1 surface of the CUBE model with the selected
data in main surface as color mode
CUBE Surface ( )
Different surfaces can be selected:
Main
The best surface as calculated in the CUBE model.
Figure 16-79 Laser scan data with the color mode Laser Color
Laser Intensity
In the laser scan data the intensity of the laser scan data is logged.
This intensity can be used as color mode to display the laser scan
data in a grey scale.
With the items Start Brightness Ramp (SBR) and Brightness Ramp
Range (BRR) in the Properties of the view the brightness of the
intensity can be defined.
From 0 – SBR:
The data is displayed with the intensity as received from the
laser scan.
From SBR – (BRR+SBR):
The data is displayed with the intensity as received from the
laser scan plus an extra intensity value started at SBR with 0
and ends at BRR+SBR with 1. Between SBR and BRR+SBR it
will be linear interpolated. This means that the data further away
gets an extra intensity to make that data more clear in the view.
Figure 16-80 Laser scan data with the color mode Laser Intensity with
BSR=50 and BRR=50
Figure 16-82 Laser scan data with the color mode Laser Color +
Intensity
Figure 16-83 Laser scan data with the Beam Color Mode Depth
again without unfiltering the data.
This option will make all selected data valid again, except the manual
rejected data. Draw a polygon around the data that have to be valid
again and all the data becomes valid. The data can be recognized by
its own filter color (Ignore Filters).
Clear Ignore Filters ( )
The ignore filters setting will be undone. Select the data by drawing a
polygon, which have to be bigger then the ignore filters area, and all
the selected data gets their own filter setting back.
Create Sonar Target ( )
When there are sonar targets Draw a box around an area in the sonar view that has to be saved as a
available, they will be sonar target.
displayed in the editor. To add The symbol for the sonar target can be defined in the Active Sonar
sonar targets a grid model has Targets Layer, which will be created when the first sonar target is
to be added to the view. selected.
When the sonar Target symbol is drawn in the editor, a context menu
becomes available for that sonar target. With a right mouse click on or
in the symbol gives some extra options. See ‘Sonar Targets Options in
Plan Views’ on page 355.
See the Sonar Targets view on page 491 for more information.
Delete All Sonar Targets
All the sonar targets from the active sonar targets file will be deleted in
the editor, in other views and from the active sonar targets file. Along
with the sonar targets the corresponding GeoTIFF files of the images
of the sonar targets will be deleted.
Layer Control ( )
Opens the Layers window where layers can be added, edited or
removed. Only the used layers will be shown in the Layers window.
Properties ( )
Opens the Properties window of the view where next to for instance
the color table and the scale factor several option from the toolbar
and/or context menu are accessible.
Next to the view properties, all the attributes of the selected layers of
the Layer Control are available.
The ping as displayed in the Ping view is only motion compensated and
not geo-referenced.
The ping that is displayed in the Ping view will be highlighted in the
Multibeam Area Editing – Standard view.
With the option 2D Side Front ( ) the standard 2D Ping view (Front
view) as shown above can be changed to a 2D Side view.
When more pings are selected in the Ping view, then also more pings will
be highlighted in the Multibeam Area Editing – Standard view (see below).
Figure 16-88 Multibeam Area Editing – Standard view with 250 highlighted
pings which are displayed in the Ping view
The editing in the Ping view is similar as the editing in the other 3D views
(see page 416).
again without unfiltering the data.
This option will make all selected data valid again, except the manual
rejected data. Draw a polygon around the data that have to be valid
again and all the data becomes valid. The data can be recognized by
its own filter color (Ignore Filters).
Clear Ignore Filters ( )
The ignore filters setting will be undone. Select the data by drawing a
polygon, which have to be bigger than the ignore filters area, and all
the selected data gets their own filter setting back.
Export Multibeam Points To ASCII…
The XYZ of the multibeam data as displayed in the view will be
exported to a file with extension ASC .
Layer Control ( )
Opens the Layers window where layers can be added, edited or
removed. Only the used layers will be shown in the Layers window.
Properties ( )
Opens the Properties window of the view where next to for instance
the color table and the scale factor several option from the toolbar
and/or context menu are accessible.
Next to the view properties, all the attributes of the selected layers of
the Layer Control are available.
File Color
The tracks are colored with the color as is given in the databar.
Show Color Table ( )
Toggles the display of the color table on the right side in the view
on/on/off.
Grid Model Color Mode ( )
In the view different Grid model color modes can be displayed:
if available the Z Average, Hit Count, Z Standard Deviation, Z
Minimum (Deepest), Z Maximum (Highest) and Time.
Coverage Settings ( )
The settings of the grid model in the editor (see page 361).
Layer Control ( )
Overview of all used background and foreground layers. Also new
layers can be added to the list.
Properties ( )
The properties of the editor.
A better method to fill the gaps in the position is by using the edit option
Fill Gap from the context menu in the Position Editor as is explained on
page 416.
The editing in the Profile view is similar as the editing in the other 3D
views (see page 416).
The data in the Profile view will not be updated when in the Multibeam
Area Editing – Standard view a new grid model or CUBE model is added.
When the Profile view is closed in the Editing it will not be available
anymore as a view in the Displays window (see page 398).
again without unfiltering the data.
This option will make all selected data valid again, except the manual
rejected data. Draw a polygon around the data that have to be valid
again and all the data becomes valid. The data can be recognized by
its own filter color (Ignore Filters).
Clear Ignore Filters ( )
The ignore filters setting will be undone. Select the data by drawing a
polygon, which have to be bigger than the ignore filters area, and all
the selected data gets their own filter setting back.
Export Multibeam Points To ASCII…
The XYZ of the multibeam data as displayed in the view will be
exported to a file with extension ASC.
16.15 Sonar
At the moment the Sonar is not an editor it is only a viewer for side scan
sonar data or for snippets data. For both types of data, a separate viewer
is available; the Sonar – Sidescan view and the Sonar – Snippets view.
In both viewers, the data can be moved to the left or right with the left or
right arrow key on the keyboard. Next to the zoom buttons ( and )
the keys ‘+’ and ‘-’ on the numerics keyboard can be used to zoom in and
out in the view.
decide when the recache of the side scan sonar or snippets data is
started. Click on to start the recache.
The + and – key of the Zoom In, Zoom Out ( , )
numerics keyboard can Zoom in and out in the view.
also be used for the Zoom
In and Zoom Out. Brightness ( , )
Increase (lighter) and Decrease (darker) the Threshold.
Contrast ( , )
Increase and Decrease the Gain.
Ping Selection ( )
Select one of the four pings or all the pings to be displayed in the view.
Lines/Dots ( )
Toggles between Dot view (Out) and Line view (In).
Speed Correction ( )
Toggles between Speed Correction Off (Out) and On (In) (see page
380).
Invert Colors ( )
Toggles between a black background (Out) and a white background
(In).
Click on to activate the Slant Range Correction ( )
changes caused by the Toggles between Slant Range Correction Off (Out) and On (In) (see
slant range correction page 381).
on/off.
Save Snapshot ( )
Save the display as a JPG or BMP file.
Create Sonar Target ( )
Draw a box around an area in the sonar view that has to be saved as a
sonar target.
The symbol for the sonar target can be defined in the Active Sonar
Targets Layer which will be created when the first sonar target is
selected.
When the sonar Target symbol is drawn in the view a context menu
becomes available for that sonar target. With a right mouse click on or
in the symbol gives some extra options. See ‘Sonar Targets Options in
Sonar Views’ on page 381.
See the Sonar Targets view below for more information.
Delete All Sonar Targets
All the sonar targets from the active sonar targets file will be deleted in
the views and from the active sonar targets file. Along with the sonar
targets the corresponding GeoTIFF files of the images of the sonar
targets will be deleted.
Layer Control ( )
Opens the Layers window where layers can be added, edited or
removed. At the moment only the Active Sonar Targets Layer is
available in the Layers window.
Properties ( )
The above-mentioned settings in the view.
The color palette can be set on rust or gray.
Figure 16-94 Three Sonar Targets views with sonar targets created in three
different views
files and all the corresponding GeoTIFF files. Don’t forget to copy the
GeoTIFF files when a copy is made of the sonar targets. When no
GeoTIFF files are available no picture is available anymore.
Measure ( )
To measure a distance and a bearing in the plan view. On the first use
the measure starts at the vessel’s tracking point. With a mouse click
the start of the measurement can be at any location in the view. The
measure window shows start and end coordinates as well as distance
and bearing between the two locations.
The Tide Station – Viewer shows only the tide data that is used for the
data in the selected file set. If there is no tide data applied to the data in
the Editing this viewer will be empty.
It is possible to modify the tide data in the viewer, but the tide data will not
be treated as PDS2000 log data like all the other data in the Editing. Any
modification made in the viewer will modify the tide values files in the
Explorer (see page 223), but not the data in the other editors. If tide data
is modified in the viewer or in the editor, use the option Tools > Apply Tide
to update the other data in the Editing.
Various sensor values are relevant against a time scale. For example,
data from a VRU shown in time shows where the VRU went wrong. When
at the same time a Position Editing – Standard view is viewed, it can be
shown where the wrong VRU data is located. This may help analyzing
data from the viewed sensors.
All data is logged in a time sequence. However, it is not always useful to
show logged data in time; for example, a shallow depth recording when
viewed in time indicates there was a shallow depth at some time during
the survey but not where the shoal is located.
In this view, the echo sounder channel data with its graphical trace
information can be displayed.
When no color table is available for the graphical trace a default color
table will be generated when the channel data is loaded in the view. In the
Channel Properties in the context menu of the view a different color table
can be selected if necessary.
With the Add Echogram ( ) option only the echo sounder channels can
be selected and added to the Time-Based Editing.
The echo sounder data can be edited with a special option in the toolbar,
called digitizing ( ). See page 498 for an explanation of the digitizing.
Zoom Window ( )
With dragging a window in the active channel a part of the channel can
be zoomed in.
Zoom Extents ( )
Show all the data for all the channels.
Selector ( )
Toggles the ‘Selector’ on/off.
Channel Partition ( )
If more than one line with data is displayed it is possible to display all
the data in one view (Overlayed) or each data line in a separate view
(Stacked).
Set Y Scale
For the view in the editor, the y-axis can be defined. Set in the Set Y
Scale dialog the high and low values for the y-axis.
17.1 Introduction
Create Model can be used to make a grid model or a TIN model from
different types of data files.
The Create Model can be started with Processing > Create Model from
the menu bar or with from the toolbar of the Control Center.
After reading the data files with an optional preview function the data can
be shown in a view. All the data or data inside a clipping polygon can be
converted into a grid model or a TIN model.
Additional parameters
If necessary a scale factor for the Z-value can be entered.
Coordinate type
Select the coordinate type used in the ASCII file.
Coordinate transformation
If the coordinate type is ‘Geographic’ a coordinate datum
transformation has to be selected. Only the datum transformation
which are compatible with the project coordinate system will be
displayed. This means that the local ellipsoid should be the same as in
the project coordinate system.
Figure 17-6 Grid model data type selection for the Grid Model
Select one of the available data types in the selected Grid Model for the
import of the grid model data.
Only from the first valid Select the sensor computation of the sensor that has to be imported.
logfile in the file set the Multiple selections can be made with the Ctrl-key.
computations will be
extracted and displayed as If the multibeam xyz computation of a RESON SeaBat 7K is selected two
option!! extra options will appears at the bottom of the data selection. From the
bathymetry data the Bathymetric data or the Backscatter data can be
used to create the model.
17.2.3 Preview
When all the data files are selected and the additional information for
each data file is entered the wizard can be closed by clicking on .
All the selected data will be loaded into the computer memory.
When Show preview is checked the loaded data will be shown in the
view. A coarse grid model is used as default to show the data.
18.1 Introduction
A grid model is a digital representation of the earth’s surface. These kinds
of models are also called DTM’s or Digital Terrain Models. These models
are usually created with survey data; however other 3D data can also be
used. A model consists of a number of cells where each cell can contain
one or more data types. The cells of a grid model are always a square
with the sides parallel to the projection grid.
PDS2000 uses grid models on various locations. In the Acquisition a
covered area is shown through a grid model. Off-line a number of
operations with a grid model are possible. Some of these possibilities are
listed below.
In the Acquisition and Presentation, coverage charts for various
sensors.
Quality control for sensor values.
Interpolation of measured values over non reachable areas.
Volume computations.
Expand or update existing models with new survey data.
Import and export of ASCII files.
Correcting measurements.
Visualization of measurements, in colors.
Comparing grid models and creating differential models.
Extracting profiles.
In the grid model editor next to the standard grid model a geoid model
grid model can be generated. This geoid model can be used in the
coordinate system to correct the satellite ellipsoid heights to the correct
local heights (see page 79). Two different geoid model grid models can
be generated, one with the satellite ellipsoid coordinates and one with the
grid projection coordinates. See the Import page on page 524 to create a
geoid model grid model.
Maximum on the right location and not in the center of the cell. When
contours are generated with the Z Minimum or Z Maximum also the right
location is used and not the center of the cell. These locations are not
visible for the user and are only used internally in the grid model.
Grid models from PDS2000 version 3.6.0.6 or earlier can still be used but
the Z Minimum and Z Maximum will have no offset.
The new grid models can be used in earlier versions but the offset for the
Z Minimum and Z maximum will not work.
The grid model editor can be started with Processing > Grid Model Editor
from the menu bar or with from the toolbar of the Control Center.
With the grid model editor grid models can be created and edited. A
number of actions are available for model computations and editing.
Multiple models can be open in the editor simultaneously, but only one
model is active and editable. The models are managed in a Displays
window which can be opened with View > Displays. Close a model by
closing the window or with File > Close. It will only remove it from the
display, but the model is still available in the Displays window with its own
too big. Each time when with from the toolbar in the Control Center
the grid model editor is opened all the grid models in the Displays window
will be opened. This can result in the fact that the grid model editor cannot
When the grid model editor
is opened from the
open or opens very slow. So remove the not used grid models from the
Explorer only the selected list in the Displays window. Better is to use the combo box in the top left
grid model will be opened. of the grid model editor to open one of the other available grid models.
With (2D) and (3D) in the toolbar of the grid model editor the view
of the active model can be set in 2D or 3D. In the 3D View the standard
3D view navigation can be used (see page 50).
There are different ways to create a grid model; during on-line logging,
with the option ‘Create Model’ (see chapter ‘Create Model’ on page 499
for more information) or with the create or import option in the grid model
editor.
Click on the yellow ball and move it around in the circle. How further
away from the center how less intense the light will be. The location of
the yellow ball in the circle gives the location of the light source.
Pan ( )
Toggles the pan option on/off. When pan is active, keep the left mouse
button in and move the mouse to pan through the data.
Measure ( )
Measure a distance between a selected point and the cursor.
18.3 Actions
The different actions on the grid model data are grouped and located
under one of the tabs in the left pane.
Create (see below)
Info (see page 514)
Edit (see page 516)
Filter (see page 517)
Update (see page 519)
Export (see page 520)
Import (see page 523)
Operations (see page 525)
Interpolate (see page 534)
By selecting an existing grid model in the combo box above the Create
tab the other tabs become available again.
Grid model
It shows the cell size and the statistical information of the grid model.
Cell size
The cell size of the grid model.
Used cells
Total number of cells in use.
In the Edit page, options are available to delete and interpolate one or
more cells in the grid model.
In Edit mode in the 3D mode for editing the left mouse button has to be
used and for moving around in the view the mouse wheel can be used.
See also the navigation in 3D views on page 50.
None
The Edit mode is switched off.
Delete
The selected cells of the grid model will be deleted.
There are three methods to delete one or more cells:
4. Delete one point by clicking on the cell with the cursor in
combination with the Ctrl key.
5. Delete more cells by placing the cursor on the right location. Keep
the left mouse button pressed in combination with the Ctrl key and
move the cursor over the grid model data. It looks like erasing the
data.
6. A different method to delete more cells is by drawing a polygon
around the points that have to be deleted. All the data that is
present inside the polygon will be deleted. The polygon can be a
polygon with line segments or it can be a free drawn polygon
(lasso).
Interpolate circular
Interpolate the gaps in the grid model with the circular interpolation. In
this interpolation all the Z data types (the Z Average, the Z Maximum
and Z Minimum, if available in the grid model) will be interpolated.
Draw with the mouse a lasso / clipping polygon and the gaps in the
lasso / polygon will be interpolated immediately.
Max gap
The maximum gap in the grid model for which the interpolation is
valid. If the gap is bigger than the max. gap then no interpolation
will be done.
Figure 18-7 Spikes previews in Red on Green (left) and in User color
Filter Options
Evaluation area size
Select an evaluation area size; for each type of area a different size
for the despiking is needed. For each area a mean is calculated
and with the threshold a spike can be detected in the area.
Threshold
The threshold is a kind of standard deviation for each area.
For an irregular area a small threshold (f.i.0.5) will give more spikes
than a threshold of 5. How bigger the threshold the more
irregularity is accepted as no spike.
Selection area
The despiking can be done for the complete grid model with the
options Entire Model’. The spikes are found after on
is clicked.
With Select area select an area of the grid model by drawing a
lasso around the area with spikes. The spikes are found when the
lasso is drawn.
or
The ‘Find Spikes’ button is only active when as selection area the
entire model is selected.
Click on the button to find the spikes in the grid model.
The ‘Find & Remove Spikes’ button is only available when the option
When Show Preview is checked the spikes become visible in the view.
Click on the button to remove the spikes. The spikes will be replaced
by interpolated data from the cells around the spike(s).
Figure 18-8 Data type and clipping polygon selection for the interpolation
Clipping polygon
A clipping polygon is not required. If a clipping polygon is not available
it should be made first, this can be done with the option Draw Polygon
in the context menu.
The data in the grid model will be replaced with the data from the 3D
model. This update is only in the cells where data from the 3D model is
available. If a clipping polygon is selected the update will take place only
inside the polygon.
Click on to start the update of the grid model.
Data type
Select one of the available data types for the export.
Clipping polygon
A clipping polygon is not required. If a clipping polygon is not available
it should be made first, this can be done with the option Draw Polygon
in the context menu.
For a bottom classification This function exports the grid model data to an ASCII text file. Each cell
model next to the phi also with the selected data type will give an X, Y and Z, where X and Y are the
phi+text can be exported. center of the cell and Z the selected data type. A comma will be used as
The text is the label in the separator. If a clipping polygon is selected the export is only from data
color table.
inside the polygon.
Check the option Export as depth when the Z value(s) have to be treated
as depths instead of heights. For the Z Average, Z Minimum and Z
Maximum the values will be multiplied with ‘-1’.
Click on to start the export of the grid model data.
This function exports the grid model data to an ESRI text file. The ESRI
format needs a rectangle parallel to the X and Y grid. If no clipping
polygon is selected PDS2000 will generate a rectangle around the data. If
a clipping polygon is selected PDS2000 will generate a rectangle around
the polygon.
Each cell in the rectangle will give a Z-value, where for the filled cells the
selected data type will be used and for the empty cells a ‘No data value’
can be specified. The cells outside a selected clipping polygon will be
treated as empty cells. The number of decimals for every Z-value can be
specified.
Click on to start the export of the grid model data.
This function exports the grid model data to a KML or a KMZ file. Both
these files can be opened in an OpenGIS system, i.e Google Earth (see
also page 221 in the Project DataBase in the Explorer).
The KML file contains the X and Y which are converted to WGS’84
coordinates. The conversion is from grid coordinates to the WGS’84
coordinates and is done according the project coordinate system. The Z
value is the value of the selected data type. The KML file gives a point
cloud with Z values.
The KMZ file contains a compressed GeoTIFF file of the grid model.
If a clipping polygon is selected the export is only from the data inside the
polygon.
Click on to export the X,Y and Z to a KML file and click on
to export the image of the grid model to a KMZ file.
The data from a standard grid model, a side scan model or a snippets
model can be exported to a compressed GeoTIFF file. The GeoTIFF file
is compressed with the LZW compression. The sun illumination setting
will be used to generate the GeoTIFF.
This file can be draped over a grid model in the 3D views of PDS2000 by
adding a 3D Draping Layer to that view.
Check the option View in 3D, select a grid model that will be used for the
draping and after the grid model is exported the 3D grid model editor will
open with the selected grid model and the GeoTIFF file draped over it.
Select one of the available data types from the grid model. This data type
will be displayed in the GeoTIFF file.
Click on to start the export of the grid model data.
This method regenerates an existing color table where the maximum and
minimum values are taken from the grid model.
Apply a correction to a grid model means that the existing data types (‘Z
Average’, ‘Z Minimum’ and ‘Z Maximum’) are corrected following the
equation:
New value data type = (Old value data type) x (Factor) + (Offset)
Change the depths to heights or vice versa by setting the factor to ‘-1’ and
the offset to ‘0’.
Click on to apply the Z correction to the grid model.
For all the cells inside the clipping polygon the values of the selected
data type will be deleted.
By selecting a grid model filter all data types in a cell can be made empty.
Display
Check this option to see which grid model cells will be made empty
with the selected grid model filter.
With a new grid model filter can be made. The grid model filter
editor will be opened (see below). With the selected grid model
filter can be modified in the grid model filter editor.
In the grid model filter editor two criteria can be defined for the grid
model filter. Both criteria must be valid to clear a cell. Select None
for a criterion to make it ‘not used’.
Clipping polygon
Select a clipping polygon, and set the condition to either Inside
or Outside.
The criterion that a grid cell is inside or outside the clipping
polygon is when the center point of the grid cell is inside or
outside.
Data type
Select the data type, a condition operand and a comparing
value. The operand can be > (bigger) or <= (smaller or equal).
After the filter is defined check the option Display to see which cells
meets the criteria of the filter. In the 2D view a red diagonal line is
Click on to make the cells empty which match with the criteria in
the filter. When the user confirm the process, it is not reversible!!
This option is to create a grid model with a difference cell size from the
active grid model by resampling the data in the grid model.
The resampling will be done for all the data types available in the active
grid model. Select a clipping polygon if only from a part of the grid model
a new grid model with a different cell size has to be created.
Click on , select an existing grid model or give a new name for
the resampled grid model and the model will be created.
Figure 18-25 Create Report dialog (left for the PDF report and right for the CSV
report)
Report
Enter a name that will be used in the header of the report.
Profiles will be extracted from the grid model over the selected runlines.
Data type
Select the data type of the grid model that will be used for the for the
profiles.
Keep Ctrl pressed to select Runlines
multiple lines or use Shift Select the runline file for the profile calculations. Select the lines of the
to select a block of lines. runline over which the profiles have to be extracted.
Use section
Check this option when a profile have to be extracted over a part of
the runline. Enter the start and end point on the runline between
where the profile has to be extracted.
Multiple displays
Each selected runline gets its own profile view with in the title bar the
name of the runline.
Single display
All the profiles of the selected runlines appear in one profile view, each
one with a different color.
PDS2000 Log Data file
For each runline a PDS2000 log data file will be create in the log data
directory.
ASCII file
All the profiles of the selected runlines are saved in one text file. For
each profile the first line has the name of the runline followed by XYZ
data and the distance along the runline.
At the bottom some extra information can be added to the file; the
Mean, the Minimum, the Maximum and/or Standard deviation of the Z-
value.
Another way to extract a profile from a grid model is with the option Draw
Profile in the context menu of the 2D view or the toolbar option Create
Detail View > Create Profile View ( ) in the 3D view.
Figure 18-29 Data type and clipping polygon selection for the interpolation
Data type
Select one of the available data types for the interpolation.
Clipping polygon
A clipping polygon is not required. If a clipping polygon is not available
it should be made first, this can be done with the option Draw Polygon
in the context menu.
The circular interpolation is usually used for small gaps in the data. These
small gaps can be caused for example by the outer beams of a multibeam
survey.
Max. gap
This is the maximum distance over where an interpolation is valid.
The interpolation routine search for every empty cell in the clipping
polygon area or in the complete grid model. It will check if original data is
available within a ‘Max gap’ distance, and if so, it fills the empty cell with a
weighted mean of the original data.
Depending on the size of the interpolation area and the power of the
computer, this method can take considerable time. The best way to use
this option is when the gaps are small and there are lots of filled cells, like
multibeam data.
Click on to start the circular interpolation.
The triangular interpolation is usually used for medium gaps in the data.
Max.gap
This is the maximum distance over where an interpolation is valid.
The interpolation routine takes three steps:
1. Find the extents of the data.
2. Create a TIN model.
3. Interpolate in the triangles of the TIN model.
Click on to start the triangular interpolation.
The directional interpolation is usually used for big gaps in the data.
These big gaps can be caused for example by sailing along runlines with
a single beam echo sounder.
Max.gap
This is the maximum distance over where an interpolation is valid.
Route
A route has to be selected or made. A quick way to make a route is
with the option Draw Route in the context menu of the 2D view.
Interpolation takes place in the direction of the route. Bends in the
route are allowed.
Perpendicular
Check this option to set the interpolation direction to across the
route.
Click on to start the directional interpolation.
19.1 General
With the TIN model viewer TIN models can be created and visualized.
The viewer allows data to be presented in a 3D view. This 3D view is
intended to be only for visualization of the data. There are no functions to
modify the data in the TIN model viewer.
The TIN model viewer can be started with Processing > TIN Model Viewer
from the menu bar of the Control Center.
19.2.1 File
The menu File has the functions to create, open, save, export and print
views and show the properties of the view. Most of these functions are
standard functions, except the export and the properties.
File > New
Under this option a number of sources are available to create a new
TIN model or to create a new color table.
Blank Model
A blank model will be generated, which can be used in combination
with the drag & drop function to add data.
From ASCII File
All the existing ASCII files in the project folder are available. From
this ASCII file a TIN model can be created.
From XYZ Point File
All the existing XYZ files in the project folder are available. These
XYZ files are the ‘Cleaned XYZ Log Data’ files, which is one of the
available logging formats. See page 119 for more information about
cleaned XYZ log data.
Color Table
Create a new color table with the standard PDS2000 color table
generator (see page 226).
File > Export to ASCII File
The current file will be saved in ASCII format, with the extension ASC.
The format is X, Y, Z.
File > Properties
The properties of the current TIN model will be shown.
19.2.2 Edit
The menu Edit has only the function Empty Cache. In case the operation
seems to become slow or the computer is running low in memory, the
data cache can be deleted. No data will be lost, all the data can be
reloaded from the database.
19.2.3 Tools
The Tools menu has the following functions:
When the feature angle is greater than the maximum feature angle,
the shared edge (the thick red line) is called a feature edge. This
feature edge is used to classify the vertex.
Maximum error
A simple vertex is a data point that is completely surrounded by
triangles.
Simple Vertex
The 3D distance is the distance from the interior edge vertex to the 3D
line formed by the endpoints of the two feature edges. The interior
edge vertex is removed if the 3D distance is smaller than the
maximum error.
If the option Remove boundary points is checked then also the
boundary vertex go through the decimation. A boundary vertex is a
vertex that is not completely surrounded by triangles.
3D Distance
Boundary Vertex
The start and end depth and a contour interval have to be set to start the
generation of the contours.
On the next page in the wizard the main project has to be selected. If
other PDS2000 projects are available with the same geodetic settings, the
data can be selected from those projects as well. Data from projects with
different geodetic settings cannot be combined.
Click on and PDS2000 will create the plot project and close the
wizard.
The project tree contains everything that is part of the project. Next to the
project tree is the overview window, which consists of two sections. The
left section shows the overview tree, while the overview plot is shown in
the right section. The overview plot also has a toolbar.
Figure 20-3 Context menu of the overview tree and overview plot
Any data that is added will show up in the tree and in the plot of the
overview window.
The new plan view is added to the project tree and displayed in the
overview plot. It is usually a good idea to give the plan view a more
descriptive name than the default one. The name can be changed in the
properties of the context menu of the plan view.
Cancel any visual Move a plan view by selecting it with the mouse, and then dragging it
operation by pressing the around the plot. Change the size of the plan view by selecting one of the
‘Esc’ key on the keyboard. handles and dragging it with the mouse.
Click on from the toolbar or select View > Rotate from the menu bar to
rotate a plan view. The handles of the selected plan view will change. By
dragging one of the handles with the mouse the plan view can be rotated
around its center point. Click on or select View > Rotate again to
finish the rotation of the plan view.
Figure 20-10 Context menu of the plot tree and the plot view
From the context menu select Place Panel and then select the type of
panel to add. For example select Plan to place a plan panel. See on page
557 for an explanation of the available panels.
The cursor will change to a cross and a rectangle can be drawn in the plot
where the panel should come. After releasing the mouse button the new
panel will be added to the plot. A window will appear with the panel’s
properties.
The panels are displayed in the plot and in the plot tree. The properties of
a panel can be opened with a double click on the panel in the plot, in the
plot tree or through the context menu of the panel.
Select the panel with the mouse and by dragging the mouse the panel
Hold the Shift key down to
can be moved around in the plot. Resize a panel by first selecting it, and
disable ‘snap to grid’.
then grabbing one of the handles.
Layers that are not visible are indicated in the plot tree by a dark light
bulb. Panels that are locked against accidental movement are indicated
with a small pad lock.
When the Toggle Auto Regenerate ( ) is on, the plot will automatically
be regenerated if necessary. When the Toggle Auto Regenerate is off and
the plot needs a regeneration the button Regenerate ( ) becomes
active and the text ‘Plot needs to be regenerated!’ will appear above the
plot.
Figure 20-15 Overwrite suppression in action; behind the easting text are no
depth values plotted
When overwrite suppression is enabled for just one layer then no text of
that layer will overwrite other text of the layer. When enabled for several
layers, the text of those layers will not overwrite each other as well.
20.2.4 Templates
Plot templates are the same as regular plots. They are only separated
from normal plots by their file name extension, which is ‘.[tpl].plt’ instead
of just ‘.plt’. The project tree displays the templates separate.
Templates can be used when creating a new plot. Check the option Copy
existing plot, and then choose the desired plot template from the file
dialog. To show only template files in the file dialog, set the ‘Files of type’
field to ‘Template Files’.
20.2.5 Keywords
Keywords are special tokens that get replaced by user-defined text. A
keyword is a piece of text between ‘%’ characters that can be present in
text boxes or in the text of DXF files.
Select Edit > Project Options from the menu bar to add or modify the 'user
text’ for the keywords. The keywords set in the ‘Project Options’ are
project wide keywords. Several keywords are already added to the
keywords list and cannot be modified. These keywords are: project
number, project name, coordinate system, current time, current date and
plot project.
Plot specific keywords can be added or modified in the ‘Plot Properties’ of
the plot. By default the plot name is added and cannot be modified.
The Mapping page of the plan panel properties requires a plan view.
When the option Auto fit to log data is checked a plan view will be
generated that fits the log data that is added as layer.
If plan views are generated in the overview (see page 549) then instead
off the auto fit option an existing plan view can be selected. The center
point and rotation of the plan view will be used directly, and are displayed
on the page.
Figure 20-19 North Arrow page of the north arrow panel properties
With the North Arrow page of the properties it is possible to select the
type of north arrow. The direction of the arrow is taken from the selected
plan panel. When a north arrow is attached to the panel, its position will
be relative to the bottom left hand corner of the plan panel.
It is possible to design your own north arrow with a CAD application.
Export the arrow to a DXF file, and place it in the ‘NorthArrows’ folder of
the ‘General’ folder of the PDS2000 installation (see page 16).
Figure 20-21 Horizontal and Vertical pages of the profile panel properties
The profile panel properties have separate mapping pages for the
horizontal and vertical axis. The horizontal and vertical options that are
available depend on the selection made in the Mode option.
Scale to Fit
Everything is calculated automatically to fit the extents of the profile.
Fixed Start and End Value
Enter a start and end value. The scale is calculated automatically.
Fixed Scale
Enter a scale and a start value. The end value is calculated
automatically.
Projected
This option is only available for horizontal mapping. The horizontal axis
will be mapped to a specified plan panel.
On the Horizontal page the option Coordinate origin defines where zero
on the X-axis starts. Note that ‘Route intersection’ only works with
runlines of the type ‘Route Crosslines’.
The profile volume panel displays multiple profile boxes in a single panel.
A selection of runlines is used for the profiles. Each line is placed into a
separate profile box.
The mapping of the profile boxes is controlled by the Distance Scale and
Depth Scale pages of the profile volume panel properties. The pages
work slightly different than the Horizontal and Vertical pages in the profile
panel (see above).
There are four parameters to set for the Distance Scale: start value, end
In all the profile boxes the value, box width and scale and four for the Depth Scale: minimum,
same vertical axis maximum, box height and scale. Select in the option Mode which of the
definition will be used. four parameters is automatically calculated, the other three can be
changed by the user.
In the profile volume properties are 3 different pages available to define
the design model and the design line with its colors and select the survey
data.
Figure 20-26 Design line and colors page of the profile volume properties
In this page the design line with its under- and overdredge line can be
defined. For the 4 areas the colors can be selected, by default the colors
are identical with the colors in the End Area Volumes.
Figure 20-27 Survey data and colors page of the profile volume properties
In this page as data a grid model or a file set with log data files can be
selected.
The profile series panel displays multiple profile boxes in a single panel.
A selection of runlines is used for the profiles. Each line is placed into a
separate profile box.
Figure 20-29 Distance Scale and Depth Scale pages of the profile series panel
properties
The mapping of the profile boxes is controlled by the Distance Scale and
Depth Scale pages of the profile series panel properties. The pages work
slightly different than the Horizontal and Vertical pages in the profile panel
(see above).
There are four parameters to set for the Distance Scale: start value, end
In all the profile boxes the value, box width and scale and four for the Depth Scale: minimum,
same vertical axis maximum, box height and scale. Select in the option Mode which of the
definition will be used. four parameters is automatically calculated, the other three can be
changed by the user.
The profile cross series panel displays multiple cross profile boxes in a
single panel.
A selection of runlines is used for the profiles. Each line is put into a
separate cross profile box.
Figure 20-31 Distance Scale and Depth Scale pages of the profile cross series
panel properties
The mapping of the profile boxes is controlled by the Distance Scale and
Depth Scale pages of the profile cross series panel properties. The pages
work the same as the Distance Scale and Depth Scale pages in the
profile series panel (see above).
Only here are three parameters to set for the Distance Scale: start value,
end value and scale. The box width in the Distance Scale page is defined
In all the cross profile by the height of the panel as defined in the Position page. Four
boxes the same vertical parameters are to set for the Depth scale: minimum, maximum, box
axis definition will be used. height and scale. Select in the option Mode which of the three or four
parameters is automatically calculated, the other two or three can be
changed by the user.
The profile info panel displays the information of a profile panel, profile
series panel or a profile cross series panel.
The information consists of the X and Y scaling mode used, and a legend
of all profile layers used in the panel. Each layer is listed with its line color
and data file name.
Figure 20-33 Profile Info page of the profile info panel properties
Select in the Profile Info page for which profile panel the profile info panel
has to be generated.
Figure 20-34 Sample of a text block panel with two text boxes
A Text Block is the parent panel for one or more Text Boxes. It is used to
group several Text Boxes together so that they can be moved
simultaneously.
To add some text to the plot, first place a Text Block. Inside this panel,
place one or more Text Boxes that will contain the actual text.
In the Text Block panel with the context menu item Place Text Box a Text
Box is placed in the Text Block. The Text Box can only be placed
somewhere inside the parent Text Block.
In the Text page of the text box properties replace the default text ‘Enter
label’ with the desired text.
The position of a text box is always relative to the lower left hand corner
of its parent text block.
Select in the DXF page the DXF file that has to be plotted. Use the
offsets, rotation and/or scale to place the data on the right location in the
panel.
The color mapping panel displays the color table of a plan panel. When
attached, the panel will automatically be placed next to the plan panel and
receive the same height. The order of the table can be reversed.
Figure 20-38 Color Table page of the color mapping panel properties
Select in the Image page the image file. The plot support several image
file formats, like BMP, JPG, TIFF, etc.
Figure 20-40 Sample of a key map panel with the current plot highlighted
The key map is a panel that can display an overview of the defined plan
view rectangles of the current plot project. A plan panel of the current plot
is highlighted in the key map.
A key map panel uses the same mapping method as a plan panel. Define
an extra plan view to cover all other plan views just for the mapping of the
key map.
After creating the panel, the first thing to do is to add the Plan Views
layer. This layer will display the available plan views. Add other layers if
needed.
The scale bar is a panel that displays the scale of a plan panel in the form
of a bar.
Figure 20-42 Scale Bar page of the scale bar panel properties
Select in the Scale Bar page the type of the scale bar and which plan
panel will be used as reference.
Profile Volume
Profile Series
Profile Cross
Key Map
Profile
Series
Plan
The clipping polygon can be plotted in the plan panel and in the key map
panel.
When the option Use only dredge status is checked, then select in the
combo box which dredge status has to be plotted.
When all the dredge statuses are plotted a dredge state color table can
be selected to show each dredge status in a different color. Check the
option Use color table to make this option active.
The dredge status information can only be plotted in the plan panel.
The text size of the text from the DXF file will varies with the scale as
selected in Plot. To disable this feature select in the Text Size page the
option Use fixed text size and enter a scale. The text is then plotted with
the entered scale.
In the Line Style page the line width can be defined. The color to plot the
data can be selected; use the colors as in the DXF file or select a user
defined color.
The DXF file can be plotted in the plan panel and in the key map panel.
The GLW grid can be plotted in the profile panel, in the profile series
panel and in the profile cross series panel.
In the Cells page is defined how the grid model data is presented in the
plot.
Use limits
If checked, only the grid model cells with a depth between the
minimum and maximum depth will be plotted.
If not checked, all the cells will be plotted.
Show cells
If checked, then the cells will be plotted with the colors of the selected
color table of the plan panel (see page 558), the key map panel has no
color table. The option Points will plot a colored point in the center of
each cell and the option Solid will fill the cell with one color.
Use sun illumination
If checked, the sun illumination settings will be used to change the look
of the grid model. This is only working when for Show Cells the option
Solid is selected.
Show labels
If checked, the depth values will be plotted on top of the grid model
with the label spacing as specified. The label spacing is related to the
selected scale in the Mapping page of the plan panel or key map
panel.
In the Depth Biasing page the biasing can be set. With No biasing the
label will be plotted according the label spacing as specified in the Cells
page.
With Shoal biasing a virtual grid with the label spacing as grid size is
generated. For each virtual grid cell the shallowest value will be plotted,
starting with the shallowest value of all virtual grid cells.
With Valley biasing a virtual grid with the label spacing as grid size is
generated. For each virtual grid cell the deepest value will be plotted,
starting with the deepest value of all virtual grid cells.
The grid model data can be plotted in the plan panel and in the key map
panel.
In the Contour page defines the contours and the location and orientation
of the contour labels.
Suppress contours shorter
Defines that plot contour lines shorter than the specified value will not
be plotted.
Contour label spacing
Defines the spacing between two labels on the same contour line. The
label spacing is related to the selected scale in the Mapping page of
the plan panel or key map panel.
Label orientation
Defines how the labels in the contours will be plotted. The option Use
Optimum Text Angle uses as much as possible the orientation of the
plan panel or key map panel to plot the labels. The options Slope
Upwards and Slope Downwards will plot the labels in direction of the
slope, upwards up or downwards up.
Smoothing window
This option can be used to smooth the generated contours, from no
smoothing to a maximum smoothing with 7 steps in between.
The labels of the contours are plotted only when in the contour
definition file for the each contour the option Show labels is
checked.
Figure 20-52 Contour properties of a contour in the contour definition file with
the option Show labels checked
Figure 20-53 Design Model page of the grid model difference properties
In the Design Model page 2 different model types can be selected; Grid
Models and 3D Models.
The Grid Model and Data Type page, the Cells page and the Depth
Biasing page are identical with the pages for the grid model layer (see
page 575).
The Contouring page and Contour Levels page are identical with the
pages for the grid model contour layer (see above).
The grid model difference data can be plotted in the plan panel and in the
key map panel.
In the Options page the settings for the profile can be defined.
Smoothing
This option can be used to smooth the generated profile, from no
smoothing to a maximum smoothing with 7 steps in between.
Average profile
The profile is generated over the active runline. Check the option Use
adjacent lines to take also profiles over the adjacent runlines on each
side. From these profiles an average is calculated and that average
profile is plotted. Enter how much adjacent lines have to be used to
calculate an average profile.
Step size
When the option User defined is not checked the points of the profile
are calculated from the centers of the grid cells that crosses the
runline.
When the option is checked the points of the profile are generated for
each step on the line. Each point is a weighted mean of the four
nearby grid cells. Enter the distance (step size) between two points of
the profile.
The grid model profile can be plotted in the profile panel, in the profile
series panel and in the profile cross series panel.
Figure 20-55 Options page of the grid model profile statistics properties
In the Options page the settings for the profile can be defined.
Smoothing
This option can be used to smooth the generated profile, from no
smoothing to a maximum smoothing with 7 steps in between.
Average profile
The profile is generated over the active runline. Check the option Use
adjacent lines to take also profiles over the adjacent runlines on each
side. From these profiles an average is calculated and that average
profile is plotted. Enter how much adjacent lines have to be used to
calculate an average profile.
Step size
When the option User defined is not checked the points of the profile
are calculated from the centers of the grid cells that crosses the
runline.
When the option is checked the points of the profile are generated for
each step on the line. Each point is a weighted mean of the four
nearby grid cells. Enter the distance (step size) between two points of
the profile.
Statistics
Define with how much decimals the mean, minimum, maximum and
standard deviation is plotted in the text box. Check the option Draw
Profile when the profile has to be plotted in the panel.
Next to this layer a text layer (see page 586) has to be added to the
The four keywords have to profile panel. After the text layer is added a text box can be added. In the
be added before as Text page of the text box the keywords ‘mean’, ‘min’, ‘max’ and ‘std’ can
keywords (see page 551) be added. The values of the keywords will be plotted in the text box.
The grid model profile statistics can be plotted in the profile panel, in the
profile series panel and in the profile cross series panel.
Set for the X and Y grid the interval and the style. The X grid will present
the KP along the selected route. The value of the KP will be plotted and
with the prefix and/or postfix extra text can be added to the label.
The KP grid data can be plotted in the profile panel and in the profile
series panel.
In the Options page the method how the data is presented can be
defined.
Show lines
The data is presented as a line, where a line a drawn between the
data points.
Show line labels
When the option Show lines is checked this option becomes available.
The name of the line will be plotted next to the line.
Show soundings
The data is presented as dots. It is not necessary that the data is a
sounding; all types of data from the log data can be plotted.
Show soundings labels
Next to each data point a label is plotted. With Label spacing the
In the Options page the smoothing of the profile can be defined. This
smoothing can be used to smooth the generated profile, from no
smoothing to a maximum smoothing with 7 steps in between.
The log data profile can be plotted in the profile panel, in the profile series
panel and in the profile cross series panel.
In the Options page the smoothing of the profile can be defined. This
smoothing can be used to smooth the generated profile, from no
smoothing to a maximum smoothing with 7 steps in between.
The pipe profile can be plotted in the profile panel, in the profile series
panel and in the profile cross series panel.
In the Labels page can be set if the KP labels and route label can be
plotted.
Show KP labels
Check the option when KP labels (KP flags) has to be plotted along
the route. Set the Interval between the KP labels and the Offset for the
length of the KP flag.
Show route label
Check the option when the name of the route has to be plotted next to
the line.
The route data can be plotted in the plan panel and in the key map panel.
Annotation
Format
Select as format Degrees Minutes or Degrees Minutes Seconds.
Decimals
Number of decimals used for the minutes when as format Degrees
Minutes is selected and for the seconds when Degrees Minutes
Seconds is selected. The format Degrees Minutes plots as
minimum 3 decimals even when less decimals is selected.
Hemisphere indicator
The location of the hemisphere indicator (N, S, W or E) in the label.
Leading means that the indicator is placed for the coordinate and
Trailing behind the coordinate.
Add degrees (°) minutes (‘) and seconds (“) symbols
Check this option to plot the symbols behind the degrees, minutes
and seconds.
Interval D MM SS.S or D MM.MMM
Select for the latitude and longitude the interval between two grid lines.
Color and Style
Color and style for the grid lines. The color of the labels can be defined
in the Labels page.
The satellite geographic grid information can be plotted in the plan panel
and in the key map panel.
In the Options page the presentation of the sonar targets can be defined.
Select as symbol for the sonar targets a Circle or a Cross. With the Size
the size of the symbol can be defined. The line style and color for the
circles can be defined in the Line Style page, the color of the cross is
always black.
The sonar targets can only be plotted in the plan panel.
In the Markers options page is defined how the markers of the streak lines
and fairway lines are plotted.
Marker top offset
The offset from the top of the profile panel where the markers will start.
Marker bottom offset
The offset from the bottom of the profile panel where the markers will
stop.
In the Options page the smoothing of the profile can be defined. This
smoothing can be used to smooth the generated profile, from no
smoothing to a maximum smoothing with 7 steps in between.
The theoretical model profile can be plotted in the profile panel, in the
profile series panel and in the profile cross series panel.
In the Cells page is defined how the TIN model data is presented in the
plot. The options Use limits and Use sun illumination are not valid for a
TIN model.
Show cells
If checked, then the cells will be plotted with the colors of the selected
color table of the plan panel (see page 558). The option Points will plot
a colored point in the center of each cell and the option Solid will fill the
cell with one color.
Show labels
If checked, the depth values will be plotted on top of the TIN model
with the label spacing as specified. The label spacing is related to the
selected scale in the Mapping page of the plan panel.
The TIN model data can only be plotted in the plan panel.
The labels of the contours are plotted only when in the contour definition
file for the each contour the option Show labels is checked.
Figure 20-69 Contour properties of a contour in the contour definition file with
the option Show labels checked
In the Contour Levels page, when the contour definition file is selected,
click on to open the Contour window in which for each contour
the contour properties can be edited.
The TIN model contour data can only be plotted in the plan panel.
In the Line Style page the line width can be defined. The color to plot the
data can be selected; use the colors as in the user map file or select a
user defined color.
The user map file can only be plotted in the plan panel.
In the Options page the work areas from the selected work areas file in
the Work Areas page can be selected.
Select the option Show all areas when all the work areas in the work
areas file have to be plotted in the panel. With the option Show selected
areas only the work areas selected in the list will be plotted. Check Show
work area labels when the name of the work area has to be plotted with
the work area.
The work areas data can be plotted in the plan panel and in the key map
panel.
Figure 20-74 Grid page of the XY grid properties for the plan panel and key
map panel
Figure 20-75 Grid page of the XY grid properties for the different profile panels
For the different profile panels the interval for the X and Y can be
different, both has their own interval and style.
The XY grid can be plotted in the plan panel, in the profile panel, in the
profile series panel, in the profile cross series panel and in the key map
panel.
In the overview a drawn plan view will define which area will be used in
the DXF Export Wizard to create the DXF file. Select Place Plan View
from the overview context menu and draw the plan view over the data that
has to be exported. In the Plan View Properties the exact size for the plan
view can be set with Size X and Size Y. Give also a well-defined name for
the plan view, because the settings for the DXF export will be saved
under this name in the DXF Export Files in the Explorer (see page 221).
Figure 20-77 Plan View Properties with an exact size for the plan view
The area covered by the plan view will be the area that is used in the DXF
Export Wizard to generate the DXF file.
Select the option Export to DXF in the context menu of the plan view to
start the DXF Export Wizard.
Click in the welcome page of the wizard on to start with the DXF
Export Wizard.
Figure 20-78 Output DXF file page of the DXF Export Wizard
Figure 20-79 The Select Data page of the DXF Export Wizard
It is not possible to select At the moment only these five data types are available for the DXF export.
two the same data types. If In the future more data types will follow.
the user wants this, then
he can use the standard Log Data; select a data item and a position track of that data item with
plot features to generate a or without labels will be plotted.
DXF from a plan panel. Grid Model; a grid model will be plotted with or without colors and
depth labels.
Contours; contours based on the data from a selected grid model will
be generated and plotted.
Runlines; the selected runlines file with or without labels will be plotted.
Waypoints: the selected waypoints with or without labels and tolerance
circles will be plotted.
The wizard will open only the pages that are related to the selected data
types.
Click on to continue with the DXF Export Wizard.
In all the pages of the wizard the button is available. This means
that at any time when the user goes through the wizard and he knows that
the selections and settings in all other pages are OK, he can click on
to go directly to the Options and Preview page where the preview
or the DXF Export can be started (see page 601).
Figure 20-80 The Plan Panel page of the DXF Export Wizard
In this Plan Panel page several tabs are available to define the settings
for the plot.
Mapping
The scale will be used to generate the right labels sizes and line
widths so that these items are plotted with the right scale when the
DXF export is generated.
Color Table
Select the color table that will be used for coloring the depths in the
plot.
Label Mode
The definition for plotting the labels in the plot.
The coloring can be set on Use Text Color or on Use Color Table.
When Use Color Table is selected all the labels will be colored
according the color table. When Use Text Color is selected then for
each data type the coloring has to be defined.
The rotation can be fixed by selecting Constant and define an angle for
the rotation.
Label Font
Select for the label the font type, the font style, the font size and the
color. The color is only valid when for Label Mode Use Text Color is
selected.
Figure 20-81 The Log Data Settings page of the DXF Export Wizard
In this Log Data Settings page three tabs are available to define the
settings for the data item.
Options
The user can select if the line of the track and the line labels are
plotted or not. If the data item is a sounding the user can select if the
soundings and labels are plotted or not.
The label spacing is the space between two plotted labels along the
track. This is specified in mm and is related to the selected scale in the
Plan Panel page (see page 595).
Line Style
Select the line style, the width and the color for the track.
Depth Biasing
With No biasing the label will be plotted according the label spacing as
specified in the tab Options.
With Shoal biasing a virtual grid with the label spacing as grid size is
generated. For each grid cell the shallowest value will be plotted,
starting with the shallowest value of all grid cells.
With Valley biasing a virtual grid with the label spacing as grid size is
generated. For each grid cell the deepest value will be plotted, starting
with the deepest value of all grid cells.
Figure 20-82 The Grid Model Settings page of the DXF Export Wizard
In this Grid Model Settings page three tabs are available to define the
settings for plotting the grid model.
Cells
If the option Use limits is checked, then only the grid model cells with a
depth between the minimum and maximum depth will be plotted.
If the option Show cells is checked, then the cells will be plotted with
the colors of the selected color table in the Plan Panel page (see page
With the option Points it 595). The option Points will plot a point in the center of each cell and
will take a long time before
the option Solid will fill the cell with one color.
the Preview or the DXF is
generated. If the option Use Sun Illumination is checked, then the sun illumination
settings will be used to change the look of the grid model. This is only
working when for Show Cells the option Solid is selected.
If the option Show labels is checked, then depth values will be plotted
on top of the grid model with the label spacing as specified. The label
spacing is related to the selected scale in the Plan Panel page.
Depth Biasing
With No biasing the label will be plotted according the label spacing as
specified in the tab Options.
With Shoal biasing a virtual grid with the label spacing as grid size is
generated. For each virtual grid cell the shallowest value will be
plotted, starting with the shallowest value of all virtual grid cells.
With Valley biasing a virtual grid with the label spacing as grid size is
generated. For each virtual grid cell the deepest value will be plotted,
starting with the deepest value of all virtual grid cells.
Figure 20-83 The Contours Settings page of the DXF Export Wizard
In this Contours Settings page three tabs are available to define the
settings for plotting the contours of the grid model.
Contouring
Define the criteria for plotting the contours lines and the labels.
The option Suppress contours shorter defines that plot contour lines
shorter than the specified value will not be plotted.
The option Contour label spacing defines the spacing between two
labels on the same contour line. The label spacing is related to the
selected scale in the Plan Panel page (see page 595).
The option Label orientation defines how the labels in the contours will
be plotted. Use Optimum Text Angle uses as much as possible the
orientation of the plan view to plot the labels. Slope Upwards and
Slope Downwards will plot the labels in direction of the slope, upwards
up or downwards up.
The option Smoothing window can be used to smooth the generated
contours, from no smoothing to a maximum smoothing with 7 steps in
between.
Contour Levels
A contour definition file has to be selected. This file has to be
generated before the DXF Export Wizard is started. See page 231 for
information about the contour definition file.
Figure 20-84 The Runlines Settings page of the DXF Export Wizard
In this Runlines Settings page three tabs are available to define the
settings for plotting the runlines file.
Line Style
Select the line style, the width and the color for the runlines.
Labels
If the option Show runline labels is checked then the names of the
runlines will be displayed with the offset as specified.
Label Font
Select the font type, the font style, the font size and the color for the
labels. These settings will overrule the settings made for the Label
Font in the Plan Panel page (see page 595).
Figure 20-85 The Waypoints Settings page of the DXF Export Wizard
In this Waypoints Settings page three tabs are available to define the
settings for plotting the waypoints.
Options
Select a symbol for the waypoints, Circle or Cross. Specify the size for
the symbol in mm.
If the option Show tolerance circles is checked, the tolerance circles
will be plotted around the waypoint.
Line Style
Select the line style, the width and the color for the tolerance circles.
Label Font
Select the font type, the font style, the font size and the color for the
labels. These settings will overrule the settings made for the Label
Font in the Plan Panel page (see page 595).
Figure 20-86 The Options and Preview page of the DXF Export Wizard
21.1 Introduction
In PDS2000 two methods for volume computation are available.
1. In the grid model editor with the operations ‘Compute Volumes’. See
for more details the chapter ‘Grid Model’ on page 530.
2. In End Area Volumes. This option will be described below.
line n
a b
line n-1
Runline
Vessel Track
Half line distance
Data point
Projected data point
a+b
Horizontal area = c
2 *
Figure 21-1 Horizontal area
f
e+f
Delta Z =
2
Reference profile
On the first page of the wizard the runlines, which have to be used for the
volume computation, can be selected. If only a part of the area, that is
Choose reference
Choose the reference level from the following file types and select the
file name. Some of the file types have extra options that have to be
set.
Profile Design Model
No extra options to set.
3D Model
No extra options to set.
Grid Model
Select which data type of the grid model has to be used as the
reference level; the Average, Minimum or Maximum of the Z-value.
Log Data File Set
Select a data item from the log data file set as reference level. For
this item the maximum gap and maximum offtrack can be set.
The maximum gap is the maximum distance between two adjacent
data points on the same runline. In case the distance exceeds the
maximum gap, no volume computation will be done on that
location.
The maximum offtrack is the maximum distance between a data
point and the runline. In case the distance exceeds the maximum
offtrack, no volume computation will be done. A practical value is a
half line spacing.
Tolerances
The tolerances are two extra reference levels, one above and one
below the main reference level. If the tolerances are set, four different
volumes will be calculated; above the above tolerance, between the
above tolerance and the main reference level, between the main
reference level and the below tolerance and below the below
tolerance.
The tolerances are a vertical shift from the main reference level.
Figure 21-8 End Area Volumes with the Vertical Areas page
22.1 Introduction
The export utility in PDS2000 is made to export the PDS2000 log data
files to file formats which can be used with external programs.
The export can be started with Tools > Export from the menu bar or with
from the toolbar in the Control Center.
It will depend on the export type which tabs (pages) are available in the
export setup. The File Sets page is identical for all the export types. On
the File Sets page the file set can be selected, modified or created. With
in the export window, with from the toolbar or with Actions >
Select Data from the menu bar the File Set Editor is opened.
The other pages will be discussed below with the different export types.
For the Excel export it is necessary that Microsoft Excel is installed on the
computer. If not it is not possible to export to an Excel file.
The Options page for both export types are almost identical. In this page
the export format can be specified.
Correlated
In case two or more sensors are selected in the Data Selection page,
one of the sensors can be selected as reference and all the other
sensor data is recalculated for the time of the selected sensor.
Time
If checked, every sensor gets its own time column. When ‘Correlated’
is checked there will be only one time column, the time of the
correlated sensor. The column ‘Time’ can be exported in Excel format
st st
(days since 1 of January 1900) or in ANSI format (seconds since 1
of January 1970).
Header
A header line is written above the data with the file info.
Title row
Each column gets a title above the data with the name of the data.
Open output after export
For the Excel export is the This option is not available for the export type Comma Separated. The
option ‘Post export action’ export file will be opened in Microsoft Excel after the export is finished.
not necessary, because
the file can be opened Post export action
automatically with the If Enable is checked then the exported file will be opened with the
option ‘Open output after program that is specified behind ‘Execute’. If the file has to be opened
export’. in for instance Notepad, the command should be ‘Notepad %F’.
Timed Output
Instead of exporting all the selected data, a time interval can be
defined. If for instance the time interval is 10 sec then every 10 sec
one record of the data will be exported. When ‘Correlated’ is checked
then the time of the correlated sensor will be used as counter.
The Data Selection page is for both export types identical. With the data
selection a data item or a data block can be selected and placed in the
export list.
Format type
Normal
A standard XYZ format is exported.
When the options Insert timestamp at start of swath and Insert
beam number and intensity are checked the time, the beam
number and the intensity will be inserted. At the start of each sway
the timestamp is added to the file, before the XYZ the beam
number is added and at the end the intensity of the beam.
The file contains per ping, if all the options are checked:
Date Time
Beam number Easting Northing Depth Intensity
Beam number Easting Northing Depth Intensity
...
Sonar swath (.IDA)
This a special format for the Sonar Swath utility.
Timed XYZ data with ping no. quality flag
This is a special format with for each XYZ the ping number, the
beam angle and a quality flag.
The beam angle is the launch angle.
The quality flag can be a number from 0 (zero) to 15. The number
is build up of 4 bits of 0’s (zero) and/or 1’s (one), with:
Bit 0 – Brightness
1 = pass and 0 = fail.
Bit 1 – Colinearity
1 = pass and 0 = fail.
On the first page the data types have to be selected. For the export at
least one of the three data sources, multibeam, side scan or snippets,
have to be selected. If at least one of them is selected the user can also
choose to export the attitude and/or position data.
If the option Automatic selection of devices is checked, the export utility
takes always the primary data sources or the data sources that is set as
primary through the automatic switch in the data sources page of the
vessel configuration (see page 103). If the option is not checked the user
can select which data source is used for the export. The automatic switch
will be ignored.
Click on to go to the second page of the XTF settings wizard.
If the Automatic selection of devices on the first page is not checked, the
user can select the which devices is used for the export.
Click on to select for the VRU, the compass or the position another
data source. For the multibeam, the side scan or the snippets the
selected device can be deleted or another one can be added to the list.
If the Automatic selection of devices on the first page is checked, there is
nothing to select on this page, this page is then pure for information to the
user.
Click on to go to the last page of the XTF settings wizard.
22.2.5 S7K
Next to the File Sets page nothing has to be specified for the S7K export.
The S7K export file contains the same records, if available, as specified
for the S7K logging (see page 122).
22.2.6 SDS
In the Options page for the export type ‘SDS’ the SDS settings for the
export can be defined.
It depends on the selected settings which CTL file will be exported next to
the SDS file. The four CTL files are:
Grid coordinates with all the data (GridCoordsFull.ctl).
Geographical coordinates with all the data (GeoCoordsFull.ctl).
Grid coordinates with position, time and depth (GridCoordsBasic.ctl).
Geographical coordinates with position, time and depth
(GeoCoordsBasic.ctl).
22.2.7 SZ
In the Options page for the export type ‘SZ’ the export file name can be
defined, the channels and the data reduction can be set.
The user has to fill in a list with SZ records, which are not available in the
PDS2000 log data file.
Channel
The user can select which channel or both channels has to be
exported from the PDS2000 log data file(s).
Data reduction settings
If the option Use data reduction is checked the data will be reduced
with the value as defined with Interval in m. This means that each
interval value data will be exported.
Aufnameart
Select the measure method that was used during logging the echo
sounder data.
3D model GLW
The echo sounder data will be corrected for the GLW value(s)
belonging to be exported runline(s). This will be done with the GLW
value(s) as specified in the selected 3D model.
The user can choose between an export in Bartel ASCII DAT format or in
Standard UXO format. If the user choose for the standard UXO format
some extra settings can be defined.
File header include file
It is possible the add a header file to the UXO export file. Click on
and select an UXO file as header file. The path and file
name will be displayed in the text field.
Decimal symbol
There can be chosen between a Dot or a Comma as decimal sign in
the numbers in the UXO file.
Relative coordinate origin
In the UXO file the local grid coordinates X and Y are written. If these
numbers are to big to use in other programs an origin can be defined
so the grid coordinates in the UXO file getting smaller. The Northing
and Easting as entered will be subtracted from the local grid
coordinates.
Sensor height
The sensor height will be written in the UXO file as the Z value.
The default and standard format is FAU 1 with the beam angle. There is
no difference in the file name between both formats.
The FAU file will be identical with a logged FAU file and is explained in
the logging (see page 123).
22.2.10 GSF
In the Options page for the export type ‘GSF’ can be selected if the
multibeam data in the GSF file is uncorrected or fully corrected. The
corrected multibeam data is computed according the multibeam xyz
computation in the multibeam device data.
The GSF file will be identical with a logged GSF file and is explained in
the logging (see page 124).
22.3 Exporting
If everything is set for the export, the selected data can be exported. Click
on from the toolbar or select Actions > Export from the menu bar to
start the export.
For the export types ‘Excel’, ‘Comma Separated’ and ‘SZ’ the standard
Save As dialog is opened and a default filename is given.
Select the location and give a proper filename for the export file and click
on to start the export. For the other export types the files are
directly saved with a default filename in the LogData folder. A Progress
window will appear to show the progress of the export.
Index ASCII File - 136, 140, 143, 147, 199, 221, 223,
224, 225, 238, 239, 243, 420, 480, 487,
503, 507, 524, 540, 610, 614
ASCII Import - 136, 137, 140, 238
Auto Pilot - 284
Auto Recache - 400
Automatic Identification System - 358
AVI File - 209, 246, 254
─3─ ─B─
3D Box View - 417, 466, 510 Backscatter - 121, 312, 504
3D Design Model - 152, 192, 364, 421, 427, 434 Backscatter Processing - 393
3D Design Model Editor - 144, 146 Bartel ASCII DAT Format - 624
3D Model - 131, 144, 145, 152, 186, 219, 221, Basic Operator - 200
222, 224, 345, 520, 529, 531, 605, 623 Batch Plot - 163, 188
3D Object Manager - 219, 255 Beam Color Mode - 420, 423, 425, 470, 479,
3D Objects - 219 487
3D Studio Model - 214 Beam Quality Filter - 324
3D View - 50, 93, 255, 522 Beam Reject Filter - 324
3D View – Online - 272, 273, 277 BITE - 306
3D View – Online Dredge - 272, 274, 277 BMP File - 209, 216, 246, 248, 254, 276, 299,
3D View – Standard - 421, 422, 425 301, 339, 352, 371, 380, 383, 419, 423,
466, 479, 482, 486, 490, 498, 500, 510,
545, 568
─7─ BPP File - 190
7K Center - 283 BSB Chart - 219, 246
Bursa Wolf - 78
─A─
─C─
Absorption - 282, 285
Access Level - 202 Cassini-Soldner - 84
Acquisition - 24, 53, 68, 69, 91, 93, 97, 105, 107, Circular Interpolation - 186, 452, 517, 535
108, 112, 118, 131, 141, 147, 148, 149, Clipping Polygon - 126, 145, 147, 220, 224, 225,
155, 156, 160, 200, 201, 203, 215, 216, 234, 355, 442, 499, 500, 504, 510, 513,
223, 239, 240, 246, 251, 252, 254, 259, 519, 520, 521, 522, 523, 524, 526, 527,
261, 262, 264, 265, 270, 271, 272, 280, 530, 535, 571, 605
290, 291, 302, 307, 340, 343, 345, 362, Clipping Polygon Editor - 214, 225
363, 368, 370, 383, 386, 387, 440, 456, Clock Synchronization - 163, 165, 166, 167
497, 507, 523 C-Map - 11, 14, 24, 25, 26, 28, 29, 32, 34, 36,
Active Editor - 399, 401 37, 215, 216, 217, 348, 352, 353, 571
Active Vessel - 255, 256, 257, 288 C-Map Chart Manager - 30, 32, 33, 34
Administrator - 200 Color Mapping Panel - 557, 568
Advanced Computation - 101, 402 Color Maps - 216
AIS Layer - 358 Color Table - 220, 226, 227, 229, 233, 276, 278,
Alarm - 53, 69, 126, 129, 144, 148, 149, 153, 309, 310, 311, 323, 354, 361, 419, 421,
219, 254, 259, 278, 279, 373, 384 423, 426, 427, 466, 468, 479, 483, 486,
Alert Sounds - 62 500, 501, 510, 525, 532, 540, 545, 568,
Alerts - 259 572, 595
Alerts View - 255, 256, 278, 279 Color Table Generator - 226, 227, 229
ALL File - 187 Compass - 319
Anchor Definition - 106 Compass View - 280
Angle to Detection Point - 329 Computation - 101, 102, 131, 255, 384, 391
Anomalies - 260, 393, 395, 401 Condition - 103, 155, 156
─U─
UDP/IP - 170, 172
Uncertainty of the Hypothesis - 440, 443, 469
Units - 58, 81, 84, 94, 97, 127, 216, 238
Universal Transverse Mercator - 84
USBL Calibration - 393