Why LOD matters for 3D building models from imagery
Most teams do not need a beautiful mesh for its own sake. They need a model that supports a decision: PV layout, CAD drafting, BIM handoff, viewer approval or an as-built digital twin.
The right detail level controls cost, delivery time and usefulness. A rough massing model can be enough for context, but it is not enough for roof edges. A heavily modeled BIM object can be wasteful when the job only needs roof planes and obstructions.
Voxelia processes existing imagery into usable model packages. That means the first question is not maximum detail, but which decision the model has to support.
Practical rule
LOD is not a quality promise on its own. A lean, purpose-built model can be more valuable than an over-modeled file without a clear handoff.
LOD, LoD and LOIN: related words, different decisions
CityGML uses levels of detail to structure geometric and semantic representations of city and building models. BIM standards focus more on the level of information need: which information is needed, when, why and at what granularity.
For image-based projects, both languages matter. A photogrammetry mesh can be visually dense without being a BIM model, while a lean BIM handoff can be valuable if it contains exactly the elements and attributes the planning team needs.
Better project question
Ask which surfaces, edges, objects, attributes, coordinates and formats must be reused at the end.
Useful detail levels for 3D building models
CityGML 3.0 provides a useful way to think about model detail. For Voxelia projects, the key lesson is simple: not every use case needs windows, interiors or every small facade element.
This table translates the idea into practical photogrammetry handoffs. It is a project guide, not a replacement for a formal specification.
| Level | Model Content | Works For | Risk |
|---|---|---|---|
| LOD 0 / context | Terrain, orthophoto, rough location or height context | Site overview and context communication | Not enough for roof edges, PV surfaces or CAD drafting |
| LOD 1 / massing | Simple building volumes without detailed roof shape | Massing, shadow context and early options | Roof pitch, obstructions and technical edges are often missing |
| LOD 2 / roof and envelope | Envelope with roof shapes, eaves, ridges and relevant planes | PV planning, CAD base data, as-built work and viewer handoff | Component semantics and interiors are not automatic |
| LOD 3 / detailed exterior | More detailed facade, roof and opening information where visible | Facade planning, digital twins and demanding BIM references | Only useful when image quality and project purpose justify it |
| BIM / IFC with LOIN | Selected components, attributes, coordinates and classification | Revit, Archicad, IFC and as-built BIM workflows | Needs clear information requirements |
PV, CAD, BIM or viewer: which output needs which detail?
Higher is not automatically better. A solar installer usually needs roof planes, pitch, orientation, obstructions and shading objects, not fully modeled facade semantics. Architects may need clean planes, coordinates and CAD or BIM structures.
Voxelia separates visible geometry from manually derived deliverables, so uncertain details are not presented as measured facts.
Detail is not accuracy
A dense mesh can contain many triangles and still be weak for CAD if scale, control, coordinate system or readable edges are not solid.
| Goal | Useful Output | Detail Level | Practical Note |
|---|---|---|---|
| PV roof planning | 3D roof model, planes, obstructions, OBJ/DXF/viewer where useful | mostly LOD-2-like roof and envelope | Focus on roof planes, pitch, orientation and shading. |
| CAD as-built base | Orthophoto, point cloud, DXF/DWG edges, planes and heights | LOD 1–2 plus technical derivatives | CAD needs clean lines and coordinates, not just a visual mesh. |
| Scan-to-BIM / as-built BIM | Point cloud or mesh reference, modeled components, IFC/Revit-ready structure | LOD 2–3 plus LOIN definition | BIM semantics must be deliberately modeled. |
| Digital twin or 3D viewer | Textured mesh, simplified envelope, hotspots and sharing link | visually optimized, often LOD 2 or selective LOD 3 | Performance and clarity matter as much as detail. |
| Facade or renovation planning | Facade orthophoto, mesh, point cloud, openings and relevant edges | selective LOD 3 on relevant facades | Only visible, sharp details should become dependable geometry. |
Why too much detail can hurt photogrammetry handoffs
Over-modeling increases delivery time, file size and coordination effort without necessarily improving decisions. In BIM, it can even mislead teams when guessed or hidden elements are modeled as if they were verified as-built data.
Photogrammetry reconstructs visible surfaces. Hidden layers, internal assemblies and covered connections need plans, measurements or expert assumptions. LOIN helps limit the delivery to information that is needed and defensible.
No false precision
If a detail is not safely derivable from the images, it should be labeled as an assumption, reference or manual addition.
How Voxelia defines the right model scope
The most efficient workflow starts with the desired handoff and works backward to the imagery. That creates a useful project package instead of an overloaded universal export.
- 01
Clarify target software and decision
PV*SOL, AutoCAD, Revit, Archicad, viewer and documentation workflows need different geometry, semantics and formats.
- 02
Check visible detail in the imagery
We review sharpness, overlap, oblique views, facade visibility, roof obstructions, scale, EXIF and control information.
- 03
Define LOD and LOIN per project
The scope states which surfaces, edges, objects, attributes and validation evidence are delivered.
- 04
Deliver a package, not just one model
Depending on the goal, the handoff may include mesh, point cloud, orthophoto, DXF/DWG, OBJ, IFC reference or viewer link.
- 05
Document limits clearly
Hidden or uncertain details are labeled so the model remains dependable for planning and communication.
Technical basis: OGC CityGML, LOIN and as-built accuracy
This guide follows standards-based thinking. OGC CityGML 3.0 explains levels of detail for city and building data. BIM information-need practice is shaped by EN 17412-1 and ISO 7817-1. USIBD Level of Accuracy terminology is useful for separating model detail from achieved accuracy in as-built documentation.
The takeaway for Voxelia projects is practical: detail level, information need and accuracy must be agreed separately.
FAQ: LOD for image-derived building models
Define scope before processing
Turn imagery into the right handoff
If you already have aerial, facade or object imagery, we assess which detail level makes sense for PV, CAD, BIM or viewer workflows.