2023-001

FMGT BACKSCATTER PROCESSING

Ocean Winds NY Bight 0537

Bluepoint Wind Project

2023-001_FMGT PROCESSING GUIDE Page 1

REV.0

GEO-SERVICES
 1. PURPOSE
The purpose of this document is to provide direction for MBES backscatter processing using Fledermaus Geocoder
Toolbox (FMGT) with data collected in Qinsy and bathymetry processed in Qimera. This document is project
specific to 2023-001 adhering to the latest revision of TS-QM-GL-001 Guideline for Control of Governing
Documents. For specific project amendments, the Project Manager is responsible for scheduling and enlisting this
document owner’s assistance and approval for the content and procedure of the amendment.

2. ABBREVIATIONS & DEFINITIONS

ABBREVIATIONS
MBES Multibeam Echo Sounder
FMGT Fledermaus Geocoder Toolbox

DEFINITIONS
N/A xxx

3. CODE, STANDARDS & REFERENCE MATERIAL

DOCUMENT NO. TITLE
Company References
Xxx xxx xxx or N/A Xxx
Industry Standards and Specifications
IHO S-44, S100
3rd Party References
xxx

4. ROLES & RESPONSIBILITIES

The designee listed on the title page is responsible for the issue and maintenance of this document. All TerraSond
Employees and contractors are required to follow this Guideline and any project specific amendments approved

2023-001_FMGT PROCESSING GUIDE Page 2

REV.0
by this document’s owner or designee. The Executive Management Team is responsible to ensure their staff use
this document to create and manage governing documents by following this guideline.

5. INTRODUCTION
This document is a guide to seafloor backscatter processing using FMGeocoder Toolbox (FMGT) when MBES
processing is done in Qimera. While this instruction will provide many of the basic steps and some
troubleshooting guides necessary for the generation of a backscatter mosaic, it is not an exhaustive reference.
Some steps may need modification for different sonars or if using different file types on import.
QPS has their own online guide (“Knowledge Base”) for all their products, including FMGT which is located at this
link: https://confluence.qps.nl/fledermaus7/reference-manual/fmgt. It has detailed walk-throughs as well as a
Quick Start Guide that is very handy for FMGT basic tools and automated processing steps.
The guide that follows will outline the basic steps, as well as provide a detailed description of FMGT backscatter
processing. Sections will mention common errors and troubleshooting steps.

2023-001_FMGT PROCESSING GUIDE Page 3

REV.0
1. TABLE OF CONTENTS
1. PURPOSE.................................................................................................................................................. 2
2. ABBREVIATIONS & DEFINITIONS ........................................................................................................... 2
3. CODE, STANDARDS & REFERENCE MATERIAL ................................................................................... 2
4. ROLES & RESPONSIBILITIES ................................................................................................................. 2
5. INTRODUCTION........................................................................................................................................ 3
1. TABLE OF CONTENTS ............................................................................................................................. 4
2. Workflow Overview .................................................................................................................................... 5
3. Detailed Guide to Processing .................................................................................................................... 6
3.1 Project Setup................................................................................................................................................. 6
3.1.1 Starting FMGT .................................................................................................................................... 6
3.1.2 Create New Project ............................................................................................................................. 6
3.1.3 Processing Parameters/Settings ........................................................................................................ 7
3.2 Exporting *.GSFs from Qimera ..................................................................................................................... 9
3.3 Import Data ................................................................................................................................................. 10
3.3.1 File Type Overview ........................................................................................................................... 10
3.3.2 Import Reference Grid ...................................................................................................................... 11
3.3.3 Import Qimera *.GSF ........................................................................................................................ 12
3.3.4 Import Troubleshooting ..................................................................................................................... 13
3.3.5 Set Project Coordinate System ......................................................................................................... 14
3.4 Automatic/Manual Processing (Mosaicing) ................................................................................................. 14
3.4.1 Tiling.................................................................................................................................................. 16
3.4.2 Mosaic Troubleshooting .................................................................................................................... 17
3.5 Gain / Visual Adjustments ........................................................................................................................... 18
3.5.1 Mosaicing Parameters ...................................................................................................................... 18
3.5.2 Cascading Backscatter Normalization .............................................................................................. 20
3.5.3 Line Backscatter Adjustment (Individual Line dB) ............................................................................ 23
3.5.4 Intra-Vessel Backscatter Adjustment (Different Vessel Data) .......................................................... 24
3.5.5 Line Processing Troubleshooting (Splicing) ..................................................................................... 25
3.6 Exporting Deliverables ................................................................................................................................ 30
4. Helpful Links............................................................................................................................................. 32

