Skip to content
CEGR 493
Investigation
Week 3
transportation
Site Investigation Lab
Not graded — practice
Capstone II dashboard

This deliverable is not counted toward your grade

Project Start and Technical Implementation (site, data and investigation) pages are required practice but are not counted toward your final grade. Your engineering grade comes from Chapter 4 and Chapter 5.

Base Mapping

Students assemble a controlled base map that merges survey, utility, and topographic data into a single reference drawing for all design disciplines.

Section progress

0% of the workflow complete

Field & Laboratory · Plan, execute and document field and laboratory data collection to a defensible quality standard.

Deliverable: Controlled base map (CAD/GIS) with SUE quality-level classification.

How to complete this section

0 words saved

Do this next: Read the Base Mapping lecture and the worked example so you know what "Controlled base map (CAD/GIS) with SUE quality-level classification." has to contain.

Not sure how to start or how much depth is expected? Read the fully written model example for this deliverable first — it shows the structure, tables and level of justification your advisor grades against.

Site Investigation Lab — what this workspace teaches

Plan, execute and document field and laboratory data collection to a defensible quality standard.

  • Planning a subsurface, structural or traffic field investigation
  • Instrumentation selection, resolution, accuracy and calibration records
  • GPS/GNSS positioning: datums, projections, RTK vs. handheld accuracy
  • GIS data capture, attribute schemas and coordinate metadata
  • Land surveying: traverses, levelling, closure and error adjustment
  • Sampling strategy: representative sampling, spacing, depth intervals, replicates
  • ASTM/AASHTO laboratory testing procedures and reporting requirements
  • Chain of custody, sample labelling and preservation
  • QA/QC: duplicates, blanks, repeatability and data validation rules

End-of-term milestones

  • Tuesday, November 17, 2026 — Poster printed and ready. 36 in × 48 in poster finalized and printed one week before the November 24 showcase.
  • Wednesday, November 18, 2026 — Final document package uploaded for scoring. Chapters 4–5, calculation package, drawings and appendices uploaded in the app for advisor scoring.
  • Wednesday, November 18, 2026 — Poster presentation to faculty and industry. Wednesday poster session — printed 36 in × 48 in poster presented in person; industry reviewers score communication and impact.
  • Wednesday, November 25, 2026 — Oral presentation and defense (scored). Scored oral presentation and defense held on Wednesday, November 25.
Week 3
transportation

Base Mapping

Students assemble a controlled base map that merges survey, utility, and topographic data into a single reference drawing for all design disciplines.

Section B

Engineering story

A real project situation that frames this module

