Skip to main content
Skip table of contents

Storage - SoundingGrid

To be able to store data into a sounding grid file, a sounding grid file needs to be created first.
This can be done either in the program Sounding Grid Utility or directly in the Session Setup by clicking on the "New" button.

File
FormatSelect a "*.grd - Sounding Grid" from the pull down menu when data needs to be stored in a sounding grid file.
FilenameSelect the designated grid file by pressing the browse button. A standard MSWindows selection window will appear.
Overwrite Mode

In case the date attribute is available in the sounding grid an Overwrite Mode will be available.
By default data in the sounding grid will be automatically merged with newer data.
The attributes are set during creation of the sounding grid file or during creation of a new layer in the sounding grid.
A sounding grid or a new layer are created using the Sounding Grid Utility or directly in the Session Setup by using the "New" button.

  • Age - In case the last update in a cell has a certain age the cell will be cleared and filled with newer data.
    • Used when using a Multibeam on a cutter dredger. When swinging in a cut the data can be averaged if the data is not older than the threshold age set.
    • This can be useful if you want to redo a survey line and only want to overwrite the sounding grid data of the previous attempt.
  • Time (older than) - In case the data in a cell is older than the time and date entered by the user, the cell will be cleared and filled with new data.
Age (minutes)Only visible when Overwrite Mode is set to Age.
DateOnly visible when Overwrite Mode is set to Time (older than).
TimeOnly visible when Overwrite Mode is set to Time (older than).
<New>

Option to create a new sounding grid file. Options are the same as in the Sounding Grid Utility.
Select the File, the Survey Units and the Origin of the grid:

Edit the name of the Reference layer, select which kind of data will be stored in it and select how extensive the data should be stored:

Edit the name of the Survey Data layer, select which kind of data will be stored in it and select how extensive the data should be stored:

Use <Add layer> when more layers are needed in the sounding grid.
Use <Remove layer> to delete layers not in use.

<Clear Layers>

Erase all data from a selected layer in the currently selected sounding grid file.

First select a layer, then press <Erase>.

<Import>

Import data (points file or another grid file) into the currently selected sounding grid file.
The options are similar to the Import option in the Sounding Grid Utility.


Press <Execute> to start the import.

Systems
System

For each system a storage layer can be selected.
This can be a different layer or the same layer.
In the Sounding Grid only data which passed the online filters as set in the Echosounder Settings will be stored.
The motion (roll, pitch, heave), height settings etc. are already applied to the data if this information is available online.

When a magnetometer is present, a magnetometer grid can be created and activated.
A corridor can be set which will look like a swath from a Multibeam echosounder, containing the one value of the magnetometer over the whole corridor width.
This 'swath' will show in the Navigation Display to indicate which area has been covered by the magnetometer survey.
The maximum width of the corridor is 100 times the minimum cell size of the sounding grid.

LayerThese layers can be defined in the Sounding Grid Utility or in the <New> option above, using the <Add layer> button.
For multibeam systems it is also possible to write, besides bathymetric data, backscatter data to a sounding grid file.
So for each multibeam system you will find two entries in the list: one for bathymetry and one for backscatter.

It is advised to write this information to two different layers in the sounding grid file to make a clear distinction between the two types of data.

Return to: Storage

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.