How to Create Contours from Survey Points

A compact field-to-office checklist

Before you share a contour result, record five facts: the source filename, the coordinate-system information, the units, the contour interval, and the checks you performed. Note any areas where the point spacing is too wide to support a confident interpretation. If a reviewer asks why a contour bends or stops, you should be able to trace the answer back to the observations rather than to a hidden setting.

For repeat work, use the same order every time: preserve the source, map fields, inspect coverage, generate, compare 2D and 3D views, validate the export, and archive the review note. This sequence is useful for surveyors, civil designers, and small teams because it separates data questions from presentation questions. It also makes a later update easier when new points arrive or a coordinate-system assumption changes. See the TopoAssist features overview for the available review tools.

What you need before you begin

Collect the original point file, the field or control notes that explain its columns, and the coordinate-system information supplied with the survey. A simple checklist prevents many misleading contour results: confirm which column contains the point identifier, which columns contain horizontal coordinates, and which value is elevation. Also note whether the file uses a local grid, projected coordinates, or geographic coordinates. Keep a copy of the untouched source so every later decision can be compared with the field record.

Contours are an interpretation of sampled elevations. They do not add information between observations, and they can look plausible even when a point has the wrong unit, sign, or coordinate order. Start the process as a data review, not as a drawing exercise.

Step-by-step contour workflow

1. Inspect the file and map its fields

Upload the supported survey point file to the TopoAssist browser workspace. Check the preview for blank rows, duplicate identifiers, text in numeric columns, and elevations that are obviously outside the project range. Select the correct coordinate-system information and verify that eastings and northings have not been swapped. If the file contains several point classes, identify whether breaklines or boundaries are represented; do not assume a generic point set describes every edge condition.

2. Check coverage and elevation patterns

Use the 2D point view to look at the overall footprint. Look for large holes, isolated points, a narrow strip where you expected a site, or a cloud that appears mirrored. Review several known elevations against the field notes. A few minutes spent checking the pattern is usually faster than explaining an incorrect contour plot later.

3. Generate and inspect the surface

Generate the contour result from the reviewed points, then open the related TIN surface view. In 2D, inspect contour spacing, sharp turns, closed loops, and the site boundary. In 3D, rotate the surface to look for spikes, pits, folded edges, or a broad tilt that suggests a coordinate or datum issue. These views are complementary: the plan view helps with location, while the surface view makes elevation discontinuities easier to spot.

4. Review interval and presentation choices

Choose a contour interval that matches the size and relief of the site and the purpose of the handoff. A very small interval can create dense lines that obscure the pattern; a very large interval can hide useful changes. Keep the interval decision documented with the source file and coordinate-system choice. If the result will be used by another team, include a short note describing what was checked and what remains to be verified.

5. Prepare the next output

When the point pattern and surface look reasonable, prepare the supported output needed by the next workflow. Depending on current access, this may include a DXF, PDF, KML/KMZ, or LandXML result. Open the exported file in the receiving workflow and compare its extent, units, and a few known points with the browser preview.

Common mistakes and practical fixes

• Wrong coordinate order: a mirrored or rotated footprint is a strong warning. Recheck field mapping before regenerating.
• Mixed units: a surface with an implausible vertical scale often comes from feet/metres confusion. Confirm the source convention and downstream expectation.
• Duplicate or stale points: repeated shots can create tight, distracting triangles. Compare identifiers and survey dates before deciding what to keep.
• Ignoring sparse coverage: broad triangles across an empty area are not evidence of real terrain detail. Flag the gap for a professional decision.
• Skipping the exported-file check: a preview can look right while a downstream import interprets units differently. Reopen the actual output.

Limitations and verification note

TopoAssist can make the import, contour, and surface-review sequence easier to inspect in one browser workspace, but the result remains dependent on the supplied observations, coordinate-system information, and any assumptions made during preparation. It does not infer missing field evidence or certify a survey. Use the workflow as a technical aid, retain the original data, and apply the level of professional verification required for the project.

Start with dependable point data

Confirm that elevations, point placement, and coordinate-system information match the job before generating a result. A contour is only as useful as its input data, so investigate gaps, duplicates, or unexpected values early.

TopoAssist imports supported survey point files into a browser workspace, where you can generate contours and inspect the associated TIN surface in 2D and 3D views.

A practical sequence

Keep review in the workflow

FAQ

Continue learning

Read the survey points to contours workflow, review TopoAssist features, or check current pricing and access.