Matt wrote:
.......but there is one important caveat: boundary points outside of the rectangular extent defined by the existing track-points will not be included in the finished map. This is because the initial gridding of the data is done to a grid size defined by the track-point data.
Matt, couldn't a person create a .csv track with '4 corners' around the lake, to import as a track? Would that create an 'outer rectangular extent for the finished map'? That way the initial gridding of the data is done to a grid size defined by the '4 corners' of the imported .csv track, and therefore all the defined depth 'boundaries' would be included?
Just curious. I might try it at some point to create rough depth maps from Google Earth georeferenced lake contour maps downloaded from my state DNR website.