A transportation engineering team hits base mapping in week 3, with the roadway geometry, control plan and operational analysis already promised to the owner. Students assemble a controlled base map that merges survey, utility, and topographic data into a single reference drawing for all design disciplines. The reviewer starts at the end and works backwards, and the chain breaks at base map layering conventions (existing vs.

Showing SUE Quality Level D (records only) utilities with the same line weight as field-verified Quality Level A. Because contour interpolation methods (TIN vs, the error does not stay local: it is carried into the data foundation every later calculation silently depends on, and every downstream product inherits it before anyone notices.

Drivers, pedestrians, cyclists, transit riders and the agency that owns the facility carry the consequence. On this module specifically, the exposure runs through utility quality levels per subsurface utility engineering (SUE) classification (A–D), and the cost of correction rises every week the roadway geometry, control plan and operational analysis moves closer to issue.

Decisions the engineer must make

  • What record establishes base map layering conventions (existing vs, and is that record in the project data inventory?
  • Does ASCE 38-22 (2022), Sec. 5, govern here — and is that the edition adopted by the jurisdiction?
  • What is the acceptance criterion for contour interpolation methods (TIN vs, and was it written before the result was known?
  • Is the documented procedure valid for the conditions this project actually presents?
  • If the check fails, does the team revise the roadway geometry, control plan and operational analysis or raise a change request against the locked baseline?
Dense peak-hour traffic queued on an urban arterial at dusk.

Photo 1. Peak-hour demand: the flow rate that drives capacity, delay and level-of-service analysis.

Wikimedia Commons, CC BY 2.0

Section C

Why this matters

Professional

A licensed engineer defending base mapping cites ASCE 38-22 (2022), Sec. 5, and shows the record behind each input. Your controlled base map (cad/gis) with sue quality-level classification. is reviewed the same way — traceability is assessed before arithmetic.

Technical

Base map layering conventions (existing vs controls the numbers this module hands forward. Contour interpolation methods (TIN vs determines whether those numbers remain valid once conditions change.

Safety

The failure mode this module guards against is a geometric or control element that puts drivers in a conflict they cannot resolve. It reaches people through reconciling conflicting elevation data sources within a stated tolerance, which is why the safety check is recorded explicitly here rather than inferred from a passing strength or performance check.

Economic

The data foundation every later calculation silently depends on is priced from this work. Quantities, unit costs and schedule float all trace to base map layering conventions (existing vs; a late correction here is paid for as a change order, not a redline.

Environmental

Environmentally, this module fixes vehicle delay emissions, pavement material demand and stormwater from added impervious area. Choosing conservatively without justification is not free — the excess shows up as material, energy and land that the project consumes for no measurable gain.

Community

Everyone who walks, rides or drives the corridor every day inherit whatever this module decides — performance, accessibility, cost of ownership and resilience are set here, not at the ribbon-cutting.

Section D

Learning objectives

By the end of this module you will be able to:

  1. 1.Compare base map layering conventions (existing vs, using this project's own conditions rather than a textbook case.
  2. 2.Justify contour interpolation methods (TIN vs, using this project's own conditions rather than a textbook case.
  3. 3.Justify utility quality levels per subsurface utility engineering (SUE) classification (A–D), using this project's own conditions rather than a textbook case.
  4. 4.Evaluate reconciling conflicting elevation data sources within a stated tolerance, using this project's own conditions rather than a textbook case.
  5. 5.Apply ASCE 38-22 (2022), Sec. 5, and cite the section that governs your acceptance decision.
  6. 6.Produce controlled base map (cad/gis) with sue quality-level classification. at a standard the DOT design reviewer would accept without a second revision cycle.

Section E

Instructional content

Full lecture notes with figures and governing equations

Base Mapping: from proposal statement to engineering product

Students assemble a controlled base map that merges survey, utility, and topographic data into a single reference drawing for all design disciplines. That single sentence hides the substance of the module: base map layering conventions (existing vs, and contour interpolation methods (TIN vs. Both must be established from project evidence before anything downstream is credible.

In transportation engineering, this work is the input to the roadway geometry, control plan and operational analysis. Utility quality levels per subsurface utility engineering (SUE) classification (A–D) — which is why this page asks you to record the source of every quantity, not just its value. The data foundation every later calculation silently depends on depends on it.

  • Base map layering conventions (existing vs. proposed, discipline-coded layers)
  • Contour interpolation methods (TIN vs. grid) and appropriate contour interval selection
  • Utility quality levels per subsurface utility engineering (SUE) classification (A–D)
  • Reconciling conflicting elevation data sources within a stated tolerance
FIGURE 1center, RPCPT1Existing contour2Proposed contour3Utility QL-B4Utility QL-A5ROW line6Benchmark
Figure 1. Base Mapping — annotated engineering schematic showing the governing quantities carried through this module.Read this figure alongside the theory block: every labelled quantity must appear in your calculation package with a unit and a source.
Dense peak-hour traffic queued on an urban arterial at dusk.

Photo 1. Base Mapping: from proposal statement to engineering product in practice — Peak-hour demand: the flow rate that drives capacity, delay and level-of-service analysis.

Wikimedia Commons, CC BY 2.0

Decision logic: the procedure that replaces a closed-form solution

Base Mapping is governed by a documented procedure rather than a single expression, so the decision logic is the deliverable: what you accept, what you reject, and on what evidence. Base map layering conventions (existing vs.

Write the acceptance criterion before you look at the result. Contour interpolation methods (TIN vs — recording the criterion afterwards lets it be shaped to fit the number you happened to get.

Dense peak-hour traffic queued on an urban arterial at dusk.

Photo 2. Decision logic: the procedure that replaces a closed-form solution in practice — Peak-hour demand: the flow rate that drives capacity, delay and level-of-service analysis.

Wikimedia Commons, CC BY 2.0

Constraints, adopted standards and the safety case for base mapping

ASCE 38-22 (2022), Sec. 5, governs this module: Standard guideline for utility quality level classification on base mapping AASHTO Green Book (7th Ed.), Ch. 2, adds the second constraint: Base mapping accuracy requirements for roadway design

The safety case is explicit here. The failure mode is a geometric or control element that puts drivers in a conflict they cannot resolve; the people exposed are drivers, pedestrians, cyclists, transit riders and the agency that owns the facility; the control that prevents it is reconciling conflicting elevation data sources within a stated tolerance together with an independent check by someone who did not perform the work.

  • Controlling criterion for this module: base map layering conventions (existing vs.
  • Adopted reference: ASCE 38-22 (2022) — cite Sec. 5 by number.
  • Failure mode guarded: a geometric or control element that puts drivers in a conflict they cannot resolve.
  • Evidence produced: Controlled base map (CAD/GIS) with SUE quality-level classification..
FIGURE 2Confirm inputs and sourcesSelect governing standardAnalyze / designCheck units and equilibriumIndependent checkAccept or revise
Figure 2. Base Mapping — professional workflow from inputs through acceptance.The revise loop is normal. Reviewers expect to see it in your version history.
Dense peak-hour traffic queued on an urban arterial at dusk.

Photo 3. Constraints, adopted standards and the safety case for base mapping in practice — Peak-hour demand: the flow rate that drives capacity, delay and level-of-service analysis.

Wikimedia Commons, CC BY 2.0

Where this method stops being valid

Every method has a domain of validity. State the range of geometry, loading, material behaviour or flow regime over which your approach holds, and state what you would do instead beyond it.

For this project, the boundary you are most likely to push is reconciling conflicting elevation data sources within a stated tolerance. If you cross it, say so in writing, bound the error, and carry the limitation into your results chapter. A disclosed limitation is professional practice; a silent extrapolation is not.

Dense peak-hour traffic queued on an urban arterial at dusk.

Photo 4. Where this method stops being valid in practice — Peak-hour demand: the flow rate that drives capacity, delay and level-of-service analysis.

Wikimedia Commons, CC BY 2.0

Section F

Engineering workflow

Steps

  1. 1. Assemble the inputs this module needs — base map layering conventions (existing vs; contour interpolation methods (TIN vs — each with a unit and a source record.
  2. 2. Confirm ASCE 38-22 (2022) is the adopted edition and locate Sec. 5.
  3. 3. State the assumptions and the acceptance criterion for base map layering conventions (existing vs.
  4. 4. Execute the documented procedure, recording each judgement and the evidence behind it.
  5. 5. Test the result against utility quality levels per subsurface utility engineering (SUE) classification (A–D).
  6. 6. Audit units and run an order-of-magnitude check by hand before the number leaves your desk.
  7. 7. Obtain an independent check from a teammate who did not perform the work, and record their name and date.
  8. 8. Assemble controlled base map (cad/gis) with sue quality-level classification. and submit it to the DOT design reviewer for review.

Decision points

  • Is every input behind base map layering conventions (existing vs traceable? If not — stop and collect the record.
  • Does the result satisfy contour interpolation methods (TIN vs? If not — revise the work, never the criterion.
  • Would the correction change the data foundation every later calculation silently depends on? If yes — raise a change-control request before proceeding.
  • Have you ruled out the most common error on this module — showing SUE Quality Level D (records only) utilities with the same line weight as field-verified Quality Level A?

Quality checklist

  • Documented: base map layering conventions (existing vs
  • Documented: contour interpolation methods (TIN vs
  • Documented: utility quality levels per subsurface utility engineering (SUE) classification (A–D)
  • ASCE 38-22 Sec. 5 cited by section number
  • Procedure steps recorded in order with evidence
  • Acceptance criterion recorded before the result
  • Independent check signed and dated
  • Controlled base map (CAD/GIS) with SUE quality-level classification. attached and named per the course convention

Section H

Interactive visualization

Base Mapping — step-through

Advance one frame at a time. Each frame adds one engineering decision to the previous state.

Stepwise reveal

Step 1 of 6

Import balanced survey control as the mapping datum.

Section I

Applicable codes and standards

ASCE 38-22

2022 · Sec. 5

Adopted design/analysis reference governing this module.

Relevance: Standard guideline for utility quality level classification on base mapping

Reference the section number and edition in your calculation package. Do not reproduce code text.

AASHTO Green Book

7th Ed. · Ch. 2

Adopted design/analysis reference governing this module.

Relevance: Base mapping accuracy requirements for roadway design

Reference the section number and edition in your calculation package. Do not reproduce code text.

Section J

Worked examples

Full engineering solution format

Section K

Common mistakes and how to avoid them

  • Showing SUE Quality Level D (records only) utilities with the same line weight as field-verified Quality Level A.
  • Interpolating contours across a real discontinuity (retaining wall, channel) as if the surface were smooth.
  • Treating base map layering conventions (existing vs as a given instead of establishing it from a project record.
  • Producing controlled base map (cad/gis) with sue quality-level classification. without showing how contour interpolation methods (TIN vs was satisfied.
  • Recording the outcome of this module without recording the judgement and evidence that produced it.
  • Missing reconciling conflicting elevation data sources within a stated tolerance, which is exactly the path to a geometric or control element that puts drivers in a conflict they cannot resolve.
  • Collecting data before defining what decision the data has to support.
  • Accepting a laboratory or field value without its method, date, operator and uncertainty.
  • Using inputs that no field record, laboratory report, or published source supports.
  • Stopping at output and skipping verification — an unverified number is not an engineering result.
  • Confusing results (what the analysis produced) with conclusions (what the engineer decided).

Section L

Industry case study

Documented failure related to base mapping

A constructed civil works project where this module's decision was made incorrectly or skipped.

Official findings

  • Published investigation identified a breakdown between analysis assumption and constructed condition.

Field observations

  • The controlling assumption was documented nowhere in the design record.
  • No independent check existed at the stage where the error entered the work.

Engineering interpretation

  • Interpretation below is student analysis for instructional purposes, not an official finding.
  • Map the failure to a step in your own workflow and state where your process would have caught it.

Lessons learned

  • Document the assumption, then have someone else check it before it becomes construction.

Source: Summarize the published investigation; cite it in your reference list. Do not reproduce copyrighted report text.

Section M

FE Civil exam connection

Handbook FE Reference Handbook — transportation engineering section (record the section number from your handbook edition).

Exam topics

transportation engineering fundamentals

Handbook formulas

    Weak results here feed your FE Civil Academy weak-area queue for targeted practice.

    Question 1 of 2

    Score: 0/2

    In base mapping, which item must be established BEFORE the analysis is run?

    Section N

    Apply it to your project — Base Mapping

    Complete this using your own capstone project data. Every field is saved to your project record and routed to your advisor with this module's submission.

    Inputs and sources

    Every value needs a traceable source.

    QuantityValueUnitSource / record

    Assumptions and consequences

    AssumptionBasisConsequence if wrong

    Self-check before submission

    Section O

    Design challenge

    Consulting challenge — Base Mapping

    Your firm has been retained to deliver the base mapping scope for a municipal client on a compressed schedule. Produce the technical position your firm would defend at a public meeting.

    Client request: The client wants a defensible recommendation, the basis of design, and an honest statement of what remains unresolved.

    Constraints

    • Adopted local code edition governs; no exceptions without written variance.
    • Budget and schedule are fixed; scope changes require change control.
    • Public safety and accessibility requirements are non-negotiable.

    Deliverables

    • One-page basis of design
    • Supporting calculation extract
    • Risk and limitation statement

    Evaluation

    • Technical correctness
    • Standard compliance
    • Clarity of engineering judgment
    • Honest treatment of uncertainty

    Section P

    Documentation workspace

    Write the report section for this module in the academic editor

    Loading editor…
    0 words

    Section Q

    File uploads

    Accepted: PDF, DOCX, XLSX, CSV, PNG, JPG, ZIP, DWG, SHP

    No files uploaded yet.

    Section R

    Deliverable and advisor review

    Controlled base map (CAD/GIS) with SUE quality-level classification.

    Data quality
    Safety
    Documentation
    Professionalism

    Submissions route to your assigned faculty advisor and are scored independently by faculty and administrator rubrics.

    Reflection

    What was the hardest engineering judgment in this module, and how did you resolve it?

    Section S

    ABET outcome mapping

    SO 2
    CE-PC1
    reinforced

    Controlled base map (CAD/GIS) with SUE quality-level classification. with advisor review and dual scoring.

    Assessment: Faculty rubric score and administrator rubric score on this module's submission.

    Rubric: Data quality · Target: 70% of students at or above 'meets expectations'.

    Section T

    References and further study

    standard

    ASCE 38-22 (2022)

    Adopted reference — cite section numbers, do not reproduce text.

    standard

    AASHTO Green Book (7th Ed.)

    Adopted reference — cite section numbers, do not reproduce text.

    template

    Base Mapping — instructor design procedure

    Course template for the calculation package format expected in the final report appendix.

    manual

    NCEES FE Reference Handbook

    Locate the equations used here and note the handbook section for exam recall.

    template

    Advisor meeting agenda item

    Bring the unresolved decision from this module to your next weekly advisor meeting.

    Week 3 · Controlled base map (CAD/GIS) with SUE quality-level classification.
    © 2026 Dr. Steve Efe. Civil Engineering Capstone Studio. All rights reserved.