Generate contours: boundary, interval and smoothing
Draw a field boundary so contours stay in the field, pick the contour interval and smoothing, check the estimate and tap Generate. What the Many contours warning means, why Generate greys out, how to edit or clear the boundary afterwards, and what the map shows.
- Full Automation Kit
- Guidance Only Kit
- Ditch Assist Lite
In the app Levee › (elevation source) › Contour Settings › Generate
Once the app has an elevation surface, it needs two things from you: where the field is (a boundary) and how far apart in height the contours should be (the interval). Then it traces the contours and draws them on the map.
Before you start
- Elevation data loaded on the Levee screen (Get elevation data)
- Connected to your kit, or Simulate on, so Generate can run
Time: 2–5 minutes; generating a big field can take a minute more.
The field boundary
A boundary clips the contours to the field: no lines running along roads, ditches, yards or the neighbour's ground, and less for the tablet to work out.
- Saved LiDAR DEM: uses the boundary you drew in LiDAR & Mapping. No question asked.
- GeoTIFF, saved survey, new survey: the app asks
Define field boundary?
with Skip (use full extent) or Draw Boundary. When it can trace an outline around your points it may offer that instead (Boundary traced (N pts)
, Use this boundary).
Tap Draw Boundary
It's the right-hand button in the Define field boundary?
window. The window closes and the map is ready for you to tap corners. Skip (use full extent) on the left goes straight to Contour Settings with no boundary.
1
2- Draw Boundary. Tap it.
- Skip (use full extent). No boundary; contours over the whole surface.
Tap each corner of the field
Tap the map at one corner of the field, then go round the edge tapping each corner in turn. An orange line joins them up, and the top button in the right-hand column counts the corners: Done (4 pts). Tapped in the wrong place? Undo, just under it, takes the last corner off.
1
- The outline. Four corners tapped round the field.
- Done (4 pts) and Undo. The count goes up with each corner; Undo takes the last one off.
Keep it simple: an outline that crosses itself is refused (Polygon edges cross. Adjust your boundary.
). Undo back to the bad corner and go round the other way. To zoom or move the map, pinch or drag with two fingers (pinch to zoom).
Tap Done
Tap Done (4 pts) at the top of the right-hand column (it needs at least three corners). The outline turns cyan and Contour Settings opens. Cancel, under Undo, throws the corners away and stops drawing.
- Done (4 pts). Tap it to finish the outline.
- Cancel. Stops drawing; no boundary.
Contour Settings
Check the top line
Under the Contour Settings title: the size of the surface and its elevation range. The range is worked out as if the elevations were metres: right for a Saved LiDAR DEM, about three times high for a GeoTIFF or point file in feet. Tapping Meters or Feet doesn't change it.
- DEM / Elev range. Size and height range of the surface.
Tap an interval
The interval is the height from one contour to the next. Tap one of the chips under Contour Interval; the one you pick turns green. A smaller interval gives more lines, closer together: pick it to suit how tightly you need to hold elevation. 3″ is picked to start.
1
2- Interval chips. 1″, 2″, 3″, 6″, 1 ft.
- 3″. Picked to start (green).
In metric the chips read 25, 50, 75, 150 and 300 mm; with decimal feet 0.08, 0.17, 0.25, 0.5 and 1 ft (the same heights).
Or type your own in Custom
For a size that isn't on a chip, tap the Custom box under the chips and type the number (typing); here 36 inches. A GeoTIFF or point file also shows Source units under it: tap what the file really is, Meters or Feet (why it matters).
1
2- Custom. 36 typed: a 36-inch interval.
- Source units. Only for a GeoTIFF or point file; Meters picked here.
Set the smoothing
Drag the dot on the Smoothing slider: right for more, left for less. It has nine steps from None to Max, with the name shown on the right; Medium to start. More smoothing rounds off bumps from rough or sparse data but loses small detail; less keeps detail but can give jagged lines.
1
- The slider. Drag the dot.
- Medium. The current setting.
Check the estimate, then tap Generate
The grey box shows about how many contours you'll get. Over 200 it turns amber with Many contours — consider a larger interval.
Over 500 it turns red and Generate greys out until you pick a larger interval. When it's fine, tap Generate at the bottom right: Generating contours...
runs, longer for big fields.
- Estimated contours. About 122 lines: fine.
- Generate. Tap it.
The estimate is a guide. The count on the map can come out higher, because a contour broken into pieces counts each piece.
What you get on the map
The contours are drawn coloured by elevation, blue for low ground to red for high, inside the boundary. The app picks the contour nearest you straight away and starts the lightbar (Follow a contour), and saves the job under a dated name ("Levee" and the date and time).
- Tap a contour to start guidance. Shown when none is picked.
- Counters. Coverage runs ("levees") and contours.
- The right-hand column. Select Nearest picks the line closest to you; Edit Boundary and Clear Boundary change the outline; Save names the job; Clear All clears the screen (no confirmation).
Edit or clear the boundary later
- Edit Boundary turns the outline orange with its corners, so you can tap more corners or Undo; Done (N pts) regenerates the contours inside the new outline.
- Clear Boundary removes it and regenerates the contours over the whole surface.
- Edit Boundary / Clear Boundary. Change the outline any time; the contours redraw.
If something goes wrong
- Generate is grey: over 500 contours estimated for the interval. Raise the interval, and check Source units is what the file really is. Fix too many contours.
- Nothing drawn: the surface is too flat or sparse for that interval. Fix no contours drawn.
- Jagged, wiggly lines: more smoothing. Fix jagged contours.
- Boundary refused: Fix a refused boundary.
- Generate refused outright: Generating needs a controller.
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.