Before you start
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 › Before you start
Three things before you generate contours or follow them:
A connection to the control module, or the simulator running. Contours and guidance are part of the Ditch Assist guidance kit. The WiFi indicator in the stats bar should be green, or you should be in Simulate. See Getting Started for the connection sequence. Surveying a field and importing data work with a Bluetooth GNSS receiver too — only the contour generation and following steps need the module.
A high-accuracy GPS lock. The GPS Accuracy badge should read RTK Fixed (green) for both surveying and following. At Low and Mid RTK Sensitivity settings the app does not force a hold on RTK Float (yellow) while following, but Float is not endorsed — continuing on it is at your own risk. At High sensitivity, Float counts as accuracy-lost and triggers the auto-hold banner. Surveys still drop non-RTK points when the RTK Filter is on regardless of sensitivity.
Your units set the way you want to work. Everything in this mode — contour interval, elevations, swath widths, the lightbar scale — shows in the units you picked under Settings → UNITS → Measurement System. Set this before you start so the numbers read the way you expect.
About benchmarks
If you are surveying a field by driving it, the app requires you to drop at least one benchmark before it will record points. A benchmark marks a fixed spot you can return to (a gate corner, a post) with an averaged elevation, so a future session can line back up even if the RTK base station has moved. Benchmarks are covered in Calibration & benchmarks in this section.
If you are importing a file or downloading LiDAR, no benchmark is needed — the elevations come from the data.
Did this answer your question?
Thanks. That tells us which pages to improve.
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.