
Ditch
One main through the lows to your outlet, feeders from the flow routes, every run fitted to your grade and cut limits.
Ditch and tile design for farmers and contractors
See where the water sits, lay out the ditches and tile, check every run against your limits, send the lines to your machine or drainage controller.

How it goes




See it
Ditch and tile each have their own ribbon of tools, numbered in the order you use them. These are real screens.

One main through the lows to your outlet, feeders from the flow routes, every run fitted to your grade and cut limits.

Best fit, pinned points or freeform bottom. Minimum grade is a hard floor; too deep is marked, never hidden.

Click a ditch and see it as it will be dug: bottom width, side slopes to the ground and the cut, at the spot under your mouse on the profile.

Photo, elevation, hillshade, soils, yield, flow lines, ponding, wetness index: one box, a switch and a strength slider each.

T1, T1-SM1, T1-SM1-L2. Statistics for the run, a grade label per stretch, a red band where a limit is missed.

Surface and tile defaults, pipe sizes and perforation, named profiles. Never lowered or raised by the program on its own.

Bring your own drone LiDAR map, or the elevation model your drone software makes. One pass at a time the field fills in; when the flight is done you design on it like on the public LiDAR, inside your field boundary.

Turn the field in 3D with the ponding, the flow and every line on it, heights exaggerated so the low runs stand out.
Features
One program, no spreadsheets, no files to shuttle between tools.
The LiDAR is pit-filled and routed. You see every trickle or only the main channels, the ponds at your cutoff, and the depressions by depth.
Ditches follow the natural low line. Every bend is a true arc at your turn radius. Preferred cut zero, maximum one foot; anything deeper is a review item.
Sketch a corridor and DDD finds the low route inside it, or keep the line exactly where you drew it. Click, drag, right-click to finish, like a CAD tool.
One system per marked outlet. Fill an area with long parallel laterals to the lowest line, each block in its own direction, with collectors to the outlet.
Laterals 3 ft, submains 3.5, mains 4, never over your maximum. A branch joins its main from above, the way a tee is cut in the field.
Drained width from the runs beside each lateral, every stretch of a main at its own grade, roughness by pipe size, always rounded up. The card says which stretch set the size.
Import your yield maps from Operations Center (the yield ZIP or shapefile export) or any yield CSV. The wet spots show on the map as a layer with a strength slider and tell the design where the water sits, so the tile and ditches go where the yield says they are needed.
Public aerial photo, soils, contours, hillshade, coverage and your yield, each with its own switch and strength slider. Bring a picture or an old plan of the field too (JPG, PNG or BMP, with or without a world file, placed on the map), import lines from KML, GeoJSON, shapefile, CSV or a drainage package, and save the finished map back as a georeferenced JPG.
Carve the ditch plan into the ground and rebuild the map: how many acres the ditches drain, and what is left for a tributary, an inlet or tile.
Affected acres, cut and fill in cubic yards, a pipe schedule by size, overburden where a run must go deeper than the plow. Print it or save a PDF.
We design it; your drainage controller controls to it. Checked runs export as KML, GeoJSON, CSV, a guidance setup file for the display, a drainage package ZIP, a georeferenced JPG map, the profile PDF and the project file. Every major drainage controller reads one of these. Runs that fail a limit are never sent.
How it works
Pick it from your field list or draw the outline on the map. DDD fetches the public LiDAR, or takes your own drone LiDAR flight, and builds the terrain and the drainage map.
Mark the outlet, create the ditches or lay the tile, set the run length with the slider, fix anything the review list flags.
Export in the file your drainage controller reads (KML, GeoJSON, CSV, guidance setup file, drainage package, JPG map, PDF), or send the lines straight to Operations Center as auto-steer guidance. Survey with RTK before you dig; the LiDAR plan is the start, not the survey.


Rules it never breaks
Get DDD
Current version 1.4.0 · fixes are numbered 1.2.2 and so on, new features 1.3, 1.4.
DDD runs installed on your Windows PC, the demo too. Nothing runs in the browser and there is no account to make.
One installer. Updates come from inside the program (Help → Check for update).
Download opens at launch. Tell us the county and the acres you drain and we let you know first.
Keep it handy
One tap puts the DDD icon on your home screen or desktop, so the site and your downloads open like an app.
Works on iPhone, iPad, Android, Windows and Mac. It is a shortcut to this website, your downloads and news. The design program itself runs on Windows 10 / 11.
What's new
Every numbered update is listed here. The same notes are in the program under Help → What's new.
Pricing
The demo has every tool and one export. After that, a licence lets the plan leave DDD: files, pictures, PDFs and guidance lines for your machine.
Prices coming soon (US dollars). A licence key is typed once into the program and checked on your computer. The demo and the licence live in the installed program; after the key is in, DDD needs no internet.
FAQ
A Windows 10 or 11 PC. DDD installs from one file and runs on its own: no other program, no server, no account. Internet is used to fetch the public LiDAR and updates; the licence key is checked on your PC, so a licensed DDD works offline.
Public USGS 3DEP LiDAR, 1 m where it exists. Design on it, then survey with RTK when the job goes ahead. DDD says so on every design.
Yes. Import the flight as a LAS or LAZ point cloud, or the elevation model (GeoTIFF) your drone software makes, exported in WGS 84 / UTM. Ground points already classified are used as they are; otherwise DDD picks the ground itself and removes the crop and bushes.
Yes. DDD writes KML, GeoJSON, CSV, a guidance setup file for the display, a drainage package ZIP, a georeferenced JPG map, the profile PDF and its own project file. Every major drainage controller and display reads one of these. Lines you already have come in the same way, get rounded for auto-steer and go back out.
No. Fields, LiDAR, yield and plans are read and kept on your computer. Only the lines you choose to export leave the program.
DDD designs it; you control to it. The export carries the line and the designed bottom: grade of every stretch, depth at every point, pipe size. Your drainage controller on an RTK receiver loads the line and runs the grade as the plough or scraper works; all the major controllers read one of the files DDD writes. An RTK survey of the route before installation is recommended.
It designs the plan: routes, bottoms and pipe sizes within your limits, as the start for the RTK survey and the installation. It never claims a plan is installation ready.
Help → Check for update in the program. It fetches the new build, shows what changed, and installs when you say so.
Try it on your own field
Download it, install it, and the 7-day demo starts on its own.