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.
Survey and GIS
Students compute a closed traverse and evaluate its precision before importing survey control into the project GIS.
Section progress
0% of the workflow complete
Field & Laboratory · Plan, execute and document field and laboratory data collection to a defensible quality standard.
Deliverable: Traverse closure computation and GIS base layer with CRS documentation.
How to complete this section
Do this next: Read the Survey and GIS lecture and the worked example so you know what "Traverse closure computation and GIS base layer with CRS documentation." 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.
Survey and GIS
Students compute a closed traverse and evaluate its precision before importing survey control into the project GIS.
Section B
Engineering story
A real project situation that frames this module
A transportation engineering team hits survey and gis in week 2, with the roadway geometry, control plan and operational analysis already promised to the owner. Students compute a closed traverse and evaluate its precision before importing survey control into the project GIS. The reviewer starts at the end and works backwards, and the chain breaks at closed-loop traverse computation.
Mixing NAD83 and WGS84 coordinates in the same GIS layer without a documented transformation. Because horizontal and vertical datum selection (NAD83, NAVD88) and geoid model application, 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 gNSS RTK vs, 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 closed-loop traverse computation, and is that record in the project data inventory?
- Does AASHTO Green Book (7th Ed.), Ch. 2, govern here — and is that the edition adopted by the jurisdiction?
- What is the acceptance criterion for horizontal and vertical datum selection (NAD83, NAVD88) and geoid model application, and was it written before the result was known?
- Is Linear misclosure = √(ΣΔE)² + (ΣΔN)² valid over the parameter range this project actually occupies?
- 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?
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 survey and gis cites AASHTO Green Book (7th Ed.), Ch. 2, and shows the record behind each input. Your traverse closure computation and gis base layer with crs documentation. is reviewed the same way — traceability is assessed before arithmetic.
Technical
Closed-loop traverse computation is what makes Linear misclosure = √(ΣΔE)² + (ΣΔN)² usable on this project rather than a formula copied from a reference. Get it wrong and every quantity derived from it is wrong by the same factor.
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 gIS layer structure, 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 closed-loop traverse computation; 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
Survey and coordinate control errors propagate identically to calculation errors when there is no independent check step. Everyone who walks, rides or drives the corridor every day live with that outcome long after the semester ends.
Section D
Learning objectives
By the end of this module you will be able to:
- 1.Explain closed-loop traverse computation, using this project's own conditions rather than a textbook case.
- 2.Interpret horizontal and vertical datum selection (NAD83, NAVD88) and geoid model application, using this project's own conditions rather than a textbook case.
- 3.Interpret gNSS RTK vs, using this project's own conditions rather than a textbook case.
- 4.Compare gIS layer structure, using this project's own conditions rather than a textbook case.
- 5.Compute the governing quantity from Linear misclosure = √(ΣΔE)² + (ΣΔN)² and Precision = 1 / (Perimeter / Linear misclosure), with a unit audit on every term.
- 6.Apply AASHTO Green Book (7th Ed.), Ch. 2, and cite the section that governs your acceptance decision.
- 7.Reproduce the worked example for a closed 4-leg traverse has a perimeter of 1,240 ft and defend the interpretation of the result.
- 8.Produce traverse closure computation and gis base layer with crs documentation. 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
Survey and GIS: from proposal statement to engineering product
Students compute a closed traverse and evaluate its precision before importing survey control into the project GIS. That single sentence hides the substance of the module: closed-loop traverse computation, and horizontal and vertical datum selection (NAD83, NAVD88) and geoid model application. 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. GNSS RTK vs — 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.
- Closed-loop traverse computation: latitude/departure, misclosure, and precision ratio
- Horizontal and vertical datum selection (NAD83, NAVD88) and geoid model application
- GNSS RTK vs. static survey — appropriate use for control vs. topographic detail
- GIS layer structure: coordinate reference system consistency across all project layers
Photo 1. Survey and GIS: 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
Governing relationships and how they are applied here
The relationships below govern survey and gis. Linear misclosure = √(ΣΔE)² + (ΣΔN)²; Precision = 1 / (Perimeter / Linear misclosure) — each is valid only inside the parameter range this project occupies, so state that range before substituting.
Horizontal and vertical datum selection (NAD83, NAVD88) and geoid model application sets the values you place into these expressions. Any code-prescribed factor must match AASHTO Green Book (7th Ed.); a factor lifted from a different edition silently changes the answer.
Linear misclosure = √(ΣΔE)² + (ΣΔN)²
- ΣΔE = sum of departures (east-west closure error)
- ΣΔN = sum of latitudes (north-south closure error)
Precision = 1 / (Perimeter / Linear misclosure)
- Perimeter = total traverse length
Photo 2. Governing relationships and how they are applied here 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 survey and gis
AASHTO Green Book (7th Ed.), Ch. 2, governs this module: Survey control accuracy applicable to roadway design base mapping FGDC Geospatial Positioning Accuracy Standards (1998), Part 2, adds the second constraint: Accuracy classification for control and GIS network survey
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 gIS layer structure together with an independent check by someone who did not perform the work.
- Controlling criterion for this module: closed-loop traverse computation.
- Adopted reference: AASHTO Green Book (7th Ed.) — cite Ch. 2 by number.
- Failure mode guarded: a geometric or control element that puts drivers in a conflict they cannot resolve.
- Evidence produced: Traverse closure computation and GIS base layer with CRS documentation..
Photo 3. Constraints, adopted standards and the safety case for survey and gis 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
The worked example — a closed 4-leg traverse has a perimeter of 1,240 ft — holds only while its assumptions hold. 1:3,670 fails the 1:10,000 requirement; the crew must re-observe the weakest leg (largest angular residual) rather than force-balance a traverse that does not meet project control tolerance. Outside that envelope the arithmetic still returns a number, and the number is wrong in a way no unit check will catch.
For this project, the boundary you are most likely to push is gIS layer structure. 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.
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. Assemble the inputs this module needs — closed-loop traverse computation; horizontal and vertical datum selection (NAD83, NAVD88) and geoid model… — each with a unit and a source record.
- 2. Confirm AASHTO Green Book (7th Ed.) is the adopted edition and locate Ch. 2.
- 3. State the assumptions and the acceptance criterion for closed-loop traverse computation.
- 4. Evaluate Linear misclosure = √(ΣΔE)² + (ΣΔN)² and Precision = 1 / (Perimeter / Linear misclosure) term by term, carrying one extra significant figure.
- 5. Test the result against gNSS RTK vs.
- 6. Audit units and run an order-of-magnitude check by hand before the number leaves your desk.
- 7. Obtain an independent check from a teammate who did not perform the work, and record their name and date.
- 8. Assemble traverse closure computation and gis base layer with crs documentation. and submit it to the DOT design reviewer for review.
Decision points
- Is every input behind closed-loop traverse computation traceable? If not — stop and collect the record.
- Does the result satisfy horizontal and vertical datum selection (NAD83, NAVD88) and geoid model application? 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 — mixing NAD83 and WGS84 coordinates in the same GIS layer without a documented transformation?
Quality checklist
- Documented: closed-loop traverse computation
- Documented: horizontal and vertical datum selection (NAD83, NAVD88) and geoid model application
- Documented: gNSS RTK vs
- AASHTO Green Book Ch. 2 cited by section number
- Units audited on every expression
- Acceptance criterion recorded before the result
- Independent check signed and dated
- Traverse closure computation and GIS base layer with CRS documentation. attached and named per the course convention
Section H
Interactive visualization
Survey and GIS — step-through
Advance one frame at a time. Each frame adds one engineering decision to the previous state.
Step 1 of 6
Occupy control points and record raw angles/distances.
Section I
Applicable codes and standards
AASHTO Green Book
7th Ed. · Ch. 2
Adopted design/analysis reference governing this module.
Relevance: Survey control accuracy applicable to roadway design base mapping
Reference the section number and edition in your calculation package. Do not reproduce code text.
FGDC Geospatial Positioning Accuracy Standards
1998 · Part 2
Adopted design/analysis reference governing this module.
Relevance: Accuracy classification for control and GIS network survey
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
- Mixing NAD83 and WGS84 coordinates in the same GIS layer without a documented transformation.
- Force-balancing a traverse that fails the precision standard instead of re-observing.
- Treating closed-loop traverse computation as a given instead of establishing it from a project record.
- Producing traverse closure computation and gis base layer with crs documentation. without showing how horizontal and vertical datum selection (NAD83, NAVD88) and geoid model application was satisfied.
- Substituting into Linear misclosure = √(ΣΔE)² + (ΣΔN)² outside the range where it is valid, and reporting the number anyway.
- Missing gIS layer structure, 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.
- Confusing results (what the analysis produced) with conclusions (what the engineer decided).
- Ignoring constructability: a design that cannot be built safely is not a completed design.
- Omitting the safety check because the strength check passed.
Section L
Industry case study
Hyatt Regency Kansas City walkway (datum/coordination lesson, adapted)
Design-build coordination failure between fabricator and design drawings
Official findings
- NBS investigation found a design change communicated through shop drawings was not independently rechecked against the original connection calculation.
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
- Survey and coordinate control errors propagate identically to calculation errors when there is no independent check step.
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
Handbook formulas
- Linear misclosure = √(ΣΔE² + ΣΔN²)
- Precision = misclosure/perimeter
Weak results here feed your FE Civil Academy weak-area queue for targeted practice.
Question 1 of 2
Score: 0/2In survey and gis, which item must be established BEFORE the analysis is run?
Section N
Apply it to your project — Survey and GIS
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.
| Quantity | Value | Unit | Source / record |
|---|
Assumptions and consequences
| Assumption | Basis | Consequence if wrong |
|---|
Self-check before submission
Section O
Design challenge
Consulting challenge — Survey and GIS
Your firm has been retained to deliver the survey and gis 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
Section Q
File uploads
Accepted: PDF, DOCX, XLSX, CSV, PNG, JPG, ZIP, SHP, DWG
No files uploaded yet.
Section R
Deliverable and advisor review
Traverse closure computation and GIS base layer with CRS documentation.
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
Traverse closure computation and GIS base layer with CRS documentation. 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'.
Traverse closure computation and GIS base layer with CRS documentation. 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
AASHTO Green Book (7th Ed.)
Adopted reference — cite section numbers, do not reproduce text.
FGDC Geospatial Positioning Accuracy Standards (1998)
Adopted reference — cite section numbers, do not reproduce text.
Survey and GIS — instructor design procedure
Course template for the calculation package format expected in the final report appendix.
NCEES FE Reference Handbook
Locate the equations used here and note the handbook section for exam recall.
Advisor meeting agenda item
Bring the unresolved decision from this module to your next weekly advisor meeting.