Hi,

I have a few presets for equipment profiles and they have different values for forward/aft correction. However, I just noticed that in track properties the information about transducer shows the same aft correction for all my imported tracks. I checked the database and indeed column "transducer_forward_aft_cm" in the table "track_import_details" has value 300 in all the rows. That is correct value for one equipment profile but not for the rest. When I select the profiles from the user interface it shows correct values for the aft correction.

Can I trust that the aft correction is still applied correctly during the import and the error is only in the metadata?
My Reefmaster version is 2.0.32.

I would like to repeat my question. In the ReefMaster2 database all rows in the track_import_details has identical attribute values for transducer_forward_aft_cm even I have prepared two presets for imports, one having "0" as forward-aft correction value, another having the value "300".

id track_id transducer_forward_aft_cm transducer_port_starboard_cm water_type water_temperature speed_of_sound use_headings track_point_interval import_time idx_file_location reefmaster_import_version
4 167 300.000000 0.000000 Fresh 15.000000 1465.190000 0 1 2017-06-12 22:52:42Z 2.0.32.0
5 168 300.000000 0.000000 Fresh 15.000000 1465.190000 0 1 2017-06-12 22:53:12Z 2.0.32.0
6 169 300.000000 0.000000 Fresh 15.000000 1465.190000 0 1 2017-06-12 22:53:22Z 2.0.32.0

For example I have imported track_id=168 with the preset that is using transducer_forward_aft_cm=0 but I can see that the value that is stored into the database is "300". Are the trackpoints still imported as they should? In not, how could I correct the import? Would it help to update the value of "transducer_forward_aft_cm" directly with SQL?

There was a bug that (fixed in 2.0.3) that sometimes resulted in the wrong import profile being used when tracks were imported, if this profile was selected from the back-stage import tab (i.e. if the profile wasn't set as the default in global settings). If the value stored (and displayed in properties) is wrong, then the wrong offset has been applied to the track.Offsets are applied and stored when the track is imported, and the details are retained purely for information - updating the contents of the workspace db directly won't fix this. Unfortunately you will need to re-import the tracks that have been incorrectly imported.

I should update the advice above to say that I was referring to track-point positions used for bathymetric mapping - these are modified on import according to the specified transducer offset.
For Sidescan Mosaic, the transducer offset is picked up from the database and used when locating the sidescan image. So updating the workspace database will have an effect for sidescan, but will not have an effect on the location of individual track-points shown in the track and project windows.Because of this inconsistency, I would caution against simply updating the db but if you are only using the tracks for sidescan mosaic, then it may be acceptable as a quick fix. The right solution remains re-importing the tracks with the correct offsets applied everywhere.