SketchUp Sandbox Contours: A Practical Workflow

A terrain model can look convincing while being useless for design decisions. If its levels are guessed, its scale is unclear, or its mesh is too dense to edit, it will not help with a retaining wall, accessible route, drainage fall or building setting-out. SketchUp Sandbox contours are useful because they turn surveyed elevation lines into editable site geometry - provided the input contours are clean and correctly located.

SketchUp's Sandbox tools are deliberately simple. They do not replace a civil grading package or repair unreliable source data. What they do provide is a quick, visual way to build a triangulated irregular network from contour lines, inspect the ground against a proposal and make controlled local edits. The quality of that terrain is decided before you select the first Sandbox command.

What SketchUp Sandbox Contours Actually Create

The Sandbox From Contours tool generates a terrain mesh by triangulating between selected contour edges at different elevations. Each contour must be a continuous line or polyline sitting at its correct Z height. SketchUp then reads the relationship between those lines and creates faces across the site.

This is not the same as importing a flat drawing of contour lines and expecting the tool to infer levels from labels. Text such as “102.50” has no geometric meaning to Sandbox. The contour geometry itself must be elevated. A contour labelled 102.50 m needs to sit at Z = 102.50 m, or at the corresponding local project elevation if you have deliberately shifted the model origin.

That distinction matters on real projects. A visually tidy plan can contain broken polylines, duplicate segments, crossing contours and lines that all sit at Z = 0. Sandbox can still produce a mesh in some cases, but the resulting triangles may fold, bridge across gaps or create false ridges. Treat the contour drawing as data, not merely linework.

Start With the Right Terrain Source

For early massing, a broad contour interval may be enough. For an entrance threshold, stepped landscape, drainage route or coordination with a civil engineer's levels, it usually is not. Choose source elevation data and point spacing around the decision you need to make.

Official mapping, LiDAR and photogrammetry datasets all have different strengths. LiDAR can describe existing ground well where coverage and resolution are appropriate, but it may include vegetation or structures unless it has been classified as ground data. Survey data can be more suitable for detailed interfaces, although it may cover only a limited area. A 1 m contour interval is useful for a neighbourhood-scale feasibility model; it may hide the gradient that determines whether a path is compliant.

It is also worth defining a boundary that extends beyond the proposed building footprint. Terrain should include enough surrounding ground to show how water, access and retaining conditions connect to the wider site. At the same time, do not download an entire district for a small plot. Oversized terrain makes SketchUp slow without adding useful design information.

A platform such as Topo-grapher helps remove the GIS step by generating clean, real-world-coordinate XYZ points for a drawn site boundary. The practical point is not the file format alone. It is receiving elevation data that can be controlled, filtered and converted into the terrain workflow your team actually uses.

Prepare Contours Before Using From Contours

Sandbox works best when the contour network is simple, continuous and purposeful. Before generating the mesh, inspect the linework in plan and in a side view. You are looking for topology problems, not graphic polish.

First, make each contour a single connected polyline where possible. Use View > Hidden Geometry if edges appear fragmented. A contour can include many segments, but endpoints need to meet exactly. Tiny gaps often arise during CAD export, particularly where contours were clipped to a boundary.

Second, confirm that contours do not cross except where the source is genuinely invalid. Ground contours should normally close or run cleanly through the site boundary without intersecting. Crossovers tell Sandbox that two different elevations occupy the same location, which produces unstable triangles.

Third, remove duplicate edges and irrelevant annotations. Copying a CAD layer into SketchUp can leave coincident linework that is difficult to spot. It can also introduce spot-level leaders, hatches, kerbs and building outlines that should not become part of the terrain input. Place the contours on their own tag and keep a separate reference group for the original survey drawing.

Finally, check vertical units. If the source is in metres but the SketchUp model is set to millimetres, the geometry can still be mathematically correct, but a missed conversion may produce a terrain one thousand times too large or too small. Use the Tape Measure tool on a known distance and inspect a known elevation in a side view before proceeding.

Working from XYZ points

An XYZ file is a point dataset, not a contour drawing, so it cannot go directly into From Contours without a conversion stage. Import the points through a compatible SketchUp extension or a script that preserves X, Y and Z values, then create contour polylines using a terrain or CAD workflow suited to the project. Alternatively, generate a triangulated terrain mesh directly from the points if that is the chosen extension workflow.

For a Sandbox contour workflow, export or create DXF contour polylines at defined elevations. Keep the contour interval explicit in the file name and model notes. This avoids a common coordination error where a team member assumes 0.5 m contours are 1 m contours and reads the slopes incorrectly.

Generate the Terrain Mesh

Select only the elevated contour edges. Do not select text, dimensions, boundary lines or the original survey group. Then choose Tools > Sandbox > From Contours. SketchUp will create a new triangulated surface above or between the selected lines.

The first result should be treated as a diagnostic, not an approved terrain model. Orbit underneath it and inspect for vertical spikes, long triangles spanning missing areas, holes, or faces that reverse direction unexpectedly. Switch to View > Face Style > Monochrome to make reversed faces easier to see. If large areas fail, repair the contours rather than attempting to patch every bad triangle by hand.

Where the source contours end at a site boundary, Sandbox may pull a mesh across the open edge in a way that is visually awkward. It depends on the shape of the boundary and the spacing of the last contours. A clean approach is to retain a slightly larger terrain extent, then crop the generated terrain with a separately modelled site boundary. Do not force the terrain to follow an arbitrary property line if that line cuts across the natural ground in a misleading way.

Group the completed terrain immediately. A Sandbox mesh contains many individual triangular faces, and leaving it loose makes accidental edits likely. Name the group clearly, such as `Existing Ground_1m_Contours_2026-09`, and place it on an existing-ground tag.

Edit Sparingly and Keep Existing Ground Intact

The Smoove tool is useful for quick studies: select the terrain, choose Tools > Sandbox > Smoove, set an influence radius and pull local vertices up or down. It can help test a platform, shallow swale or local regrading idea. It is not a substitute for calculated earthworks or drainage design.

Keep a locked copy of the original existing-ground mesh before using Smoove. Then duplicate it for proposed terrain. This makes cut-and-fill discussions clearer and stops concept edits overwriting the record of what the source data showed.

Avoid smoothing every facet simply because the terrain looks angular. A triangulated mesh will always reveal facets at close range, particularly with coarse contour intervals. Excessive smoothing can disguise sharp changes in grade and create an attractive but less truthful model. For presentation, use materials, shadows and carefully chosen scenes. For design review, expose the mesh and show spot levels or section cuts.

Check Levels Where Decisions Happen

A terrain mesh is only valuable when it can be checked against design geometry. Add guide points or short vertical reference lines at building corners, finished-floor levels, road tie-ins, accessible routes, drainage outlets and retaining walls. Use Tools > Section Plane to cut through those locations, then verify the proposed relationship to existing ground.

Pay particular attention to coordinate handling. Large real-world coordinates can reduce display and modelling precision in SketchUp. Many teams model near a local origin while retaining a documented relationship to survey coordinates. That is sensible, but only if the offset, units, northing and elevation datum are recorded and applied consistently across CAD, BIM and civil files.

If the terrain is being exchanged with another discipline, state what it represents: existing ground or proposed ground, source date, coordinate reference, vertical datum, contour interval or point spacing, and any filtering applied. A clean model without that context can still be misused.

Good SketchUp terrain is not the mesh with the most triangles. It is the one that makes the next site decision easier to see, question and coordinate before that decision becomes expensive to change.