Most drainage arguments on a job site start the same way: someone points at a low spot and says water goes there. Maybe they are right. Maybe the low spot is a canopy crown, a temporary stockpile, or a roof edge that looks like ground from the air. Drone drainage analysis only earns its keep when the surface under the analysis is bare earth and the workflow treats that surface like evidence, not decoration.
This guide is opinionated on purpose. Fly and process for a digital terrain model first. Run water-flow analysis from that DTM. Use the Slope, percent, Drainage lines, Ponding, and Catchments layers to brief the client. Hand stamped hydrology and engineered design to the people licensed to own them. If you reverse that order, you will ship pretty maps that route water over trees.
Why a DTM, not a DSM, for drainage
A digital surface model (DSM) includes everything the camera sees: roofs, walls, canopy, cars, equipment. A digital terrain model (DTM) is bare earth. Water on a real site does not flow across treetops. If you run flow tools on a DSM, the software will happily treat canopy as terrain and send the "drainage lines" wherever the tops of the trees happen to sit.
That is not a software quirk. It is physics meeting the wrong input. Meaningful drone drainage analysis needs a bare-earth surface. Build or export the DTM first, then analyze. For how DSM and DTM surfaces get produced on your own desktop, start with DSM and DTM generation on your desktop. Contours from those surfaces are the other half of the elevation foundation; see contours from a local DSM or DTM when you need labeled lines for the same site.
SkyView Desktop delivers both DSM and DTM as live processing outputs, and contours can be generated from any elevation surface in the project (DTM, DSM, or an imported surface). Use the DTM for flow. Use contours as the readable summary for people who will never open a GIS viewer.
What water-flow analysis actually produces
In SkyView Desktop, water flow analysis is part of the Survey & Earthworks add-on, and it runs against a bare-earth DTM. It is not a separate product called "Flow Direction" or "Watershed." Those names show up as layers and results of the analysis, not as standalone tool categories you buy or toggle on their own.
Select the DTM, press Run water flow analysis, and you get four layers that answer the questions clients actually ask:
- Slope, percent — the grade at every cell, showing where the ground steepens and where it flattens.
- Drainage lines — the channels water gathers into as it moves downhill, with each line's order and length.
- Ponding — depressions past your depth and area thresholds, with the deepest point, area, and volume each one holds.
- Catchments — the ground that drains to each channel, with its area.
On top of the layers, two click tools matter in the field meeting: Trace flow path from a click shows where water goes downhill from any point, and Outline watershed from a click outlines everything uphill that drains through it. That is how you turn a map into a conversation instead of a PDF nobody opens.
Know the limits before you brief anyone. SkyView's water flow analysis shows the shape of the ground. It does not model pipes, storm drains, rainfall, or soil, and it does not replace engineered runoff, culvert, or grading design. Drainage lines, Ponding, Catchments, and the two click tools are the whole story.
Buildings: run Planimetrics first
Bare earth alone is not enough when the site has buildings. Water does not flow through a warehouse slab. A DTM removes the building, so without footprints flow can cut straight across where it sits.
When the project has a Planimetrics run, SkyView puts buildings and retaining walls back so water routes around them. One hard opinion: on any built site, run Planimetrics before you analyze flow. Water that routes through a building footprint is not a deliverable anyone should defend. On a bare grading pad with nothing built yet, the terrain alone is the right question. Note in the report whether Planimetrics ran so next month's run uses the same rule.
A practical flight-to-flow workflow
Skip the magic-button fantasy. Drainage work is a sequence.
- Fly for terrain, not just pretty ortho. Overlap, altitude, and timing still matter. Shadows, standing water, and tall crops punch holes in the surface. Note them.
- Process locally into ortho, point cloud, DSM, and DTM. SkyView Desktop runs that stack on your own Windows hardware with no per-map cloud processing fee — that is our claim and our model, not a jab at anyone else's price sheet.
- Confirm the DTM looks like ground. Spot-check against known hardscape, ditches, and pads. If canopy or vehicles are still sitting in the "terrain," fix classification or editing before you analyze flow.
- Run Planimetrics so buildings exist as features the flow tools can respect.
- Run water flow analysis on the DTM (Survey & Earthworks add-on).
- Read the layers with the client: Slope, percent, Drainage lines, Ponding, and Catchments, then use Trace flow path from a click and Outline watershed from a click on the hot spots.
- Export what the next person needs — often contours plus screenshots or GIS-ready layers — and keep the talk in the report honest about what the surface can and cannot prove.
If the client wants labeled contours for the same pad, generate them from the DTM you already trust. Contours are live in SkyView from any elevation surface in the project; they summarize the same elevation story the flow tools are reading.
Where this helps — and where it stops
Use drone drainage analysis to show patterns: where sheet flow concentrates, where a pad is likely to pond after a storm, which upslope area feeds a ditch the client cares about. That is decision support for contractors, landowners, and pilots who need a clear picture before the next grade change.
Do not use it as a substitute for a licensed surveyor or civil engineer. SkyView does not certify survey-grade accuracy. Surface error and occlusion can displace features. Professional licensing rules and measured accuracy sit outside the software. The tool analyzes the surface you give it; it does not stamp hydrology, certify faults, or prove compliance with a stormwater design standard.
Say that out loud in the proposal. Clients who hear the limit early stay clients. Clients who hear it after a dispute do not.
Common mistakes that wreck the result
- Analyzing the DSM "because it looks sharper." Sharp roofs are not drainage. Use the DTM.
- Skipping Planimetrics on a built site. Flow through a building is a modeling error, not a site feature.
- Running Planimetrics on one visit and skipping it the next and then arguing that "drainage changed." Method change is not hydrology change.
- Promising engineered design from a photogrammetry surface. Pattern recognition is not stamped design.
- Ignoring holes and noise from water, glare, or vegetation. Bad surface in, confident nonsense out.
Fix the input. Re-run. Compare. That loop beats another hour of arguing about a pretty but wrong map.
SkyView as the front door, Pilot Ledger for the job
SkyView Desktop is the processing front door: RGB photos in, ortho and photo-based 3D out, DSM and DTM as live deliverables, contours from the elevation surfaces you keep in the project, and water flow analysis (Survey & Earthworks add-on) that turns a bare-earth DTM into Slope, percent, Drainage lines, Ponding, and Catchments layers you can walk a client through.
The second beat is short on purpose. Once the map is done, quoting the drainage review flight, scheduling the re-fly after grade, and getting paid still live in the same Pilot Ledger account. Processing without a per-map cloud fee only helps if the rest of the job also closes.
SkyView is available now. Process on your hardware, deliver the surfaces and the flow layers, and keep the engineering stamp where it belongs.
What to put in the client report
- Flight date, altitude, overlap, and the GSD you actually flew.
- Which surface fed the analysis (DTM), and confirmation it is bare earth.
- Whether Planimetrics ran, so buildings and retaining walls were respected.
- Screens or exports of Slope, percent, Drainage lines, Ponding, and Catchments for the outlets that matter.
- A plain-language limit: patterns from the modeled surface, not survey-grade or engineering certification.
- Next step — re-fly after grade, hand off to the engineer, or both.
If a follow-up question pops up after publish day — entitlement details, a workflow edge case, or whether a feature sits in a given plan — ask Ask Mav on pilotledger.com. Product facts change; Ask Mav is the live check.
Bottom line: drone drainage analysis is only as honest as the DTM underneath it. Build the bare-earth surface, respect buildings, run the water-flow layers, and refuse to oversell the stamp. When you are ready to process and deliver that stack from your own computer, see SkyView and Pilot Ledger plans.