I have a bathymetry DEM which I want to display in 3D (ArcScene or Fledermaus). The data set is one single raster but looks like it is a mosaic of several smaller datasets. The problem is the absolute height values between these sub-sets varies and is quite prominent: resulting in the cliff like features in the below picture.
I want to 'correct' each of the subsets to create a more smooth and realistic scene. I'm not bothered by the accuracy of the depths, this is just a relative correction for visualisation.
Originally I had hoped we had the individual sub-sets as separate raster and I was going to start from the largest sub-set raster, take an adjoining raster and add or takeaway the mean difference in the heights along their adjoining edge. Maybe looking a bit at the difference in error from one side of the edge to the other. For an indication the bin size is 100m and depths only change by 1-3m between cells within a sub-set. Between sub-sets the difference is 30-100m.
Keeping his idea in mind, I then tried to separate the sub-sets back out ('un-mosaic'). Manually digitising will work but it's a lot of manual labour - too much to justify doing. Picking out the edge has to be quite precise because if I am a cell out on either side the cliff edges will still be there.
I have been trying to find more automated ways of doing this and tried a lot of edge finding filters (3x3 and 5x5 using various values) and sharpening techniques although my experience of working with rasters in this way is quite limited. It sort of worked but wasn't too great and the edge it would pick out was 2-3 pixels wide.
I then just tried all of the hydrology tools (ArcMap) and slope as I thought they might help pick out these sharp contacts. That worked like the above filtering but gave better results when I used the 'Drop' raster from the 'Flow Direction' tool. See below:
This isn't perfect but I thought I could use this, convert to polylines, manually digitise the missed parts, convert to polygons and then clip each sub-set. I'm not even sure that this would work but converting to polylines gives me the below issue. Using the simplify lines check box just made the geoprocessing run for almost 24 hours before I cancelled it.
Any ideas where to go from here?