I am have difficultly in correcting depths using the Correct Depths feature.

In the example I have attached, you can see an old river bed that I would like to correct but the control via the mouse is very intermittent and does not move the depth point very far, up or down.

Should I be able to move the point horizontally as well as vertically?

Your thoughts are appreciated,

thanks.

Mark.

The current way this works is that you can only move the depths of existing data points - not the position. New data points are generally added to a track every time the position changes in the sonar log file, so sometimes you will get larger gaps like this that cannot be made to fit perfectly with the bottom. On the one hand, we should/could probably move to interpolating extra points along a track, although this would come at a cost of extra data points. The flip side to that is that these points are very likely so close together that adding extra depth resolution here probably wouldn't make any difference to the resolution of a map project, although it could help somewhat with slant range correction in sidescan mosaic. It is something we are looking at improving as part of the RM2 release cycle (along with automatic depth detection) but at the moment you probably have the depths as good as you are going to get in that example.

Yes, I have the same problem, very difficult to correct depth value.

Is the issue here that the depth points are spaced too far apart to follow the contours of the bottom precisely (as in the original post), or is there something else going on?
The v2 correct depths functionality is basically the same as v1, in that you can only move existing data points up or down - you can't move them laterally within the SV. The actual redrawing code in v2 is (should be) much faster and more reliable than v1, but the original restriction remains. I can only repeat what I said in my previous reply, which is that any terrain that is changing at a rate faster than new data points are being added (usually about a metre) is probably too detailed to be reflected in any map produced from the track so as long as the depth points follow the bottom fairly closely you should be OK.

V2 is much improved over V1 in this regard!

Its better - or at least faster - but we do need to address the issue of completely missing data points and it is something that is on the radar. When automatic edge detection is ready, we'll probably create a completely new set of points interpolated over distance and depth at some sort of regular distance spacing along the track, and perhaps even completely discard (or have the option of discarding) the extant data points.

Matt wrote:
That would be awesome!

Matt wrote:
Is there any news on this feature?

igorsd wrote:
It is still happening but I can't give an update as to when. Unfortunately, for a variety of reasons (resourcing, mainly) the development of some of these new features is taking a lot longer than anticipated. It will be part of the 2.x cycle.