Additional i used "slope" tool to the natural neighbor raster. It's looks a bit like a fake thermal picture.

And now natural neighbor blue/green/yellow/red & 70 % opacity slope in black/white. And there is much more options ...

Matt, can you tell me if the Garmin .RSD log format will be supported? I know a guy on Facebook named HummSucker can read echograms in this format without the Garmin SDK.

This is a tricky one Pavel. We could release support for Garmin tomorrow as we also have the format (and an in-house implementation), but the format is proprietary. We have had some communications with Garmin and it might be possible - I really hope so - but ultimately it will come down to whether or not they allow us to use it. Yes, I do understand EU rights around using one's own data etc. but no tiny company wants to get into a fight with a big one, so we wouldn't do it without permission.

Could you please tell me what model of fish finder and what model of transducer is receiving this data? I just bought a Garmin Panoptix PS70 hoping to get similar data.

Matt, Thanks for the reply. Let's hope the guys at Garmin will be accommodating.

PavelP wrote: Data what? Multibeam sonar- no, Quickdraw contours not utylized more than single track from ps30, so I'm not suppose that PS70 is any better for mapping

The PS70 uses MBES for QD plotting, just like its Furuno DFF3D counterpart. These are essentially Airmar sensors.
But none of the professional hydrographic programs have supported the PS70. Either Garmin hasn't approved it, or the product isn't designed for mapping.

Baikal38 wrote:
Is QD converter extract MBES data from PS70?

iceperch wrote:
Yes, in a highly interpolated form with fictitious depths

RM3 Feature Requests

1. Device Connections
1.1 Working with virtual COM ports
1.2 Communication with devices via Ethernet TCP/IP, UDP, and port. (Lowrance SIMRAD has the ability to transmit NMEA 0183 data via Wi-Fi or through NMEA2000-WiFi gateways.)
1.3 Connecting more than one depth source
1.4 Creating a boat model with sensor offset assignments
1.5 Working with HDT compass data

2. Real-time data collection
2.1 Simplified visualization of real-time bathymetry, similar to DrDepth
2.1 Simple text display of sensor readings without compass cards or other graphic elements.
2.3 Survey Line generation based on shoreline coverage, including interline distance and heading angle parameters.

3. Editing
3.1 Lasso-style depth mark selection
3.2 Undo/Redo commands for all RM operations
3.3 Crop by SHP polygon object boundaries
3.4 Exporting project depth mark logs
3.5 Assigning water levels to a group of objects or selected objects
3.6 Filtering logs by speed
3.7 Filtering logs by sharp depth drops
3.8 Filtering logs by thinning by a specified radius
3.9 Filter preview
3.10 Displaying depth marks in digital form with color shading by height; display variations must be enabled in the parameters.

4. Interpolation
4.1 Intermediate simplified preview mode for fast rendering and display of bathymetry during editing.
4.2 Ability to define a map by SHP polygon object boundaries
4.3 Arbitrary generation of isobath cross-sections, i.e. For example, the sequence (0.5 1 2 3 4 5 10 50 100) is specified. Creating Custom Contour Profile Presets with Names

5. Profile Tool
- Creating profiles along an arbitrary path with points or a loaded SHP line
- Saving profiles with names
- Displaying the nearest GRID-based depth marks of the log on the profile for comparison and accuracy analysis
- Generating a profile image in graphic format
- Generating XYZ profile points in text or SHP format

6. Depth Mark Generation Tool
- Generating depth mark points based on GRID data, placing points along a specified radius and vertical level within a depth range.
For example, the user can specify depths with a radius of 50 m in the depth range from 10 m to 20 m, and with a radius of 100 m for areas deeper than 20 m (i.e., from 20 to ∞). Adding new ranges on a new line.
1. range 10-20 radius 50
2. range 20-∞ radius 100
- The tool should generate depths in shallow areas to show whether the area is deeper or shallower than the surrounding contour (like bumps or pits). For this, the minimum size of such areas is specified.

Thanks Baikal, that's quite a comprehensive list!
It seems you are quite into the live mapping - we do need to do a lot of work on this area, although my perception was that it wasn't used by most. It's not a top prioroty for the first v3 release but will see what time permits. Certainly there will be improvements.

Much of 3/4/5 are already in the plans. You'll need to describe 6 to me in a bit more detail - I am not quite following the requirement.

thanks,
Matt