RELEASE NOTES

NAVIEDIT 8.5.1

Last update: 03/03/2020

Version: 8.5.1
 Contents

1 Release notes NaviEdit 8.5.1 ......................................................................................... 3

1.1 Formatting conventions .............................................................................................. 3

2 Service Pack 8.5.1 ........................................................................................................... 3

3 New features.................................................................................................................... 4

3.1 Free objects ................................................................................................................ 4

3.2 Binning filter ................................................................................................................ 5
3.3 Position quality ........................................................................................................... 7
3.4 Imagenex DT360 ........................................................................................................ 8

4 Minor improvements .................................................................................................... 10

4.1 Enhancements ......................................................................................................... 10

4.2 Workflow Manager enhancements ........................................................................... 12
4.3 Bug fixes ................................................................................................................... 12

5 Database upgrade ......................................................................................................... 13

6 Known limitations ......................................................................................................... 14

Page 2 of 14
 1 Release notes NaviEdit 8.5.1
NaviEdit 8.5 collects a series of features and fixes implemented during the second part of
2019.

NaviEdit 8.5 is a major release and remains backwards compatible with previous versions of
NaviEdit.

NaviEdit 8.5.1 includes a series of minor bug fixes.

This version includes an automatic database upgrade to NaviEdit database version 8.0.3.5
and is designed for direct combability with NaviModel 4.4. You can find compatibility details
via the EIVA Download Site.

1.1 Formatting conventions

Items formatted in bold are properties, buttons, or other elements in the NaviEdit software.

2 Service Pack 8.5.1

NaviEdit 8.5.1 includes a series of minor bug fixes after the first usages of version 8.5. It is
fully compatible with version 8.5

The main issue was related to the use of new license activator tools, unfortunately it had a
missing link when adding new workstations to a server environment – it was not possible to
identify the server. This have now been fixed

 Fixed a problem with the look up in the binary geoid.bin or geoid.gbin file for
Height/Bathy calculation
 Fixed an import crash for GSF files which have ranges without having bearing
angles.
 Fixed an insufficient number of decimals for the rotational part of a possible datum
shift saved in geodesy.ini. This could affect a datum shift defined during import of
geographical GPS coordinates.
 Fixed an issue with a dummy zero valued motion sensor being set as the active
when merging position data without motion and saying yes to the 'Merge data
missing and dummy inserted, do you want to commit anyway' dialog.

NaviEdit851.docx
Page 3 of 14
Last update: 03/03/2020
 3 New features

3.1 Free objects

NaviPac uses a term called free objects – those are eg transponders from a USBL that
haven’t been assigned to a vehicle. They can now be imported into NaviEdit – and assigned
to vehicle and used like ordinary position sources.

Figure 1 Assign Free object

Page 4 of 14
 Figure 2 Object relationships

3.2 Binning filter

Added an option to change the binning filter during import of NaviScan SBD files with
interferometric multi-beam data. 3 different filtering options are available:

NaviEdit851.docx
Page 5 of 14
Last update: 03/03/2020
 Figure 3 Binning filter

1) Divide the across direction in bins with the specified bin size, find the vertical
median value in each bin and accept all values in each bin with a vertical value +/-
the noise limit around the median value.

Page 6 of 14
 2) Divide the scan in angle bins with bin size width and find the median range value in
each bin and accept all values in each bin with a range value +/- the noise limit
around the median range.

3) Divide the scan in range bins with the specified bin size and find the median angle
value in each bin and accept all values in each bin with an angle value +/- the noise
limit around the median range.

3.3 Position quality

The standard deviation of position source plays an important role when re-calculating and
merging position sources in NaviEdit. To support this, we have introduced a new window for
read-only display of the standard deviation.

NaviEdit851.docx
Page 7 of 14
Last update: 03/03/2020
 Figure 4 Position quality time series plot

3.4 Imagenex DT360

NaviEdit includes a tool to import data recorded by the Imagenex system as standalone
tracking. Please note that you can also interface and record the setup in NaviScan

The tool is divided in three steps

1. Import DT360 as multibeam data block
2. Merge cable, motion and gyro data from csv into the multibeam data
3. Calculate navigation track based on cable and attitude data – user enters start
location

Page 8 of 14
 Figure 5 Data editor with final result

Figure 6 Imported in NaviModel as point cloud

NaviEdit851.docx
Page 9 of 14
Last update: 03/03/2020
 4 Minor improvements

4.1 Enhancements

 Added an 'open containing folder' path to the first page in the export wizard, to
automatically open the containing folder when the export is done.

 Added the option to Merge the bathy from another Block. The action is found in the
JobPlanner Tools menu.

Page 10 of 14
  Added support for the new NaviPac .rlxp runline format.
 Added a binary LAS export.
 Recalculation of objects with combined position now allows you to first recalculate
the position of the individual transponders before recalculating the combined object.
 The file import report now shows the quality distribution of merged multi-beam data.
 Added an 'Update Standard Deviation' action in the JobPlanner to update the
standard deviation of a position source which is part of a combined object. The
definition of the standard deviation is found in the combined position object.
 Re-introduced the option to skip every nth scan during import.
 Changed the extension of exported UKOOA P1/90 files from 'UKOOA' to 'p190'.
 Added an option to the UKOOA P1/90 exporter to export Ocean Bottom Nodes
