Enhancing UAV–SfM 3D Model Accuracy in High-Relief Landscapes by Incorporating Oblique Images
Bibliographic record
Abstract
Complex landscapes with high topographic relief and intricate geometry present challenges for complete and accurate mapping of both lateral (x, y) and vertical (z) detail without deformation. Although small uninhabited/unmanned aerial vehicles (UAVs) paired with structure-from-motion (SfM) image processing has recently emerged as a popular solution for a range of mapping applications, common image acquisition and processing strategies can result in surface deformation along steep slopes within complex terrain. Incorporation of oblique (off-nadir) images into the UAV–SfM workflow has been shown to reduce systematic errors within resulting models, but there has been no consensus or documentation substantiating use of particular imaging angles. To address these limitations, we examined UAV–SfM models produced from image sets collected with various imaging angles (0–35°) within a high-relief ‘badland’ landscape and compared resulting surfaces with a reference dataset from a terrestrial laser scanner (TLS). More than 150 UAV–SfM scenarios were quantitatively evaluated to assess the effects of camera tilt angle, overlap, and imaging configuration on the precision and accuracy of the reconstructed terrain. Results indicate that imaging angle has a profound impact on accuracy and precision for data acquisition with a single camera angle in topographically complex scenes. Results also confirm previous findings that supplementing nadir image blocks with oblique images in the UAV–SfM workflow consistently improves spatial accuracy and precision and reduces data gaps and systematic errors in the final point cloud. Subtle differences among various oblique camera angles and imaging patterns suggest that higher overlap and higher oblique camera angles (20–35°) increased precision and accuracy by nearly 50% relative to nadir-only image blocks. We conclude by presenting four recommendations for incorporating oblique images and adapting flight parameters to enhance 3D mapping applications with UAV–SfM in high-relief terrain.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".