FW09 — Topographic Survey and Contour Map Preparation

Learning Objectives

  • Establish or verify survey control for a topographic detail survey.
  • Collect sufficient spot elevations and coded detail points to represent terrain and site features.
  • Identify and observe terrain breaklines rather than relying only on uniformly spaced points.
  • Reduce and organize coordinate/elevation data into a traceable point file.
  • Prepare a complete engineering topographic map with spot elevations, contours, breaklines, scale, north reference, legend, and control information.
  • Perform independent checks before leaving the site and document the coordinate reference used.

Topographic Surveying Is Controlled Sampling of the Ground Surface

A topographic survey does not attempt to measure every point on the site. Instead, the survey team observes enough well-distributed points, terrain changes, and physical features to reproduce the shape of the ground accurately. Points at ridges, drainage paths, tops and toes of slopes, pavement edges, curbs, building corners, and other discontinuities are more important than simply collecting a large number of random points.

Required Equipment and Records

Field Equipment

Record Before Detail Collection

Survey Control and Coordinate Reference

Control First, Details Second

Detail points are meaningful only when they are tied to reliable horizontal and vertical control. Before collecting terrain points, verify the occupied station, backsight orientation, benchmark/elevation reference, and coordinate system. If classroom coordinates are assumed, label them explicitly as an assumed local coordinate system.

Do Not Present Assumed Coordinates as Geodetic Coordinates

Local coordinates such as N = 1000.000 m and E = 1000.000 m are valid for a classroom exercise when clearly declared. They must not be described as GNSS, cadastral, PRS92, UTM, or other geodetic coordinates unless the survey is actually tied to that system.

Point Coding and Terrain Breaklines

Recommended Coding Logic

Use short, consistent codes that identify what each point represents. Typical examples include GRD for ordinary ground, EP for edge of pavement, TC for top of curb, INV for drain invert, BLDG for building corner, TOE for toe of slope, TOP for top of slope, and CL for centerline. The same code must not mean different features within one survey.

Breaklines Must Be Deliberately Observed

Collect points along abrupt changes in terrain slope and along linear features that control the surface shape. A dense cloud of random points cannot reliably replace a missing ridge, ditch, curb, retaining wall, or top/toe-of-slope breakline.

Field Procedure

Topographic Detail Survey

  1. Reconnoiter the assigned area and identify control, access limits, pedestrian routes, hazards, and important terrain features.
  2. Establish or verify the assigned occupied station and backsight.
  3. Record all setup metadata before collecting detail points.
  4. Take an initial check observation to a known control point or benchmark when available.
  5. Collect spot elevations over ordinary terrain at a density sufficient to represent the surface.
  6. Increase point density wherever slope, curvature, or feature complexity changes rapidly.
  7. Collect dedicated points along breaklines such as pavement edges, ditches, ridges, tops/toes of slopes, walls, and building outlines.
  8. Use consistent point IDs and codes. Do not renumber points after the field record is complete without documenting the change.
  9. Before leaving the site, perform at least one independent control/check observation and review the point list for missing areas or duplicated/wrong codes.
  10. Export or transcribe the raw observations and preserve the original electronic job file when one is produced.

Contour Interpolation

Linear Contour Interpolation

Locates a contour elevation between two surveyed points when linear interpolation is appropriate.

f=Zc−Z1Z2−Z1f=\frac{Z_c-Z_1}{Z_2-Z_1}d=fLd=fL

where ZcZ_c is the contour elevation, Z1Z_1 and Z2Z_2 are the bounding point elevations, LL is the plan distance between them, and dd is the distance from the first point toward the second point.

Contour Behavior Checks

Contours of different elevations do not normally cross. Closely spaced contours indicate steeper ground; widely spaced contours indicate gentler ground. Contours should respond to breaklines and drainage/ridge geometry rather than be smoothed blindly through them.

Required Topographic Map Elements

Finished Map

Field QA/QC Before Leaving

Topographic Survey Quality Check

Point Density Is Terrain-Dependent

The instructor may assign a minimum number or spacing of detail points. Regardless of the minimum, the team must increase observation density where terrain or site features require it. Meeting a numeric point count does not compensate for poor coverage.

Submission Timing

Fieldwork Data is due within the scheduled 3-hour class period. Submit the raw point/observation record, control information, field notes, and required electronic export within that class period. The Full Fieldwork Report, including the final topographic map and discussion, is due on the next class meeting. FW00 remains authoritative for naming, safety, data integrity, and submission requirements.

FW09 — Required Data Tabulation

Use this structure as the minimum field or research data table. Add columns when the activity requires more detail.

Point IDCodeNorthingEastingElevationFeature / breaklineDescription / QA note
CP-01CTRLRecordRecordRecordControlKnown/check point
P-001GRNDRecordRecordRecordGroundSpot elevation
P-002EDGERecordRecordRecordBreaklinePavement / curb / slope break

Use unique point IDs and consistent point codes. Control/check observations should remain identifiable separately from detail points.

FW09 — Grading Rubric

Award points according to the evidence shown for each criterion.

Total: 25 pts
CriterionFull-credit evidencePoints
Control, setup, and field procedureControl reference, setup metadata, orientation, point coding, and site safety are correctly established.5
Topographic detail dataSufficient spot elevations, breaklines, feature points, codes, and descriptions are complete and traceable.5
Topographic map and contoursCoordinates/elevations are plotted correctly; contours are interpolated consistently; map includes scale, north, legend, control, and relevant site features.7
Control checks and terrain QA/QCControl/check observations are verified and contour/terrain behavior agrees with measured elevations and breaklines.4
Report and presentation qualityRaw data, processed point table, map, assumptions, metadata, and engineering interpretation are clear and organized.4
Total25 / 25

Scoring guide: full credit for complete, technically correct, traceable evidence; reduce proportionally for minor errors, incomplete work, or weak documentation.

Key Takeaways
  • Reliable topographic mapping begins with verified horizontal and vertical control.
  • Terrain breaklines are intentional survey observations, not drafting decorations.
  • Every mapped feature and contour must remain traceable to the field dataset.
  • Control checks and coverage review must be completed before leaving the site.