average position.
 Added the option to enter a position mounting for the NMA merger. Note: The
existing mountings are shown and can be selected as the new mounting or if the
value is changed the new mounting will get the changed value.
 Reintroduced the SPS exporter (Shell Processing Support Format Rev 2.1). The
receiver exported is intended for USBL position fix like exports of Ocean Bottom
Nodes. The intended use of the source export is for CSEM Seismic data with a
Front and Tail Electrode.
 Added support for 3D at Depth underwater LIDAR.
 Support for IMAGENEX external sensors.

NaviEdit851.docx
Page 11 of 14
Last update: 03/03/2020
  Added a Turbidity merger to merge visibility into an existing block. Could also be
used to merge other single beam values.
 Added an EIVA Pipetracker merger to merge pipetracker results from the EIVA
Deep Learning board into a block.
 Added a Kongsberg Hugin merger to merge pipetracker results from the Kongsberg
Hugin.
 Added a new JobPlanner > Tool > Combine Pipetrackers action to create a new
combined pipetracker object that is the average of the existing pipetrackers.
 The different NaviEdit programs like the different importers started from the
JobPlanner now automatically remember the position on the monitor the next time
the program is started.

4.2 Workflow Manager enhancements

A series of new commands have been added to the WorkFlow manager tool:

 Added WorkFlowManager XML configuration support for choosing between 'Raw

range/bearing' and 'Depth XYZ' datagram during import of Kongsberg .ALL files.
This is done by adding a new datagram attribute to the EmInterpreter element. Note
Kongsberg HiSAS should be imported as 'Depth XYZ':
<EmInterpreter version="1.0" emType="3" datagram="0">
<!-- datagram 0: Raw range bearing, 1: Depth XYZ -->
 Added the option to import a runline with the Workflow Manager
 Added the option to call the NavInXTF export from the Workflow ManagerAdded a
SetGeodesy task, so it is possible to change the projection, ellipsoid and apply a
possible datum shift with the Workflow Mananger.

4.3 Bug fixes

 Merging of Cathx PCP files could mark some beam with an ‘invisible’ negative
quality, this is now fixed.
 The CSEM Tx export dialog should now always show both single beams and
objects.
 Fixed a wrong Doppler Vy value in the CSEM Tx export.
 Dynamics offset for transponder objects with absolute position like Sonardyne
SPRINT are no longer imported.
 Fixed a bug in import of the new Kongsberg KMALL format.
 KMALL import does not subtract or reapply the two-way travel time correction from
Kongsberg. The user should simply use the already corrected travel time.
 Fixed some import problems for KMALL files, among others correct echo sounder
roll pitch crosstalk when heading is non-zero.
 Fixed a problem running the SQL Query Report.

Page 12 of 14
  The Sound Velocity Profile Correction which was created from within the
DataEditor was not saved. This is now fixed.
 Fixed a bug in Use Secondary Sensor where the list of other sensors did not
show.
 Now mark near-horizontal beams ending at the MBE head (0, 0) as deleted when
they bounce out of the water (above the water line).
 Ensure block duration of embedded SVP/CTD is zero.
 Ensured pitch is not saved without roll and vice versa
 Fixed a Recordset is read-only database error when replacing an existing sensor
during merge.
 CSEM Rx and Tx exporters: If a NaviEdit datum shift is in use, it is reported in the
export header. Otherwise report the one from the NaviPac H3 header written in the
import report.
 Innovatum pipe tracker solution value was wrongly always 0.
 Recovery of Kongsberg files did not load secondary sensors correctly and was
missing motion C-O.
 Correctly handle the possible transmit delay for different sectors for Kongsberg
echo sounder for both .ALL and .KMALL files.
 Don't collapse the JobPlanner left side tree view when editing files. (The tree
rebuilds when new files are imported to detect new files and folders.)
 Fixed slow running of 'Estimate DVL Mounting'.
 UKOOA P1/90 export now automatically takes Area, Job, Vessel and Client from
NaviPac header
 Fixed: When multiple NaviPac S-files were loaded into the same folder, combined
position items showed up with duplicate transponders in the Header Editor.

5 Database upgrade
This version includes a database upgrade to NaviEdit database version 8.0.3.5. You can
find compatibility details via the EIVA Download Site.

The Microsoft SQL Server included in this NaviEdit installer is SQL Server 2019 Express.
This SQL Server requires Windows 10 64-bit. You can install this NaviEdit on a Windows 7
computer; you just need to download the free SQL Server 2012 express version or connect
to a SQL Server on another computer. If you want to install NaviEdit on a Windows 7
computer, select the 'Select this option to connect to a SQL Server on another computer'
option during installation.

If you want to upgrade from SQL Server 2012 Express to SQL Server 2019, you should
uninstall the 2012 version first. EIVA does not see any urgent need to do this as NaviEdit
databases created with SQL Server 2019 cannot be attached to earlier versions of the SQL
Server.

NaviEdit851.docx
Page 13 of 14
Last update: 03/03/2020
 NaviEdit can connect to SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL
Server 2014, SQL Server 2016, SQL Server 2017 and SQL Server 2019.

6 Known limitations
There are no known major problems.

Page 14 of 14