Why nadir imagery alone is often not enough
Nadir imagery looks straight down. That is ideal for classic orthophotos, DTMs/DSMs and large roof or site surfaces. But once vertical or angled geometry matters, gaps appear: facades only show up at the image edge, roof edges become soft, and parapets, eaves or rooftop structures are reconstructed poorly.
That is why building-focused photogrammetry workflows explicitly add visible facades to the dataset. In practice, if you need a roof model for PV, a facade view without perspective distortion, a usable digital twin, or a BIM handoff with clean building edges, oblique imagery should be planned from the start.
Simple decision rule
Orthophoto question: usually nadir. Building-envelope question: usually nadir plus oblique imagery.
Nadir vs oblique in real projects
Nadir and oblique imagery are not alternatives. They solve different parts of the same problem. Nadir is efficient and strong on horizontal surfaces. Oblique imagery is strong wherever vertical faces, overhangs and roof edges matter.
That is why many building projects are best captured as a hybrid dataset. Roof geometry stays stable, while the building envelope gains enough side visibility for better 3D reconstruction and more usable derived outputs.
| Mission | Camera | Overlap | Output | Best suited for |
|---|---|---|---|---|
| Nadir grid | camera straight down | often 75/60 to 80/70 | orthophoto, DTM, DSM, top-down products | sites, roof areas, terrain, plans |
| Double grid with oblique angle | additional facade and edge visibility | for visible facades often 85/70 | 3D mesh, point cloud, stronger building edges | building envelope, roof detail, as-built models |
| Orbit or facade mission | side-facing or angled view | high, often ≥ 85% depending on object | facade model, orthoplane, detail capture | facade surveys, heritage, damage documentation |
Mission design: angle, overlap and flight pattern
For visible facades, Pix4D recommends a double-grid city-reconstruction workflow with high overlap. DJI enterprise platforms increasingly automate oblique capture, but route count, image volume and processing cost still vary significantly by aircraft generation.
There is no single perfect angle. What matters is not one number, but whether all relevant faces are seen multiple times with enough texture, stable exposure and clean overlap.
Oblique does not automatically mean better
Too many angled images without clean overlap, exposure control or nadir support can increase processing time and still produce a weaker model.
Which outputs from oblique data really matter
The biggest misconception is that oblique capture automatically gives you every useful deliverable. In reality, the final product depends on how the data is projected and processed.
For facades and other non-horizontal surfaces, tools such as orthoplanes or planar orthoprojections are usually more reliable than screenshots from a 3D viewer.
| Deliverable | Strength | Limitation | Practical note |
|---|---|---|---|
| 3D mesh / model | better roof-edge and facade reconstruction | strongly dependent on texture and processing budget | good for viewers, digital twins and early planning |
| Point cloud | useful building-envelope geometry for CAD/BIM | gaps remain if the mission lacks side visibility | works well for Revit, Civil 3D and as-built use |
| Facade orthoplane | scaled 2D facade view without perspective distortion | requires correct section/orientation | ideal for architecture, renovation and documentation |
| Top-down orthophoto | still the standard product for sites and roofs | side geometry remains incomplete | still essential for layout, PV and area analysis |
Workflow for roofs, facades and digital twins
Reliable building data starts before the flight. Perspective, deliverable and downstream workflow must fit together from the beginning.
- 01
Define the final deliverable
Decide whether the project needs an orthophoto, roof model, facade orthoplane, point cloud or full 3D model.
- 02
Separate nadir and oblique roles
Use nadir for horizontal surfaces and oblique capture for vertical or complex geometry.
- 03
Set overlap and pattern by project type
Building envelopes usually need more overlap and more structured coverage than simple roof surfaces.
- 04
Keep georeferencing stable
RTK or GCPs do not replace the right angle, but they ensure the geometry is usable later.
- 05
Derive the correct projection
For facades, create an orthoplane or planar orthoprojection rather than exporting a perspective screenshot.
Capture the building envelope cleanly
Voxelia delivers roof, facade and 3D data aligned to the downstream workflow
Whether you need an orthophoto, facade orthoplane, point cloud or PV-ready roof model, we design data capture around the real deliverable instead of generic flight patterns.
Where oblique imagery matters most in practice
Oblique imagery matters most when roof edges, parapets, dormers, rooftop equipment, facade openings, inner courtyards or complete building envelopes are part of the decision-making workflow.
For facade surveys, renovation planning, architectural documentation and digital twin work, oblique imagery is often the difference between a visually plausible model and a technically useful one.
Typical mistakes and how to avoid them
Mistake one is confusing more images with better geometry. Additional angled images only help if they add useful visibility and remain well connected to the rest of the dataset.
Mistake two is choosing the wrong deliverable. A facade screenshot is not a scaled facade orthoplane.
Mistake three is overtrusting smart oblique defaults. Automation helps, but difficult courtyards, tight facades and special geometries still need human planning.
Client briefing tip
Specify the decision output, not just the object: roof model, facade ortho, BIM handoff or viewer. That determines whether nadir is enough or oblique imagery is required.