RW06 — Preliminary Engineering Site Reconnaissance Using Google Earth and Google Maps
Learning Objectives
- Conduct a structured desktop reconnaissance of an assigned real-world site.
- Identify access, terrain, surrounding features, constraints, and potential survey control locations.
- Propose a preliminary field-survey strategy supported by annotated mapping.
Activity Scope
Review an assigned site using Google Earth and Google Maps, identify approximate project limits, access routes, terrain changes, nearby structures, roads, waterways or drainage features, likely obstructions, potential control or benchmark locations, and areas requiring detailed field observation. Prepare an annotated reconnaissance map and a concise proposed survey workflow.
Desktop Reconnaissance Limitation
Remote imagery can be outdated, obstructed, generalized, or incomplete. Every desktop finding that affects engineering work must be verified during actual site reconnaissance or field survey.
Submission Requirement
Research Work is due on the next class meeting and is handwritten. Required annotated Google Earth or Google Maps outputs may be printed and attached.
Placeholder Status
The final activity will specify site selection, annotation symbols, required reconnaissance observations, and grading criteria.
RW06 — Required Data Tabulation
Use this structure as the minimum field or research data table. Add columns when the activity requires more detail.
Include an annotated reconnaissance map showing the approximate project boundary, access, major features/constraints, proposed control locations, and the planned field-survey coverage.
RW06 — Grading Rubric
Award points according to the evidence shown for each criterion.
| Criterion | Full-credit evidence | Points |
|---|---|---|
| Site selection and reconnaissance basis | A suitable CE site/problem is defined with clear location, purpose, boundary/extent, and digital reconnaissance sources. | 4 |
| Mapped site features and constraints | Access, terrain, drainage, structures, hazards, boundaries, and other relevant features are identified and annotated clearly. | 5 |
| Engineering concerns and interpretation | Observations are translated into relevant surveying/CE concerns while clearly distinguishing desktop evidence from field-confirmed facts. | 5 |
| Proposed field-survey plan | Logical control locations, survey coverage, priority checks, and follow-up measurements are proposed. | 3 |
| Handwritten presentation | Reconnaissance notes and recommendations are handwritten, organized, legible, and supported by the required annotated map. | 3 |
| Total | 20 / 20 | |
Scoring guide: full credit for complete, technically correct, traceable evidence; reduce proportionally for minor errors, incomplete work, or weak documentation.
Key Takeaways
- Desktop reconnaissance improves field planning but does not replace site verification.
- A useful reconnaissance output links visible site conditions to a practical field-survey plan.