Blog

Blog

Did you know: it's very easy to link the 3D editor selection box to the scroll reference line

Just press ctrl + left  mouse click on the navigation after having made the 3D selection box. The selection box is then linked to the navigation, turning the navigation into the scroll reference line. You can now use the key combinations ctrl + →  and  ctrl + ↓ on your keyboard to move the scroll box up and down along the scroll reference line. For more information visit our Howto Qimera - Scroll referencing knowledge base article.

Remote Display Client – RDC

The Remote Display Client or RDC is a tool within QINSy that is used to broadcast QINSy data from the main data acquisition computer to remote computers. 

 

With the RDC add-on enabled on the QINSy license, QINSy is able to send the actual raw sensor data, computed data, survey line information and bathymetry information to any computer that is in the same network, it is not just video streaming. The only requirement is that QINSy is also installed on the remote computer(s). No USB dongle is required for the remote computers, and there is no limitation on the number of sessions that can be running simultaneously.

Besides sending data, it is also possible to configure the RDC to control the data recording from the remote location. For example, a surveyor is able to oversee and control a survey from a position on the bridge while the main survey computer is in a different location on the vessel where all the system interfacing is done. This allows the surveyor to start and stop the survey recording.

The main survey computer that sends out all the data also controls what others are allowed to see, use or do.

 

 

The RDC looks very similar to the QINSy Controller and provides the same display options as the QINSy Controller. The user has the ability to create and configure displays to his/her preference, and it is also possible to define multiple display sets for different operators on different shifts.

Use cases

The RDC option can be used to provide the ROV pilot survey information such as a 3D picture of the ROV hovering above a pipeline, including actual raw and processed multibeam data, bathymetry information from the sounding grid as well as 2D/3D measurements. The RDC can provide the captain with survey information, such as real-time bathymetry being updated in the sounding grid and the survey lines that he is sailing. It can also be used to provide a client representative with survey information in his own cabin, the client rep. is then able to receive survey information and perform quality checks at any given moment without having to bother the online surveyor. If a vessel has an internet connection to an office, the information can also be displayed onshore using the same principles.

 

An example of a use case can be found on our website under the client spotlight, where tunnel segments were transported over water and placed at the correct location using QINSy and the Remote Display Client. http://qps.nl/display/main/2015/02/09/20150209_ClientSpotlight_Geovisie

 

Ask our sales team for more information about the Remote Display Client.

A new howto was just added to the Qimera Knowledge Base, describing how to work with Reson S7K data in Qimera and providing sample data for download: Howto Qimera - Working with Reson S7K Data

We now have howto documents and sample data sets available in the Knowledge Base for all of Qimera's currently supported raw sonar formats – QINSy, Kongsberg ALL, Hypack HSX, and Reson S7K. The documents currently available in the Knowledge Base continue to evolve and the available documentation continues to grow weekly – if there is documentation you would like to see, please contact our support department and let us know!

Interested in trying Qimera yourself? Sign up for an evaluation!

Show which line is Up-or downcast in Import SVP dialog

The Import Sound Velocity Profile dialog in the Echosounder Settings shows the up-and downcast (when available) in different colors.

Note that in the Options of the Import dialog it is possible to select whether to use only up-or down cast.

Add sound velocity from system to velocity profile

Most multibeam systems are able to measure the sound speed at the transducer. As this value is more up to date than the SVP, it makes sense to use the near real-time value for ray tracing.

A problem here is that the units do not really report the sound speed at the head, they report the sound speed at the head that they used to calculate the beam angles. When the unit is configured to use the real time sound velocity, this value will be equal to the actual sound velocity at the head, but there is also an option to set the sound velocity the unit uses by hand. In that case, the reported sound velocity may not match the actual sound velocity.

Because of this fact the usage of the sound velocity received from the unit is now a user configuration item.

