Qimera Match QPD Process

Qimera - Match QPD Process

This process is only done on QINSy (.db) files.  During metadata extraction of the Qinsy raw sonar file, Qimera will attempt to find the associated QPD file for the line.  Every QPD in a Qimera project will ultimately appear in the project ~/DtmData/VesselName folder where VesselName is the name of the vessel for the specific loaded raw sonar file. In order to successfully match a line with it's associated QPD, the base name, (the part of the filename after the directory declaration and before the extension)  must be the same as the raw sonar file base name.

Opening Qinsy Projects

Qimera will first look in the  ~/DtmData/VesselName  folder of that project for the QPD.  If a match is found, the matching process stores the value in the project XML and exits.  If the match is not found, Qimera will then look in the root project ~/DtmData folder.  When a match is found, the file will be moved to the ~/DtmData/VesselName folder for that project. The path is then stored in the XML and the matching process will exit.  When a match is not found, the raw sonar file will display as requiring processing in the tree view by the

Importing Qinsy DB Files

If you have created a new project and are importing .db files into your project from another folder, Qimera will look  in the Qinsy project's ~/DtmData/VesselName folder for a matching QPD.  If a match is found in the  ~/DtmData/VesselName folder, the file is copied to the local project ~/DtmData/VesselName folder. If a match is not found, Qimera will look in the root folder ~/DtmData of the QINSy project. If the match is found in the root folder  ~/DtmData of the QINSy project, the file will be copied to the local project folder ~/DtmData/VesselName. In either scenario, the path is then stored in the XML and the matching process will exit. 

Note, if the output coordinate system of an imported QINSy file is not the same as the Qimera project, Qimera will deem this a match failure.  If a match is not found due to differing coordinate systems, the raw sonar file will display as requiring processing in the tree view by the

Multi-Vessel DB files

If a DB / QPD pair contains data from more than one supported vessel (also called objects or vehicles), the following steps will take place:

1) When the file is imported, the source files will be split so each vessel has its own source file in the Project Sources dock.

2) For each vessel that has supported systems, a subfolder in the DtmData directory will be created.

3) If a QPD is matched, as in the Importing Qinsy DB Files section above, it will be copied into the appropriate DtmData subfolders. Vessels that do not contain supported systems will not have a QPD copied into the vessel's subfolder.

4) Each copy of the QPD will be compared to the vessel it is linked to. If the QPD contains griddable systems (MBES, Singlebeam, Laser, Pipetracker) that are not associated with its vessel, those systems will be removed. This results in the QPD only containing griddable systems that are associated with the linked vessel.

5) If systems are removed from a QPD, a backup is created first.

Return to: Dynamic Workflow

Return to: Qimera Table of Contents