Why layer structure matters more than a nice export
Photogrammetry can produce geometry, texture, point clouds, and orthophotos. Planners need more than files: they need data that is understandable, filterable, and reviewable in CAD.
Autodesk describes layers as a central method for organizing objects and controlling visibility and properties. For photogrammetry deliveries, that separation decides whether the data is usable or becomes manual cleanup work.
Voxelia processes supplied imagery into planning-ready data. The product is the usable geometry, not the drone flight.
Useful layers for DXF/DWG from photogrammetry and 3D models
A strong layer structure separates source, interpretation, and review state. An orthophoto is not a CAD edge; a point cloud is not a clean drawing; a mesh is usually a reference body, not a constructed component model.
| Layer | Suitability | Best for | Practical note |
|---|---|---|---|
| ORTHO_REFERENCE | image reference | roof view, facade orthophoto, site context | Keep as locked reference and separate from vector geometry. |
| ROOF_EDGES_ASBUILT | derived lines | PV layout, roofing, CAD base plans | Deliver with scale and quality status. |
| OBSTACLES | planning exclusions | chimneys, skylights, vents, parapets | Separate from visual-only details. |
| POINTCLOUD_REFERENCE | measurement reference | BIM, facade survey, height checks | Use as reference, not as finished CAD geometry. |
| MESH_REFERENCE | 3D context | viewer and visual coordination | Keep relevant vector edges separate. |
| QA_CHECKS | review trail | acceptance and scale checks | Keep control distances visible and switchable. |
Units, origin, and coordinates
CAD deliveries often fail because context is missing: meters or millimeters, local origin or georeferenced, 2D polyline or 3D polyline. Those details need to be decided before export.
buildingSMART separates geometry, units, and spatial referencing in IFC. CAD deliveries need the same discipline in simpler form: clear units, origin, coordinate status, and usage notes.
Typical errors in CAD exports from photogrammetry
A textured mesh is not automatically a clean CAD base plan. A point cloud does not replace layer logic. Orthophotos are powerful references, but they must stay identifiable as image references.
The most critical issue is mixing reliable and uncertain elements. Verified edges, hidden edges, and shadow-based interpretation should not share the same status.
| Problem | Why it matters | Typical symptom | Countermeasure |
|---|---|---|---|
| Everything on Layer 0 | No separation by source or status | Manual cleanup in the planning office | Separate orthophoto, edges, obstacles, references, and QA |
| Mesh as CAD substitute | Triangle surfaces are heavy and hard to edit | Large DWG with poor measurability | Deliver mesh as reference and vectorize relevant edges |
| Unclear scale | The file opens but measurements are unreliable | Issues appear in PV or detail planning | Document units, references, and check distances |
Voxelia workflow: from imagery to CAD package
The process starts with the target system. PV layout, roofing, architecture, BIM, site plan, and viewer workflows need different layers and detail.
Define the delivery
The target workflow determines layer logic and detail depth.
Review imagery and references
Scale, control dimensions, sharpness, overlap, and hidden zones are evaluated first.
Derive geometry
Orthophoto, mesh, point cloud, and relevant edges are created separately.
Structure the CAD package
DXF/DWG receives layers, units, origin notes, QA items, and usage recommendations.
Practice for PV, roofs, facades, and BIM
For PV, roof planes, obstructions, maintenance areas, and shading objects matter more than maximum data volume. For roofing, edges, penetrations, parapets, drainage zones, and dimensions matter. For facades and architecture, axes, openings, height references, and orthoplanes become more important.
BIM-oriented deliveries need a clear distinction between reference data and modeled components. A point cloud or mesh can be a strong base, but it is not yet an IFC component model.