2023-001_FMGT PROCESSING GUIDE Page 4

REV.0
2. WORKFLOW OVERVIEW
1) Create New Project
a. FMGT Project Name to match Qimera Project Name
b. Save to Local for Faster Processing
c. Auto-compute output coordinate system
2) Add Reference Grid (Floating Point GeoTIFF Grid)
a. DO NOT CHANGE ANY DEFAULT SETTINGS, accept default Coordinate Reference System
b. Will appear under tab Visual Objects, Grids. Leave selected to be used in processing.
3) Add Source Files (*.GSF)
a. Processing Parameters to Default
b. Geodetics to NAD83
c. Custom settings can be selected in this section (refer to section 3.3)
4) Create Tiles (If Required per Memory Allocation)
5) Automatic Processing (i.e., Mosaic/ARA/Statistics)
6) Gains/Visual Adjustments
7) Export Deliverables

2023-001_FMGT PROCESSING GUIDE Page 5

REV.0
3. DETAILED GUIDE TO PROCESSING
3.1 Project Setup
3.1.1 Starting FMGT
Ensure that a valid QPS FMGT dongle is connected to the CPU. FMGT is an additional
package to Fledermaus which must be validated. Locate and activate the FMGT software,
icon shown on left. This will prompt the main FMGT window to open. This window has five
major components: 1) main menu bar, 2) source files panel, 3) mosaic information panel, 4)
map viewer and toolbar, and 5) processing panel. Get familiar with each component and use
the online walk-throughs for more details if needed, above and beyond this POP.

3.1.2 Create New Project

