Rhino 3D Tip: Creating Accurate Terrain Surfaces from Elevation Contours in Rhino

Turn elevation contours into a useful terrain surface with Rhino’s Patch command. The key is preparing reliable 3D curves, then balancing surface flexibility against the accuracy your project requires.

Start with clean, correctly positioned contours.

• Confirm units: Check the document units before importing survey data. A mismatch between meters, feet, and millimeters can invalidate the entire site model.
• Verify elevations: Inspect contours in Front or Right view. Each contour should lie at its intended Z elevation, not simply carry an elevation label while remaining flat at Z=0.
• Clean the curves: Use SelDup to locate duplicates and Check to identify invalid geometry. Join segments where appropriate, but do not connect separate contours simply because they share an elevation.
• Protect the source: Keep original survey contours on a locked reference layer and work with copies.

Build a controlled first surface.

Select the elevation curves and run Patch. Rhino fits a surface to sampled locations along the input geometry. Begin with moderate settings and preview the result before increasing complexity.

• Surface spans: Increasing U and V spans gives the surface more freedom to follow terrain changes. Excessive spans can introduce ripples, increase file size, and make subsequent editing harder.
• Stiffness: Higher values resist deformation and generally produce a smoother, less responsive surface. Lower values allow closer fitting but may exaggerate irregularities in the input.
• Point spacing: Smaller spacing samples curves more densely. Use enough detail to capture meaningful changes without oversampling noisy survey linework.

Change one setting at a time. This makes it easier to distinguish a genuinely better fit from a surface that merely looks smoother in a shaded viewport.

Trim only after checking the fit.

Do not assume the outermost elevation contour represents the property boundary. A terrain surface and a site boundary serve different purposes. Keep a separate boundary curve, and use it to trim the accepted surface. If the boundary is planar, project it onto the terrain in the intended direction before trimming.

Validate against the survey, not just the viewport.

• Run Contour on the resulting surface using the same elevation interval and matching elevation levels as the original data.
• Compare the generated contours with the source curves in Top view. Noticeable shifts indicate areas that need adjustment.
• Inspect sections through steep slopes, ridges, and drainage channels. Smooth shading can conceal flattened crests or artificial depressions.
• Check surface edges carefully; terrain beyond the available contours is extrapolated and should not be treated as surveyed ground.

Know when Patch is not enough. Patch is an approximation, not a guarantee that every contour will be matched exactly. For engineering workflows requiring enforced breaklines or a triangulated terrain model, use an appropriate terrain-modeling workflow rather than forcing a single smooth surface to do everything.

For Rhino software and additional workflow resources, visit NOVEDGE and explore the NOVEDGE blog. Preserve your source contours alongside the finished terrain so future revisions remain traceable.

You can find all the Rhino products on the NOVEDGE web site at this page.