In this version of QINSy, support for True KP was added. This means that it is now possible to compute/show/output KP values based on ellipsoidal distance along the pipe/cable route. In previous versions this was only possible by overriding the KP values at each of the Control Points making up the pipe/cable route. In the most recent version it is no longer necessary to do this. If the user decides to use True KP and modifies the setting as shown below, this is applicable to all KP values computed/shown/output in QINSy.

 

True KP activation

In order to use the True KP option the user should change the 'Distance Reference' setting in the 'Global Settings' dialog from 'Grid Range' to 'True Range' as shown below:

After activating the new setting the user should restart any modules that are active (i.e. the Controller in an online situation).

 

Once the new setting is active it is applicable to all KP values as computed/shown/output throughout QINSy. However any files that contain KP values need to be recreated in order to contain True KP values. Currently the only file that contains KP values is the QPD file. Therefore, it is recommended to make sure this setting is correct at the start of a project.

 

User Supplied KP Values

In case the user has chosen to enter KP values at the control points the modules will compare the entered KP values against the Grid KP values. If the entered KP values match the Grid KP values to within 1 ppm it is assumed that the entered KP values are Grid KP values. In this case the KP values are automatically converted to True KP values when the user decides to change the Global Setting mentioned above. If the difference is larger than 1ppm the user entered KP values will remain active and the changed setting has no influence on the computed/shown/output KP values.

 

Navigation Surface Support

It is now possible to have multiple Navigation Surfaces. This can be useful to split survey data in several areas or to have the data in Navigation Surfaces with different cell sizes. The Navigation Surfaces are all listed under Grids in the project explorer. A link icon in front of the name indicates that it is a Navigation Surface to distinguish it from a normal sounding grid.

 

New Data Filters

The newly implemented filters, located in the Filter Wizard, can reject data based on quality, TPU, intensity, or position mode. 

 

Tide Data Manager Updates

This stand-alone tide prediction utility has been improved. Buttons have been added to step through tide predictions and also the reporting and export have been improved. For finding tidestation from a long list a filter option has been added.

 

 

 

 

 

In the Fledermaus module, Explore Mode is the primary mode used to interact with your data. When you are in Explore mode, you hold down the left mouse button and move your mouse to rotate around the point of interest (by default, the center of the loaded data), you middle click or push on the scroll button to move the point of interest, you scroll in and out to zoom, and you right click and drag on a DTM surface to create a profile. Using this mode you can quickly and easily move through your dataset.


Explore Mode in Fledermaus.

When you want to select part of the surface, say in order to select an area for cleaning in the 3D Editor, you choose a selection mode – Select, Polygon Select, or Area Select. The Selection Modes changes how your left mouse button operates – left-clicking and dragging the mouse will now create a selection. You can still use the middle mouse button to move location and scroll, but you can't rotate.


Fledermaus Selection Modes. Note that the mode description and hotkey (in parenthesis) become visible when you mouse over the button.

Once you have a selection mode active, you select the location of interest and click Launch 3D Editor to view the point information and clean the data. To move to a new location, you go back to Explore mode, then activate the selection mode again to select the next area. A pro user of the software probably knows that one way to speed up that process is to use the hotkeys: Space Bar for Explore Mode, S for Select Mode, P for Polygon Select Mode, A for Area Select Mode, and the 3 to launch the 3D Editor. However, even a pro user may not be aware that you can temporarily override a selection mode to explore your data by holding down the Shift Key, and then using the mouse as if you were in Explore Mode.

Try it now: Click on Select Mode (or use the S hotkey), then left click and drag the mouse to create a selection rectangle. Now hold down the shift key and use your mouse to move to another part of the dataset. When you are holding the shift key, you will be able to rotate in the scene even when you have the Select Mode activated.

For a demo of this tech tip, watch the movie linked below.

 

New Export Formats

Quick setup for VisualSoft Export

In the Generic layout editor the option is added to quickly generate a new layout in order to export raw profiler data to VisualSoft's file format. Select from the File pull-down menu option Generate Layout, Export, Visual Works...A dialog will appear where the user only has to select which profiler (or multibeam) system to use. Finally, pressing the generate button will automatically create two layouts, one called XP and one called RAWSURVEY.

