Welcome, Guest
Username: Password: Remember me

TOPIC: Custom Path Depth

Custom Path Depth 10 years 7 months ago #6637

  • dbuss
  • dbuss's Avatar
  • Offline
I am trying to fill some holes in my map by creating custom paths in the user map, exporting to csv, then importing as an asset. Currently I have to populate the depth column in the exported csv.

How do I get the Depth column editable while creating/editing custom paths? Exporting the paths just gives a list of points and I can not distinguish between different paths I have created.

Thanks
The administrator has disabled public write access.

Custom Path Depth 10 years 7 months ago #6683

  • Matt
  • Matt's Avatar
  • Offline
Custom paths don't have a depth attribute, so I'm afraid it is not possible to add spot depths in this way.
The way I would recommend doing this (although it is a bit of a pain), is to add "boundaries" to your map:

1. Add a new map boundary, and deselect the "Is Boundary" check box. This will create a "boundary" that doesn't actually act as a boundary.
2. Make sure "Provides depth" is selected, and enter the spot depth that you require.
3. Deselect "show in map", so that the boundary is not included in the generated contour map.

Setting up a "boundary" in this way will provide depth values during the map generation process, 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.

We are adding a built-in spot depth mechanism which will make this process much easier.
The administrator has disabled public write access.

Custom Path Depth 10 years 4 months ago #7009

  • CamoHunter
  • CamoHunter's Avatar
  • Offline
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.
The administrator has disabled public write access.
SCROLL TO TOP