Skip to end of metadata
Go to start of metadata

When using applications such as FMGT, the expectation is that the source data has been processed to a high level for positioning, roll, pitch, heave and latency offsets and vertical offsets in the data and also velocity profiles. However sometimes the data that one is endeavouring to produce mosaics from and do Angle Range Analysis may still have unresolved issues, artifacts or lack of post processing for tides or sound speed for the particular survey or survey area.


Qimera comes into its own in this situation both to diagnose and identify the issues or artifacts and to resolve them, by the application of relevant files or information to the source files; for instance the correct or better suited sound velocity profile or the correct offset for timing or pitch for example.


In FMGT timing or offsets, incorrect sound velocity profile negatively impacts the data which produces bathymetry that is very poor. This makes FMGT's job impossible as it needs 'good' bathymetry data to produce realistic angle range analysis.


Cleaning up the bathymetry data, running a patch test to find the offsets and applying a more representative sound velocity profile to the data will produce better results from FMGT.

Figure 1. Qimera showing a Dynamic Surface, Swath Editor Tool and a Cross profile through data with potential offset and sound velocity profile issues. 

 

Qimera functions very effectively as a post processing software which can apply and correct motion, offset and velocity (sound speed) issues. At present FMGT is not part of the actual package it will be in future.
For the current workflow for Qimera to FMGT this article may be of use: https://confluence.qps.nl/display/KBE/Howto+Qimera+-+Migrate+a+Qimera+Project+to+FMGT
There is a very useful Knowledge Base for Qimera here: https://confluence.qps.nl/display/KBE/Qimera+Knowledge+Basehttps://confluence.qps.nl/display/KBE/Qimera+Knowledge+Base

 

There is no content with the specified labels