Most bad contour maps are not software failures. They are interval failures. Someone picks the tightest spacing the tool will draw, the lines look impressively detailed, and the client walks away believing the ground is known to a precision nobody ever measured. That is the real risk in contour interval drone mapping: not ugly lines, but confident lines that the source data cannot back up.
This guide explains what a contour interval is, how it differs from the horizontal spacing you see on the map, how scale and units change the choice, and why the quality of the elevation surface should set the floor. The one, two and five foot examples below are illustrations of the trade-off, not targets any drone survey is guaranteed to support.
What is a contour interval?
A contour line joins points of equal elevation. The contour interval is the vertical difference between neighboring lines. The U.S. Geological Survey puts it plainly in its Topographic Map Symbols guide (checked 10 Nov 2026): "The elevation difference between adjacent contour lines, called the contour interval, is selected to best show the general shape of the terrain." The same page notes that each contour is a line of equal elevation, so contours never cross, that wider index contours carry printed elevation values, and that the interval is printed in the margin of every USGS map.
Two phrases in that definition matter more than people give them credit for. "Selected" means the interval is a decision, not a default. "General shape of the terrain" means contours are a way to communicate landform, not a substitute for the elevation data underneath them.
Vertical interval versus horizontal spacing
The interval is fixed. The distance between lines on the map is not. With a constant vertical interval, the horizontal gap between contours changes with the slope of the ground. The USGS guide describes the visual rule: lines that are close together mean steep ground, while widely spaced lines, or no lines at all, mean the ground is relatively level.
A little arithmetic shows why this matters for drone sites. On a uniform 2 percent grade, the ground rises one foot every 50 feet, so one-foot contours land about 50 feet apart. On a 10 percent grade, the same one-foot interval puts lines about 10 feet apart. On a 50 percent embankment, they are 2 feet apart and start to merge into a brown smear. One interval can be too sparse on a flat parking lot and too crowded on the slope next to it.
That is the first test of any interval: does it produce readable horizontal spacing on the slopes your client actually cares about, at the scale they will actually view?
Contour interval drone mapping: one, two and five foot spacing compared
Think of these three as illustrative choices on the same imaginary site, not as outputs a particular project will support.
- One foot. Shows subtle grade changes on gentle ground such as pads, lots and fields. It also shows every bump in the surface, real or not. On flat ground it can be the only interval that reveals anything, but it is also the interval most likely to draw noise as terrain. Use it only when you can explain why the elevation surface deserves it.
- Two foot. A middle ground for many mixed sites. Gentle slopes still get some lines, steep sections stay legible, and small surface artifacts are less likely to become closed loops. If you are unsure, this is often a more honest starting point than one foot.
- Five foot. Built for rolling or steep ground and wider areas viewed at smaller scales. It hides minor grade changes, which is a feature when those changes are smaller than what the data can resolve, and a flaw when the client needs to see drainage on a nearly flat lot.
Our bias: start coarser and tighten only with a reason. A map that understates detail invites a follow-up question. A map that overstates detail invites a decision nobody should make from it.
Map scale changes the right answer
An interval that reads well on a zoomed-in screen can collapse on a printed sheet. The horizontal spacing you calculated above shrinks with the map scale. If a client will review contours as a printed overview of the whole property, a tight interval on steep ground becomes a solid band of ink. If they will zoom into a single pad in a GIS viewer, the same interval may be perfectly readable.
Ask how the deliverable will be used before you choose. Overview, design discussion and progress reporting are different jobs. It is fine to deliver more than one set of contours for different views, as long as each set is clearly labeled.
Units: say what the lines mean
A contour labeled "2" is meaningless without a unit and a reference. Feet and meters are not interchangeable shorthand. A half-meter interval is roughly 1.64 feet, which is neither a one-foot map nor a two-foot map. Pick the unit your client works in, keep it consistent between the elevation surface and the contours, and state it in the legend along with the vertical reference the elevations use. If you are not sure what that reference is, sort that out before you label anything. Our guide to DSM versus DTM in drone mapping is a useful companion here, because the surface type belongs in that legend too.
Source-data uncertainty sets the floor
Contours do not create information. They redraw whatever elevation surface they come from, at whatever spacing you ask for. If the surface is uncertain, contours drawn closer together than that uncertainty are mostly a picture of the uncertainty.
Common sources of trouble on drone sites:
- The wrong surface. A surface model that includes rooftops, vehicles, stockpile equipment and tree canopy will put contours around all of them. If the question is about the ground, contours from a surface that includes everything on top of it will mislead.
- Vegetation and water. Tall grass, brush and reflective or moving water make elevations harder to pin down. Contours through those areas deserve less trust than contours over bare, textured ground.
- Edges and gaps. Elevation near the edge of the flight area, or in spots with thin image coverage, tends to be weaker. Clip or flag those areas instead of letting lines wander off the edge.
- Ground resolution. Pixel size is not vertical certainty, but coarse imagery limits how much fine detail the surface can hold in the first place. Our explainer on ground sampling distance (GSD) for drone mapping covers how flight height and camera choice set that baseline.
The honest move is simple. If you can describe how well the elevations were checked, choose an interval that respects that check. If you cannot, choose a coarser interval and say in the notes that the contours show general landform, which is exactly what the USGS definition says they are for.
A quick checklist before you deliver contours
- Confirm which surface the contours came from and whether it matches the client's question.
- Check horizontal spacing on the flattest and steepest areas at the scale the client will use.
- State the interval, unit and vertical reference in the legend.
- Label index contours so a reader can find elevations without counting lines.
- Mask or flag vegetation, water, edges and weak coverage.
- Add a plain note that the contours are not a survey and that design decisions need a licensed professional.
For a product-side discussion of building contours from a local surface model, see our earlier post on contours and local DSMs. The interval decision in this guide applies no matter which software draws the lines.
Where Pilot Ledger fits
Interval choice is a scoping conversation, so it belongs in the quote. Pilot Ledger keeps quotes, jobs and invoicing in one account, which makes it easier to write down what the client asked for and what the deliverable is meant to show. SkyView Desktop turns RGB drone photos into orthomosaics on a Windows computer with no per-map processing fee, then delivers results to clients through Pilot Ledger.
If that workflow fits your business, compare Pilot Ledger plans.