These two layouts can be used in the Export Generic Wizard in order to export your raw profiler data to files which can be imported into VisualSoft's VisualEdit Professional Processing software.

 

 

LAZ/LAS Data Format Export

In this version of QINSy it is possible with the Processing Manager to export QPD data to the LAS/LAZ format. The LAS format is a public binary format typically used to exchange 3D point cloud data. The format originated in the LIDAR community, and LAZ is a compressed version of the LAS format. The export module supports version 1.2, 1.3 & 1.4.

 

WCD in SBES Display & WCD Editor

In this version, Water Column Data (raw echogram) support for Single Beam Echo Sounders (WCD SBES) was added to both the online Single Beam Echo Sounder display and the offline Water Column Data Editor. This makes it possible to add the WCD as a background in the Single Beam Echo Sounder display and to monitor the quality of the bottom detection while recording the data. It also makes it possible to monitor any other reflectors present in the water column such as gas seeps, wire or seaweed. See example:

 

Offline, using the WCD Editor utility (Processing Manager) allows the user to quickly check and even to alter digitized depth (with the changes being written directly to the QPD file), see example:

 

 


3D Editor in Processing Manager

 

3D Editor added to Edit ribbon of the Processing Manager

 

With a valid QLOUD license, now a 3D editor is available in the Processing Manager. First an area needs to be selected and then the editor can be started. The editor has keyboard shortcuts available so that editing can be done by using mouse and keyboard in combination. For further information there is a Howto document available in the Knowledge base and also the online help has a description of the new functionality.

 

3D Editor module

 

3D View DTM Surface In Processing Manager

A 3D view is available which shows the navigation surface. The view can be enabled from the View menu. The plan view and 3D view are synchronized so that panning with the middle mouse button in plan view is followed by the 3D view.

 

3D DTM view

 

For more information or to download the latest QINSy release, please visit the QINSy release webpage.

 

 

Fledermaus 7.4.1 (released 4 July 2014) included new tools for working with watercolumn data – semi-automated feature detection and cluster analysis.  These research tools were originally written by Dr. Tom Weber of the Center for Coastal and Ocean Mapping (CCOM) at the University of New Hampshire to help detect seafloor seeps in watercolumn data.  The QPS developers have used the Fledermaus plugin architecture to create a new tool that is now available to all FMMidwater users, another example of successful partnership between researchers and industry. 

We will be hosting webinars on July 22nd and July 23rd to demonstrate the new functionality, please visit the webinar event page for more information and to register.  We have also created two new Howtos with step-by-step instructions, the first explaining how to use the Feature Detection tool in FMMidwater and the second describing the associated Point Clusters SD object and clustering analysis tools found in Fledermaus.


Preliminary view of a watercolumn file prior to any filtering.



Scanning for potential seeps manually using signal level.



Potential seeps detected using despeckling filter in the Feature Detection tool.

 


To view a larger version of any image, simply click on it.

 


Line Data Manager Functionality

The majority of the Line Data Manager functionality has been integrated into the Processing Manager. Future QINSy versions will likely include the as yet not ported functions. For the time being the Line Data Manager may be used to perform these functions. In preparation for new functionality the Processing Manager stores the survey line data in two file formats. The first file format is the PRO-file format which is also used in the Line Data Manager and the second format is the QGF-file format. In future releases the QGF-file format will be used throughout QINSy.


Line Data Manager showing PRO-file

The Line Data Manager functionality may be found in a separate ribbon which becomes available after selecting a Line file in the Project Explorer pane. A Line file may either be newly created by selecting the New Line from the File menu or by importing from a AutoCAD DXF, DWG or Microstation DGN file. An option is also included to export the data to AutoCAD DXF file format where by the following AutoCAD versions are supported: R13, R14, 2000, 2004, 2007, & 2010.


Improved workflow to generate grid from QPDs

Only two steps need to be executed in order to fill a grid using a number of QPDs:

1.Select QPDs which are to be added to the grid file
2.Select/Create the grid file and additional properties.


