Week 14 · overview
Week 14: Data Capture Quality and Ground Control
This week, you will build capture quality plan for a bounded Drone Engineering scenario. The work stays in classroom-safe analysis, supplied evidence, simulation, planning, and documentation. It does not authorize real flight or unsupervised hardware work.
The engineering problem
Two image sets cover the same field, but one produces a cleaner reconstruction than the other.
The core idea is that data quality is engineered before processing starts. Students will connect that idea to flight path, shutter behavior, overlap, altitude consistency, ground control, and image review determine whether processing has enough reliable evidence.
Evidence you keep
| Sequence | Evidence artifact |
|---|---|
| Lesson 1 | Mechanism explanation and first evidence table |
| Lesson 2 | Boundary note and no-go or revision condition |
| Lesson 3 | Review-ready decision table |
| Mapping Log | Capture quality plan with limitation statement |
Vocabulary and decision lens
Important language this week includes: system boundary, evidence, limitation, no-go condition, revision rule, and data capture quality and ground control.
Decision lens: reject capture sets that cannot support the product even if the software produces something that looks finished.
Approximate time: 3 to 4 class periods, about 160 to 200 minutes of reading, analysis, evidence writing, and review.