RW03 — Route Distance and Elevation Profile Using Google Earth

Learning Objectives

  • Trace an assigned or proposed route using Google Earth.
  • Determine route length and interpret the elevation profile along the path.
  • Identify significant high, low, steep, and potentially earthwork-sensitive portions.

Activity Scope

Create a path between defined points, record total route distance, inspect the elevation profile, identify starting/ending/high/low elevations, describe major grade changes, and prepare an annotated route map plus a concise engineering interpretation of terrain implications.

Submission Requirement

Research Work is due on the next class meeting and is handwritten. Required route maps and elevation-profile screenshots may be printed and attached.

Placeholder Status

Route-selection constraints, station interval, gradient calculations, screenshot format, and grading criteria will be expanded later.

RW03 — Required Data Tabulation

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

Station / sampleDistance from startElevationΔElevationGrade (%)Terrain / route note
0+0000Record——Start point
0+100100 m or sampled distanceRecordComputeComputeTerrain note
…ContinueRecordComputeComputeHigh/low/steep segment

Include route start/end coordinates, total traced distance, highest and lowest elevations, and the Google Earth elevation-profile screenshot/printout.

RW03 — Grading Rubric

Award points according to the evidence shown for each criterion.

Total: 20 pts
CriterionFull-credit evidencePoints
Route selection and digital traceRoute is clearly defined, reproducible, and traced accurately between documented endpoints.5
Distance and elevation dataTotal distance, sample/station elevations, high/low points, and profile data are complete and correctly tabulated.4
Grade and profile analysisElevation differences, representative grades, steep segments, and profile interpretation are mathematically and technically sound.5
Civil-engineering interpretationDiscussion identifies terrain implications such as access, likely cut/fill, drainage, or alignment constraints without overstating Google Earth accuracy.3
Handwritten presentationCalculations and interpretation are handwritten, legible, organized, and supported by the required printed/digital profile.3
Total20 / 20

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

Key Takeaways
  • A route must be interpreted in both plan and profile.
  • Digital terrain information supports reconnaissance but does not replace field verification.