A new update is available with the following changes:

Features:

• Curve and speed filters restored for sidescan mosaics (note - hardware graphics support required).
• Water column offset added for sidescan segments which can be used to hide any remaining water column in the centre of the swath (note - hardware graphics support required).
• Bounds meta-data added to MBTiles exports for better compatibility with ARCGis.
• Depths are now included for waypoints created within the Sonar Viewer window.
• Added show all and hide all waypoint set buttons.
• Active waypoint set is now updated to last edited/added waypoint, making adding multiple waypoints to a particular waypoint set much faster.
• Separate menu bars added for track sidescan and selected segments within sidescan mosaics.

Fixes:

• Better checking for DirectX compatibility.
• Import of hardness values via CSV fixed - all values go to single PSV layer.
• Fixed issue with bad range values being stored for some sidescan mosaic tracks.
• Fixed crash in palette editor when editing min/max depth values with no palette selected.
• Fixed issue with boundaries controls not showing correctly without first being resized in project properties panel.

To update, use the Check for Updates menu item in the FILE menu and follow the prompts/

Hello Matt.
Thank you for the work done!
When you have the chance to add points with a depth value and stones from the shape files?
Very need to create a vector map.

NMEA does not work with non-standard headers
I can not connect to the equipment (FURUNO navNet vx2), drdepth and others without problems!
I sent you NMEA Log that it's hard to make out?

So there is no important!
The editor of the measurement in the form of a graph
Filtering depth soundings at a predetermined distance
Export depth soundings

3D multibeam data from SL3 will?

[3D multibeam data from SL3 will?[/quote]

It will be milestone in mapping......I'm dream about. How long it takes? Months, years?

Thanks Matt - the side scan water column feature worked well, does this affect GPS locations at all , ie fo underwater tree positions change when i hide the black holes from the water column

skinnee wrote:
Lateral offsets for objects in sidescan are calculated using simple trigonometry so yes, the positions will change slightly as the depth underneath the boat is changed. As an example, something showing at a raw sonar range of 20m will be shown 19.36 from the boat at a depth of 5m and 19.22m from the boat at a depth of 5.5m. So the change is relatively small, especially at higher ranges (and a 0.5m adjustment is quite a large one). You need to remember though that all sidescan offsets are approximations, and all rely on the (often/usually false) assumption that the surrounding terrain is flat, with the same depth as directly underneath the boat. In this context, changing the depth slightly to remove the water column is not going to reduce the overall quality of sidescan mosaics and should in fact improve them given that visible water column is an indication of a recorded depth that doesn't match the recorded sonar exactly.

Hi Matt

one question about water column and Sidescan Mosaic:
do you agree that in Moasic is better to remove the water column offset automatically made by RM? And therefore "fill" the swath with an overlapping track scan?