3D Tiles from Photogrammetry

Why 3D Tiles matter for photogrammetry digital twins

Many photogrammetry projects do not end with a model; they end with a handoff. Solar teams need to review roof geometry, architects need existing conditions in context, contractors need client approvals and BIM teams need geometry that fits their planning workflow. A single huge OBJ, FBX or point cloud file is often the wrong delivery shape.

OGC describes 3D Tiles as a community standard for streaming and rendering massive 3D geospatial content such as photogrammetry, 3D buildings, BIM/CAD and point clouds. The value is delivery: a viewer loads the tiles and levels of detail needed for the current view.

That fits Voxelia’s role. The service is not selling drone flights; it is assessing and processing supplied imagery into usable models, CAD/BIM data, orthophotos or viewer handoffs.

What OGC 3D Tiles provide technically

3D Tiles organize 3D content in a spatial hierarchy. Instead of loading a full scene at once, a tileset describes which tiles, levels of detail and contents matter for the current view. This is well suited to buildings, sites, facades, roofs and large existing-condition models.

The OGC publication explicitly lists photogrammetry, BIM/CAD, point clouds and 3D buildings as target content. Cesium also documents tiling photogrammetry or LiDAR-derived meshes into 3D Tiles so they can be shared on the web without simplifying them into one small file.

glTF and GLB remain important. Khronos describes glTF as a compact, runtime-efficient 3D asset format, while Cesium notes that 3D Tiles build on glTF and other 3D data types. Practically, GLB is excellent for individual optimized models; 3D Tiles are better for large, geospatial, streamed scenes.

3D Tiles, GLB, point cloud, CAD and BIM: which output fits?

A common mistake is treating every 3D output as interchangeable. Planning and approval workflows need different properties: streaming, georeferencing, measurability, file size, semantic structure and editability.

3D Tiles are not a CAD or BIM replacement. They are a delivery and viewer format for large 3D scenes. Technical work may still require DXF, DWG, IFC-oriented models, point clouds or orthophotos. The best handoff often combines several outputs.

Which imagery is suitable for a 3D Tiles handoff

3D Tiles do not repair weak source data. If the photogrammetry geometry is unstable, roof edges, facade planes or equipment remain unreliable in the viewer. A good workflow starts with image quality, overlap, camera calibration, metadata and target accuracy.

For web-ready models it also matters how much detail is actually needed. A digital twin for visual review can be optimized differently than a handoff for CAD tracing, BIM checks or PV planning. The more decisions depend on the viewer, the more important scale, coordinate reference and documented limits become.

Cesium lists OBJ, FBX, DAE, glTF and GLB among supported inputs for photogrammetry tiling, and notes that models should use local coordinates with meters as units. The critical part is therefore not just tiling, but preparing a consistent model first.

Workflow: from supplied imagery to a web-ready digital twin

The strongest process separates image assessment, model QA, optimization and viewer delivery so each output has a clear purpose.

1. 01

   Review dataset and target output

   Voxelia first checks whether supplied photos, drone images or ground images are sufficient for the requested viewer, CAD, BIM, orthophoto or PV roof model.

2. 02

   Build and review the photogrammetry model

   Camera poses, point cloud, mesh and texture are generated, then weak overlap, blur, difficult surfaces and unstable areas are identified.

3. 03

   Optimize geometry for the use case

   Viewer navigation, CAD edges and BIM structure need different priorities, so optimization is guided by the target workflow.

4. 04

   Create the right format package

   Depending on the project, delivery can include GLB, 3D Tiles, point cloud, orthophoto, DXF/DWG or IFC-oriented files.

5. 05

   Separate viewer and planning handoff

   The browser viewer supports review and approval, while technical files remain available for CAD, BIM and PV teams.

Limits, risks and useful alternatives

3D Tiles are powerful when large 3D scenes need interactive delivery. They are less useful when a small roof body as GLB is enough, when the real need is a DXF drawing, or when the team only works in Revit, AutoCAD or PV software.

Hosting and data governance also matter. 3D Tiles can be delivered via cloud services, own infrastructure or project-specific viewers. The right choice depends on project size, access control, data ownership and integration needs.

Practical handoff: viewer for review, technical files for planning

For most Voxelia projects, the best result is not one format but a coordinated delivery package. A 3D viewer makes existing conditions understandable, while CAD, BIM, orthophoto or point cloud files support the actual planning work.

For roof and PV projects, this may mean a viewer-ready 3D model plus DXF/DWG roof edges, an orthophoto and obstruction geometry. For architecture and existing-condition capture, a 3D Tiles viewer can support coordination while an IFC-oriented model or point cloud supports production.

The practical search intent is clear: people looking for 3D Tiles from photogrammetry usually do not need a flight provider; they need imagery, geometry, formats and viewer delivery aligned into a usable model.