Begin by navigating to File → Create Project. This will initiate the Create Project Wizard, as shown in the figure
below. Select a relevant project name (Project#, Vessel, etc.) and leave “Auto-compute output coordinate system”
checked, as shown below. FMGT will automatically save the project to the C: drive unless specified to save
elsewhere. For increased processing speed, it is best to save the project to the local disc with sufficient space and
back it up to the server after processing is completed.

2023-001_FMGT PROCESSING GUIDE Page 6

REV.0
3.1.3 Processing Parameters/Settings
Before importing data files to the project, ensure that the processing parameters are set appropriately. These
settings may vary depending on the file type or sonar used, as well as specifics of each dataset. THIS WILL
NORMALLY BE LEFT TO DEFAULT. If there are any import or processing issues that potentially require changes
to the Processing Parameters, alert the SME immediately before attempting the options below. These will be
decided upon officially by the SME/Data & Technical Managers.
Navigate to Settings > Processing Parameters > Edit Default to view what the default settings are. An alternative
option if additional settings are needed is to navigate to Settings > Add Processing Settings. The user is then asked
to enter a new settings name. Navigate back to Settings > Processing Parameters. This time the user will see the
option to edit default or edit the newly created processing settings.
Note: It is recommended to create a new processing settings option. This way the user maintains a default setting
to revert to.

2023-001_FMGT PROCESSING GUIDE Page 7

REV.0
If there is an error with the data on import or processing, the only tabs that normally require altering are Adjust
and Sonar Defaults. Unfortunately, some of these settings will require editing that can only be determined after
unsuccessful import or mosaicing.

The image above displays the Adjust tab of Processing Parameters. If there are issues related to mosaic creation,
uncheck Apply Backscatter Corrections but otherwise it should be left turned on as this will determine the *.dB
range automatically. The only other setting that should be altered from the default settings on this tab is the
Backscatter Range. This range should only be altered after attempting to make a mosaic once for the data. The
standard *.dB range is usually -70 to 10 *.dB. However, if there is an error in mosaicing it is usually due to these
values being outside of the standard range. The user has two options here: select Uncalibrated and change the
minimum and maximum range OR set a head bias so the dB falls within the calibrated range (the error message
that will appear during mosaicing will list the range and should be noted to input here). Either option will work
for mosaicing. In the case *.XYB files are a required deliverable, ensure “Keep detailed per beam ARA
information” is checked – this must be selected before creating the mosaic. Refer to section 4.5 for more
information. Leave all other settings in this tab on default and move on the Sonar Defaults.

2023-001_FMGT PROCESSING GUIDE Page 8

REV.0
The image above displays the Sonar Defaults tab of Processing Parameters. This tab should normally be set to
Automatic (Default setting). If there are issues importing the data, select Custom Defaults and the appropriate
sonar type selected: Reson T50. Be sure to select Dual Head. The settings listed in the image are an example only.
These values will need to be compared/confirmed for each project.

3.2 Exporting GSFs from Qimera

Prior to processing in FMGT, *.GSF files will need to be exported from Qimera upon the completion of MBES
processing. Exporting a *.GSF will cause Qimera to read the QPD files that are created when the raw MBES *.dB
files are imported. These QPDs contain all changes made during Qimera processing to provide a processed MBES
Backscatter file in the form of *.GSF for use in FMGT.
Once MBES processing is completed in Qimera, highlight all the Raw Sonar Files that require *.GSF exports and
either navigate to Export > Raw Sonar File > to GSF or right click and in the dropdown select Export > to GSF.
The following window will appear: *.GSF Export Options. This is where the specific systems and settings for the
*.GSF files are chosen. There should be Head 1 and Head 2 listed for the OWF Dual Head MBES system, so be sure
both Heads are checked on. Under *.GSF Options, select to Include water column picks and include raw
backscatter imagery.

2023-001_FMGT PROCESSING GUIDE Page 9

REV.0
Selecting OK will begin the *.GSF export. This can take some time depending on the number of files within the
project. These files will automatically be saved to the Qimera project’s Export folder. These will need to be saved
to the server.

3.3 Import Data

3.3.1 File Type Overview
This step begins long before FMGT is ever opened. Ensuring that the proper data logging/export is crucial for
successful processing in FMGT. For information on accurate backscatter logging procedures, review QINSy setup
manuals.
The following list is taken from the QPS FMGT Online and Offline Manuals. It provides the file types or file pairs
which can be imported into FMGT for backscatter processing, although some are only allowed in newer versions
of FMGT. Check the version to ensure the intended data pairs are accepted. Often, data must be cleaned prior to
import; it is important to know what software will be used for bathymetry processing, as this will also determine
which file types can be used.
• GSF** – GSF files that contain beam averaged or beam time series data can normally be mosaiced in
FMGT.

2023-001_FMGT PROCESSING GUIDE Page 10

REV.0
 • XTF – XTF files that contain side scan data can be mosaiced. There is minimal support for side scan
processing as FMGT's primary focus is multibeam time series or beam average data.
• DB/QPD Pair – The *.qpd file can only be paired with a raw *.dB file, this being the raw file format
recorded by QPS QINSy. QPS QINSy software receives raw sonar datagrams which are then used to
compute the sounding footprint locations. The results are stored in a QPD file, but the raw observations
are stored in the *.dB file.
• GSF/XTF Pair – Used to process Reson or R2Sonics data where the multibeam depths come from a *.GSF
file and the sonar beam time series data is stored in the *.XTF file. FMGT will create a new *.GSF file
containing both the multibeam depths and the time series data and use that in the standard *.GSF
processing flow.
• GSF/S7K Pair – Used to process Reson data where the multibeam depths come from a *.GSF file and the
sonar beam time series data is stored in the S7K file. FMGT will create a new *.GSF file containing both
the multibeam depths and the time series data and use that in the standard GSF processing flow.
• Kongsberg (.all) Files – Depending on the sensor used to collect the information, backscatter data can be
directly mosaiced from the *.all files. There is a detailed procedure for importing .ALL files into QINSy for
replay and export into FMGT that can be found on the QPS FMGT Knowledge Base.

Newer versions of FMGT will also accept HYPACK 7K/GSF, CARIS HDCS/XTF, CARIS HDCS/ALL (Kongsberg), CARIS
HDCS/S7K or CARIS HDCS/HYPACK 7K pairs. The CARIS license .DAT file path must be selected under Preferences
to be able to use HDCS data.

3.3.2 Import Reference Grid

A Reference Grid in GeoTIFF format can be added in FMGT to improve processing results. In the case of
multibeam sonar source data where corrected bathymetry is present (i.e., the fully populated *.GSF) the
Reference Grid will be used to determine topographic slope, while the corrected bathymetry in the source files
will continue to be used to geo-reference the snippet trace from a single ping to the correct spot on the seafloor
and with the correct scaling.
The reference grid should be added first, and to prevent coordinate reference system issues it is best to use a
GeoTIFF exported from Qimera. To import the reference grid, navigate to File > Add Reference Grid in FMGT.

2023-001_FMGT PROCESSING GUIDE Page 11

REV.0
As mentioned in section 2 since we are using a GeoTIFF do not change any of the default Coordinate Reference
System settings. After successful import, the Reference Grid will be visible in the Map View area. It will be listed in
the Visual Objects tab under Grids (#2 image in Section 3).

Note: Checking it off will exclude it from being used as part of processing!

3.3.3 Import Qimera *.GSF

Once the *.GSF files are created (as described in Section 2 above) and a project has been made in FMGT, navigate
to File > Add Source Files. This will initiate the Import Wizard. Select the *.GSF file type on the left-hand side of
the window, and then select Add Source File(s)… and navigate to the location of the *.GSF’s on the server.

Unless needed for troubleshooting, leave the settings on Default as shown below.

2023-001_FMGT PROCESSING GUIDE Page 12

REV.0
FMGT will run through several iterations of the screen below as it imports the selected files. When this
successfully completes, the *.GSF files will be listed in the source files window tree. The checkbox next to each file
serves a dual purpose. The first is to determine if the object is to be displayed in the map view (#4 on the image in
Section 3). The second, for source files, is to determine if the file is to be used for any selected processing. This is a
key part of FMGT's workflow. If a source is checked, it will be included in any processing. If not, it will be ignored.

3.3.4 Import Troubleshooting

On occasion, there will be errors upon import. Oftentimes the specific error that shows in the Processing
Messages will need to be sent directly to QPS for investigation (Link to Support Ticket System is provided in
Section 6).
A few options to try for initial troubleshooting include:
1. Re-export the *.GSF from Qimera. Follow Section 2 again.
2. Create custom Settings within FMGT’s Processing Parameters (See Step 5.2) and re-import the data with
the new custom setting selected (the image below from the final import stage would need to have the
setting drop down for whatever the new custom setting was named; again, see Step 5.2 for details).

2023-001_FMGT PROCESSING GUIDE Page 13

REV.0
 3. If the issue persists, it may be necessary to create a new Qimera project that only contains the *.dB’s of
the *.GSF’s that have failed to load into FMGT. Once the new project is created and the appropriate edits
have been applied, export the necessary *.GSF’s and there should be no issue importing into FMGT.

3.3.5 Set Project Coordinate System

NOTE: If a GeoTIFF was used as a reference grid, DO NOT CHANGE PROJECT COORDINATE SYSTEM – the GeoTIFF
will provide this information and any changes will cause the project to fail.

The Project Coordinate System dialog shown in the figure below allows for editing of the project coordinate
system. It is best to do this step immediately after data import, otherwise all data will need re-processing if this is
changed after processing has been carried out (Section 4.6). In this option, set the UTM zone; navigate to Settings
> Project Coordinate System…

3.4 Automatic/Manual Processing (Mosaicing)

Once the data (*.GSF and reference grid) have been successfully imported into FMGT (files shown under Source
and Visual Objects, respectively), processing and mosaicing can begin. Unless specified otherwise, automatic
processing should be used. Be sure to have all the files checked on in the source list (unless there is a reason to
exclude lines; this is normally determined after an initial mosaic is made). Before processing, be sure the settings
are appropriate for the required mosaic resolution (#3 from image in Step 3). As shown below, the pixel size
(resolution) for the resulting mosaic can be set. However, depending on the size of the backscatter project, the
memory might exceed the processing capabilities when setting the mosaic resolution. This will be shown by the
mosaic memory font turning red after a value is set. If this occurs when setting the pixel size to the project
requirement, tiling will need to occur within FMGT (Section 5.4.1).
NOTE: If working on a large project, use a higher resolution (1 or 2m) which will allow for much shorter loading
times and allow for a faster initial QC of the surface. As long as “Use Cascading Normalization Line Offsets” is
2023-001_FMGT PROCESSING GUIDE Page 14
REV.0
selected under Settings > Mosaic Parameters, changes made to intensity in Cascading tool will carry over when
creating a new mosaic with the required resolution.

The Processing Panel, as seen below, is where processing will begin. Again, unless specified otherwise, be sure
only Mosaic is checked as shown in the image below then select the Mosaic button – at which time you will be
prompted to name your mosaic.

From both the Manual Processing tab shown above and the Main Menu Processing drop-down shown below, the
individual processing steps can be accesssed and run if needed.

2023-001_FMGT PROCESSING GUIDE Page 15

REV.0
3.4.1 Tiling
If due to mosaic memory limitations, the project requires tiling, the following steps will need to be performed.
Confirm with the SME / Data & Technical Managers if there is a need to tile to verify the tiling requirements.
Navigate to the Manual Processing tab of the Processing Panel, as shown below. Here, the option for creating
Mosaic Tiles exists. Tiles can be made either by Pixel Size or by Meters. Since final deliverables will require
combining files in Global Mapper, these tiles do not necessarily need to be set to a specific value. Often, using a
pixel size of 2048 will bring the Mosaic Memory back into the green, acceptable range. Several “meter” tile
options can also be tested to see how large/small the tiles need to be to bring the Mosaic Memory to an
acceptable range.
Set the Mosaic Tile size and then select Create New. The process will run, and then the designated tiles will show
in the map view.

Once tiles exist, running the Processing/Mosaicing stage will create an individual file for each tiled area.

2023-001_FMGT PROCESSING GUIDE Page 16

REV.0
3.4.2 Mosaic Troubleshooting
A common issue encountered while creating two separate mosaics in one FMGT project (or adding individual
Source Files/ *.GSF’s not in bulk) is a limited extent. This involves a blue box denoting the extent of the first
created mosaic, limiting access of following mosaics to that area, as seen in the following image. In the image, the
crossline mosaic was created first, establishing the extents (the blue box).

Blue box/ Extents

Due to this, when the mainline *.GSF’s were added, the software still defaulted to the surface extents (the blue
square) and only created a new mosaic within that area – as seen in the first image. To resolve this issue, delete
the most recent mosaic (in this case, the cropped mosaic) and this resets the parameters in the software. Create
the desired mosaic a second time and the extents should allow the full surface to generate as seen below. It
should be noted that the associated *.GSF’s are processed when a mosaic is created, so re-creating the mosaic
will take a fraction of the time.

2023-001_FMGT PROCESSING GUIDE Page 17

REV.0
3.5 Gain / Visual Adjustments
There are several options within FMGT for improving the visual aspects of the final backscatter mosaics. A few
options are listed below. Not every project will require the same settings, so these are to be used with caution.
Ask the SME if in doubt about using/applying parameters.

3.5.1 Mosaicing Parameters

The Mosaic Parameters Dialog, shown below, is used to control mosaic generation. Any changes to these settings
will require the mosaic to be reprocessed. Access this menu by navigating to Settings > Mosaic Parameters…

2023-001_FMGT PROCESSING GUIDE Page 18

REV.0
The Line Blending option controls how multiple samples that fall within the same mosaic cell are blended.
Normally the default is 50% which is an equal contribution from both samples.
The Mosaicing Style options provide control over how pixels are blended in overlapping areas near nadir. Blend is
selected by default, where nadir pixels are blended with other overlapping pixels. Using either of the No
Nadir options provides two methods of weighting nadir pixels to reduce their effect with overlapping data from
other lines. If the survey lines do not overlap enough, these options will have no effect on the mosaic. No Nadir
if possible 10% will prioritize +-10% of the distance from nadir to the outer beam distance. No Nadir if
possible 25% will prioritize +-25% of the distance from nadir to the outer beam distance. Examples of the three
options are shown from left to right below: Blend, No Nadir 10%, No Nadir 25%.

Image from QPS

2023-001_FMGT PROCESSING GUIDE Page 19

REV.0
NOTE: Before beginning processing, it is very helpful to turn on 3σ. This will make mismatched *.dB intensities
more evident. Double click on the scroll bar below the histogram to return to the default setting.

3.5.2 Cascading Backscatter Normalization

This tool can only be run on a single mosaic (NO TILING). If it is determined that the Cascading tool is to be
used, create a single mosaic without tiles. If this cannot be done at the project resolution due to size
limitations, create a lower resolution surface (+1m) that can be made as a single mosaic. This will be the
primary tool you will use to process you mosaics.

Select the mosaic to run the normalization on, then select Tools > Cascading Backscatter Normalization. Also,
ensure the desired lines are checked on under the Source Files tab or else they will not be accessible in Cascading
Tool. Similarly, any lines not associated with the selected mosaic will not be accessible and instead grayed out.

2023-001_FMGT PROCESSING GUIDE Page 20

REV.0
All lines that contribute to the mosaic will be listed. As you move your mouse over the map, the survey line that
falls under the cursor position is listed immediately below the map, along with the color code that is used in
the Plot Color column of the table view. By double clicking on a line in the map, the Source Item will become
highlighted. The main approach will be selecting lines that are not matching the overall surface and either
increasing (to lighten) or reduce (to darken) the *.dB offsett. To identify which line you have selected, hover the
cursor over the area of interest and the name will be listed near the bottom of the window, as seen in the
following image.

2023-001_FMGT PROCESSING GUIDE Page 21

REV.0
This approach can also be used to investigate how the lines are interacting to create the surface. By running the
cursor an area of interest and watching which line is named, you can see if an issue is being created by two lines
overlapping. If this is the case, a solution is to return to the main project window and moving one of the lines
forward or back to reduce the overlapping effect. If working on a larger surface, it can save time to turn off
“Preview Change in Mosaic Immediately”. You will have to refresh the surface to see updates by clicking “Preview
Normalizaed Mosaic” but it will greatly reduce the loading time. It should be noted that none of the edits will be
applied to your working mosaic until you select OK.

NOTE: Be very cautious when putting in values; if too large a number (positive or negative) is inputted, the line
will become damaged. At this point, you will either need to exit Cascading Backscatter Normalization (losing
any edits) or need to re-import the relevant *.GSF.
You are also able to choose a reference line to normalize all other survey lines against. This should be a line free of
any artifacts and that runs the full length of the FMGT project. Left click any area on the map and the Source Item
table will scroll down to that particular line. Tick the Reference checkbox to set the selected line as a reference (or
multiple lines). These lines WON’T have an offset applied. Any unchecked lines will be processed/offset.

2023-001_FMGT PROCESSING GUIDE Page 22

REV.0
Once a reference line/lines have been chosen, click the Compute Offsets button at the bottom of the window. The
process will launch and a status bar will be shown on the bottom as the offsets are processed. Once complete,
the Offset column will be populated with *.dB offsets and the map view will update with a preview of the result.
Once complete, click Ok to apply. The mosaic that was selected to start the process will then be updated and the
*.dB offsets are saved for each line in the project folder, as long as the Save Cascading Normalization line
offsets checkbox is checked in the mosaic parameters. They are also used in any subsequent creation of new
mosaics.

3.5.3 Line Backscatter Adjustment (Individual Line dB)

NOTE: Due to Cascading Backscatter Normalization, this tool is redundant but will be left in this operating
protocol manual for reference.
The Backscatter Adjustment option allows the user to offset the processed *.dB value for the currently selected
line. This is useful if a line’s overall brightness level is different from the surrounding lines. After selecting a line,
FMGT will create a dynamic mosaic of the currently selected so that the user can interactively adjust the *.dB
offset of the selected line and see the overall effect in the mosaic. If the mosaic has been tiled, the dialog will
contain just the data for the tile that was selected at the position of the line selection. Select the line that needs
adjusting in the map view, so it is activated, then navigate to Tools > Backscatter Adjustment. If a line is not
selected in the map view, the Backscatter Adjustment option will be greyed out, as shown in the image below.

2023-001_FMGT PROCESSING GUIDE Page 23

REV.0
Simply use the Bias slider to change the offset value to apply to the line. Once the OK button is selected, FMGT
will apply the offset and refresh the currently selected mosaic.

3.5.4 Intra-Vessel Backscatter Adjustment (Different Vessel Data)

NOTE: Due to Cascading Backscatter Normalization, this tool is redundant but will be left in this operating
protocol manual for reference.
Backscatter Level Adjustment is used for matching intensity between lines with different processing settings (i.e.,
collected from different vessels). Before using this dialog, ensure that the lines selected to match are configured
to use different Processing Settings. To confirm this, right click on a line and selecting the Set Settings option.
To run the dialog, have only two lines checked in the project tree view to determine the adjustment level and
have the mosaic (or mosaic tile) selected that contains the two selected lines. This mosaic must contain data
from the two lines of interest (usually this is best done with overlapping lines), otherwise the adjustment will not
work. If the mosaic is not tiled, just select the mosaic. FMGT will then extract the backscatter data per line and
separate the lines as separate layers in the tool.

2023-001_FMGT PROCESSING GUIDE Page 24

REV.0
Once the Backscatter Level Adjustment window opens, zoom into the display using the mouse wheel or click-drag
to pan around the display. Click on the home button to zoom back out to the extents of the data. Change which
line is on top in the view by using the layer swap button.
Either line can be adjusted manually using the slider bar or the spin box. The levels will be persisted into the
configurations of both processing settings. To use one of the lines as a reference, simply click the lock button next
to the line of choice. Automatic level matching can be attempted using the Auto Match Levels button if a
reference line is chosen. Once satisfied with the adjustments, click OK to exit. This will cause FMGT to save the
offset value in the Head 1 and Head 2 Bias options of the specific Processing Settings. The data will require
complete reprocessing to implement the changes. To replace the current mosaic, simply click the Mosaic button
to proceed with processing. The resulting mosaic will have the new adjustments applied to all associated lines.
This tool should be used with caution and advisement from SME / Data & Technical Manager.

3.5.5 Line Processing Troubleshooting (Splicing)

Occasionally you will encounter a line that does not show a consistent intensity along its entirety. With these
issues, there is no single *.dB offset you can apply to make the entire line match the surface. An example can be
seen in the following image.

2023-001_FMGT PROCESSING GUIDE Page 25

REV.0
Lines with these characteristics can be managed by using a work around generally referred to as a splice. This is
accomplished by creating duplicates of the line causing issues and creating a new mosaic that has it included.
When creating the duplicate, it is best to change the name slightly to denote that it is a duplicate as seen in the
following image. A useful naming convention is to add an underscore followed by a letter denoting its iteration
(there are times multiple duplicates will be needed to resolve a surface issue). This will also prevent the duplicate
from overwriting the original when it is added to the project.

For this method, we will be deleting the portions of the original line that exhibit inconsistencies. These will then
be replaced with segments of the duplicate line which will have a different *.dB intensity applied to mask the
varying intensity in the original line. It should be noted that this process is time consuming, so first try shifting the
line back to try to conceal it with adjacent lines.
2023-001_FMGT PROCESSING GUIDE Page 26
REV.0
Once the duplicate line has been added, you will use the Edit Segment tool in the Toolbar to select the parts of
each line you want to remove. Plan for what portions of the original and duplicate line you will be removing so
you can keep you work consistent. For this example, we will first remove the two dark sections of the original line
(as seen in the image below), followed by removing the light area from the duplicate.

With Edit Segment selected, left click to start a line and right click to end the line. Once selected, click
the Cut Segment tool to remove that portion and then repeat this process for the other dark area of
the original line. Upon cutting the line there will not be a visible change if the original and duplicate
lines are set to the same intensity. Therefore it is helpful to change the intensity of one line to make it
more obvious, for example changing the original lines intensity to +10.

2023-001_FMGT PROCESSING GUIDE Page 27

REV.0
As seen in the image above, the intensity of the original line has been increased, making it more obvious which
sections have been removed. Following this, select your duplicate line and repeat the cutting process but this time
for the light area so that the original and duplicate will not overlap. Once complete, you can apply different *.dB
intensities to the original and duplicate in Cascading Backscatter Normalization to mask the issue. While it may
not fully resolve the issue, it will make the line look far more consistent along its length. It should be noted that
sometimes it will require multiple duplicates to address these types of issues.

2023-001_FMGT PROCESSING GUIDE Page 28

REV.0
As it can become confusing to keep track of which lines you are manipulating, it is useful to only have the lines of
interest turned on under Source Files so that when you open Cascading Backscatter the list of lines will only be
those relevant.

If you accidently remove too much line or need to start over, you will repeat the process with the Edit
Segment tool but select the Add Segment instead of Cut Segment. You will be able to see this is the
issue if you can see the Reference Grid.

2023-001_FMGT PROCESSING GUIDE Page 29

REV.0
3.6 Exporting Deliverables
As with other sensors, exports should NOT live within the project. This causes the projects to often be 100+ GB
larger than they need to be and cause additional headaches when trying to copy to and from the server.
The Export sub-menu provides a way to export your mosaic tiles to another format.
To export ASCII Processed Backscatter files, “Keep data for processed backscatter export” must have been
checked under Processing Parameters as discussed in section 3.3 before creating the surface mosaic. Following
this, ensure all source files that are required for export are checked on (those that are not, will not be exported).
To export all desired source files simultaneously, right click on “Source” on the Source Files tab, select “Export”
and then “ASCII Processed backscatter..” as seen below. Following this, a window will prompt you to select the
folder destination.

2023-001_FMGT PROCESSING GUIDE Page 30

REV.0
The most common exports will be XYZ and Floating Point GeoTIFF Grid which will be under the Surface dropdown.
These can be accessed by navigating to the Visual Objects tab, right clicking on your desired mosaic, Export >
Surface >XYZ/GeoTIFF.
The mosaic can be exported in several other formats under the Surface drop down including:
• ASCII Z
• ArcView ASCII Grid, or
• Raw binary grid
• NetCDF/GMT Grid
• QPS GRD3
The other options under the Export dropdown include:
The Grayscale Geo TIFF option exports the mosaic as a single plane GeoTIFF file. If multiple tiles have been used in
the mosaic creation multiple GeoTiffs will be created representing each tile.
The Color Geo TIFF option exports a color version of the mosaic. If multiple tiles have been used in the mosaic
creation multiple GeoTiffs will be created representing each tile.
The One Merged Grayscale Geo Tiff option exports a multi tiled mosaic as a single plane GeoTIFF.
The One Merged Color Geo TIFF option exports a multi tiled mosaic as a single coloured GeoTIFF.
The One Merged Floating Point Geo TIFF option exports a multi tiled as a single 32bit floating point GeoTIFF.

2023-001_FMGT PROCESSING GUIDE Page 31

REV.0
4. HELPFUL LINKS
1) Introduction to FMGeocoder Toolbox (FMGT): https://confluence.qps.nl/fledermaus7/reference-
manual/fmgt
2) QPS Support Desk: https://confluence.qps.nl/sup/support-desk-64916760.html
3) QPS Support Ticket System: https://jira.qps.nl/secure/Dashboard.jspa

2023-001_FMGT PROCESSING GUIDE Page 32

REV.0