Week 13 · lesson
Images Become Measurements Through Geometry
One aerial photograph is a picture.
A set of photographs taken from different known or estimated viewpoints can become a geometric measurement system.
That is the core idea behind photogrammetry.
A pixel does not contain distance by itself
Look at a single image of a roof.
You can see corners, vents, seams, and shadows. But one pixel does not tell you its real-world X, Y, and Z position automatically.
The image records how light from the scene projected through the camera onto the image plane.
To recover geometry, processing software needs constraints from multiple images, camera models, position/orientation information, scale references, or other control evidence.
The useful question is:
Where does the same physical feature appear when the camera views it from another position?
Different viewpoints create parallax
Hold one finger in front of your face and alternate which eye is open.
Your finger appears to move relative to the background.
That apparent shift is parallax.
Photogrammetry uses the same geometric idea. A feature observed from multiple camera positions appears at different image coordinates. Those viewing rays can be used to estimate the feature’s position in space.
A simplified model is:
camera A ── ray to feature ┐
├─ estimated 3D feature position
camera B ── ray to feature ┘
Real reconstruction uses many features and many images, not just two perfect rays.
Tie points connect the image set
Software searches images for recognizable features that appear in more than one view.
These matched features are often called tie points.
Tie points help the reconstruction estimate how images relate to one another.
A strong set has many usable features distributed across the scene and visible from multiple viewpoints.
A weak set may contain:
- blank water;
- repetitive roof shingles with few unique features;
- motion blur;
- moving vehicles or people;
- strong reflections;
- large areas seen in only one image;
- major lighting differences.
The problem is not that the image “looks bad.” The problem is that the reconstruction has fewer reliable geometric correspondences.
Structure from motion
Modern photogrammetry pipelines often use Structure from Motion, or SfM, to estimate camera relationships and 3D scene structure from overlapping photographs.
Conceptually:
images
→ detect features
→ match features across images
→ estimate camera poses
→ triangulate scene points
→ refine the model
OpenDroneMap, for example, exposes Structure-from-Motion processing and can produce point clouds, orthophotos, elevation products, and 3D models from suitable datasets.
You do not need to operate a live drone to learn the reconstruction logic. Supplied image sets are enough.
Camera geometry changes the result
A camera model includes properties such as:
- focal length;
- image dimensions;
- lens distortion;
- sensor geometry;
- camera position;
- camera orientation.
If those properties are wrong or poorly estimated, reconstructed geometry can distort.
This is why camera calibration and metadata matter in measurement work.
A beautiful photograph can still create poor geometry if the camera model or image network is weak.
Scale has to enter somewhere
A reconstruction can have internally consistent shape without trustworthy real-world scale.
Scale can come from evidence such as:
- calibrated camera/geolocation information;
- known distances;
- ground control points;
- other surveyed references.
The exact method and achievable accuracy depend on the workflow.
Do not claim centimeter accuracy because the output software displays centimeters.
Display precision is not measurement accuracy.
Worked example: two roof datasets
Dataset A contains:
- 40 sharp images;
- strong overlap between neighboring views;
- stable exposure;
- several unique roof features visible repeatedly;
- camera positions recorded;
- one known scale reference.
Dataset B contains:
- 25 images;
- several gaps with no overlapping neighbor;
- motion blur in eight images;
- changing shadows;
- little metadata;
- no independent scale reference.
Which dataset is more likely to support a defensible geometric product?
Dataset A.
Not because 40 is a magic number. It has a stronger observation network: more repeated features, fewer gaps, cleaner imagery, and better reference information.
Moving objects can corrupt the geometry
Photogrammetry usually assumes the scene is reasonably static during capture.
If a car changes position between images, the same physical car feature does not occupy one stable 3D location.
Moving people, waving vegetation, water, shadows, and changing equipment can therefore create bad matches or reconstruction artifacts.
The software may still produce an output.
Your job is to decide whether the output represents the scene strongly enough for the claim you want to make.
Build a reconstruction evidence model
Take a supplied set of five image thumbnails and mark:
- features visible in multiple images;
- one area with strong overlap;
- one area with weak or missing overlap;
- one moving or ambiguous feature;
- one piece of camera or scale metadata.
Then draw:
capture geometry
→ matched features
→ camera pose estimate
→ 3D points
→ map/model product
→ measurement claim
Under each arrow, write one way the chain could fail.
Misconception: the software measures whatever appears in the photo
The software reconstructs from evidence and assumptions.
If the image network is weak, the scene moves, scale is poorly controlled, or camera geometry is wrong, the output can still look impressive while the measurements are weak.
A map is not accurate because it rendered successfully.
The Week 13 starting model
Photogrammetry turns images into measurements through geometry:
multiple viewpoints → repeated features → camera relationships → reconstructed scene → scale/georeference → bounded claim.
The next lesson focuses on the first major control you have over that chain: overlap and reference evidence.
decision flow
Automation Models: From Script to Responsible Boundary
Name the system model
Identify whether the supplied case describes a fixed sequence, an adaptive system, or an unknown behavior.
Identify the human role
Record the authority, supervision, and accountability described by the archival case without assigning operational duties to students.
Read the abstract representation
Interpret supplied coordinates or state labels as data, not as instructions for a location or vehicle.
Trace a modeled transition
Follow a provided state diagram and mark assumptions, missing evidence, and possible failure points.
Hold the operational boundary
Explain why qualified adults, official guidance, and manufacturer documentation own configuration and real-world decisions.
Read this concept flow as plain text
- Name the system model. Identify whether the supplied case describes a fixed sequence, an adaptive system, or an unknown behavior.
- Identify the human role. Record the authority, supervision, and accountability described by the archival case without assigning operational duties to students.
- Read the abstract representation. Interpret supplied coordinates or state labels as data, not as instructions for a location or vehicle.
- Trace a modeled transition. Follow a provided state diagram and mark assumptions, missing evidence, and possible failure points.
- Hold the operational boundary. Explain why qualified adults, official guidance, and manufacturer documentation own configuration and real-world decisions.