Learning Center

Tips & gotchas

Levee & Contour Guidance chapter of the Ditch Assist app manual. The same text is in the app under Manual.

In the app Manual › Levee & Contour Guidance › Tips & gotchas

The blade is never automatic in this mode. Levee and Field Survey guidance only show you where the line is — you steer and you control the blade. If you want the blade to move on its own, use Ditching, Simple Grading, Forming, or Leveling instead.

Steer toward the arrows. The single thing to remember: the lightbar lights the side you drifted to, the arrows point the way back. Follow the arrows and the lightbar center goes green.

A module or the simulator is required to generate or follow. Surveying and importing work on a Bluetooth receiver, but the contour lines will not draw and guidance will not start without the Ditch Assist module connected (or Simulate running). The app will tell you if you try.

Cover the field evenly when surveying. The surface is only as good as the data. Drive the field back and forth with even spacing, and capture low spots and edges with Log Point Here.

Pick the right interval. A smaller contour interval gives you more lines to follow but a busier map. For levee work, match the interval to how finely you need to hold elevation.

Get the source units right. When importing a GeoTIFF or point file, choosing feet when the file is in meters (or the reverse) makes the contour spacing wrong by a factor of three. If your contours look far too close together or too far apart, re-import and check the units.

Keep boundaries simple. Draw boundary corners around the field edge without crossing lines. A self-crossing outline is rejected.

Save the job. Coverage and contours are only kept if the job is saved — and it auto-saves once contours generate, so you rarely lose work, but tap Save Job to give it a memorable name.

Did this answer your question?

Still stuck? Talk to a product specialist. 1-833-DITCH-AS · support@ditchassist.com · Monday to Friday, 8 a.m.–5 p.m. Central.

Calling about a problem? Send your app logs first so support can see what happened.