Skip to content
VOXELIA 3D

BIM & delivery · LOD, LOIN and model purpose

Choose the right LOD for 3D building models

A useful model is not always the most detailed model. PV, CAD, BIM, viewer and digital-twin workflows need the right level of visible geometry, information need and delivery format.

  • LOD 0–3CityGML logic

    from context to envelope detail

  • LOINinformation need

    EN 17412-1 / ISO 7817-1 thinking

  • Purpose firstdelivery rule

    CAD, BIM, PV or viewer decides

Why LOD matters for 3D building models from imagery

Textured 3D model of a real building with surroundings in an oblique view
3D model · real projectTextured 3D model of a real building — the right level of detail depends on the purpose.

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 delivery, 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.

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 delivery can be valuable if it contains exactly the elements and attributes the planning team needs.

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 deliveries. It is a project guide, not a replacement for a formal specification.

LevelModel contentWorks forRisk
LOD 0 / contextTerrain, orthophoto, rough location or height contextSite overview and context communicationNot enough for roof edges, PV surfaces or CAD drafting
LOD 1 / massingSimple building volumes without detailed roof shapeMassing, shadow context and early optionsRoof pitch, obstructions and technical edges are often missing
LOD 2 / roof and envelopeEnvelope with roof shapes, eaves, ridges and relevant planesPV planning, CAD base data, as-built work and viewer deliveryComponent semantics and interiors are not automatic
LOD 3 / detailed exteriorMore detailed facade, roof and opening information where visibleFacade planning, digital twins and demanding BIM referencesOnly useful when image quality and project purpose justify it
BIM / IFC with LOINSelected components, attributes, coordinates and classificationRevit, Archicad, IFC and as-built BIM workflowsNeeds 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.

GoalUseful outputDetail levelPractical note
PV roof planning3D roof model, planes, obstructions, OBJ/DXF/viewer where usefulmostly LOD-2-like roof and envelopeFocus on roof planes, pitch, orientation and shading.
CAD as-built baseOrthophoto, point cloud, DXF/DWG edges, planes and heightsLOD 1–2 plus technical derivativesCAD needs clean lines and coordinates, not just a visual mesh.
Scan-to-BIM / as-built BIMPoint cloud or mesh reference, modeled components, IFC/Revit-ready structureLOD 2–3 plus LOIN definitionBIM semantics must be deliberately modeled.
Digital twin or 3D viewerTextured mesh, simplified envelope, hotspots and sharing linkvisually optimized, often LOD 2 or selective LOD 3Performance and clarity matter as much as detail.
Facade or renovation planningFacade orthophoto, mesh, point cloud, openings and relevant edgesselective LOD 3 on relevant facadesOnly visible, sharp details should become dependable geometry.

Why too much detail can hurt photogrammetry deliveries

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.

How Voxelia defines the right model scope

The most efficient workflow starts with the desired delivery and works backward to the imagery. That creates a useful project package instead of an overloaded universal export.

  1. Clarify target software and decision

    PV*SOL, AutoCAD, Revit, Archicad, viewer and documentation workflows need different geometry, semantics and formats.

  2. Check visible detail in the imagery

    We review sharpness, overlap, oblique views, facade visibility, roof obstructions, scale, EXIF and control information.

  3. Define LOD and LOIN per project

    The scope states which surfaces, edges, objects, attributes and validation evidence are delivered.

  4. Deliver a package, not just one model

    Depending on the goal, the delivery may include mesh, point cloud, orthophoto, DXF/DWG, OBJ, IFC reference or viewer link.

  5. 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

Which LOD do I need for PV roof planning?
Usually an LOD-2-like roof and envelope scope is enough: roof planes, pitch, orientation, eaves, ridges, obstructions and shading objects.
Is a photorealistic mesh automatically BIM?
No. A mesh captures visible surfaces. BIM needs structured components, attributes, coordinates, classification and a defined information need.
Can Voxelia create LOD 3 from existing images?
It depends on visibility, sharpness, overlap and scope. Visible facade and roof details can be modeled, but hidden or uncertain elements should be labeled as assumptions.
What matters more: LOD or accuracy?
They answer different questions. LOD describes model content and detail. Accuracy describes how close the geometry is to reality.
What should I provide before starting?
Original images, target software, desired outputs, coordinate requirements, existing plans and the decision the model needs to support.
  • LOD
  • LOIN
  • BIM
  • CAD
  • Digital Twin

Related

Related guides

Get started

The first project is on us.

Upload your drone photos. Standard projects are ready in 24–48 hours – for PV*SOL, AutoCAD, GIS or the browser.

First project without a credit card · then from €45 per project · no subscription needed

Keep this ready

Keep the prepared €45 pilot by email

We keep package, scope, and article context. If you do not pay now, the prepared Stripe link can come back later.