Selecting QPDs to add to grid file



Selecting grid file and additional properties

 

Improved workflow to edit data using Qloud

It is no longer necessary to separately group the QPDs. The user may just select the QPD files and choose the edit in Qloud option.


Selecting QPDs to be edited in Qloud

 

Once the correct files have been selected the QTM file settings may entered. This dialog gives the user control over which systems will be part of the QTM file and what information will be transferred into the quality field of the QTM file. In case a Navigation Surface was created the program will re-use as many settings as possible.


QTM settings dialog

 

Once the QTM file creation is finished Qloud will open to allow processing. While processing in Qloud the QPD files will remain marked as locked in the Processing Manager.


QPDs being edited in Qloud shown as locked

 

When the processing is finished and Qloud is closed the user is given the option to immediately synchronize the changes made to the QTM file back to the QPD files.

Synchronize changes in QPD dialog 

 

The user may however decide not to synchronize the changes in the QTM file to the QPD files. This will allow the user to come back at a later stage and resume editing in Qloud i.e., the next day.

While the changes in the QTM file have not been synchronized back to the QPD files the QPD files remain marked as modified.


QPDs shown as being modified 

 

Once the user is finished processing the data in Qloud the changes may be synchronized back to the QPD files by using the Synchronize option.


 

 

When: Version 7.4.1 of the Fledermaus Suite, released 4 July 2014 includes an important bug fix that may impact the appearance of your processed backscatter.  

What are the changes?

It was recently discovered that the backscatter corrections being done in FM Geocoder Toolbox (FMGT) were not correcting for seafloor 3D incidence angle, even when corrected bathymetry was included in the processing routine.  We have added a fix to use a Reference Grid (in Fledermaus SD format) to determine the topographic slope during processing and mosaic creation.  To clear up any potential confusion, it is important to point out that the corrected bathymetry data that has been necessary to import data into FMGT have only ever been used for georeferencing seafloor imagery.  The original Geocoder software from UNH provided the ability to compute the 3D incidence angle with a Reference Grid, however, this was only implemented for sidescan sonar imagery and not for multibeam imagery.  We have followed the same strategy for multibeam imagery now and the Reference Grid is now used to estimate each beam's 3D incidence angle with the seafloor.  This more accurate method of calculating the incidence angle directly improves the accuracy of the ensonified area correction, which is a function of the projected beam footprint size on the seafloor.

While implementing the Reference Grid calculations for multibeam imagery, a small number of errors were noted in the original UNH Geocoder approach.  These were corrected for the multibeam imagery correction algorithms, however, the corrections have not been ported to the sidescan signal level corrections yet.

Who does this impact?

This type of correction is particularly important for ARA users since the input signal to ARA now represents the seafloor's true backscatter value with much higher fidelity than before.  For FMGT users who focus primarily on creating seafloor mosaics only, the new algorithm will dampen topographic effects, such as higher signal levels on inward facing slopes and lower signal levels on outward facing slopes.  As part of our ongoing efforts to improve the underlying Geocoder algorithms from UNH, we have identified the need to propagate the angle and terrain corrections into the AVG stage of processing.  Once this is complete, mosaic imagery will have a much higher fidelity in representing seafloor backscatter.  Look forward to this in a future release.

The terrain correction can be applied for Kongsberg, Reson and R2Sonic multibeam systems that have the sonar beamwidth and pulse length parameters correctly recorded in their data stream.  The corrections are done for both .ALL input format (Kongsberg only) and for .GSF (Reson, R2Sonic and Kongsberg).

Where to get more help?

This HowTo explains how to add a Reference Grid and create a new mosaic.  If you have any questions or need further clarification, please contact Support (support@qps.nl).


 

The American Polyconic projection may be visualized as "rolling" a cone tangent to the Earth at all parallels of latitude, instead of a single cone as in a normal conic projection. Each parallel is a circular arc of true scale. The scale is also true on the central meridian of the projection. The American Polyconic projection is used in Brazil and the South Pacific.