Skip to content
VOXELIA 3D

Practical guide · Choosing the right downstream delivery

Point Cloud, Mesh or Orthophoto?

Many projects fail not because of the imagery, but because of the wrong output. For PV planning, CAD, BIM, facades, or viewers, not every 3D result serves the same purpose. This guide explains when existing imagery should become a point cloud, a mesh, an orthophoto, or an orthoplane for vertical surfaces.

  • 2D / 2.5D / 3DOutput logic

    the downstream workflow matters more than render quality

  • RCP / RCSRevit point cloud

    Autodesk baseline for many BIM reference workflows

  • 2026ReCap mesh in Revit

    RCMR integration documented by Autodesk from ReCap Pro 2026

Why output choice matters more than simply exporting a model

Voxelia is not a flight provider. The real service is turning existing or provided imagery into planning-ready deliverables. That means the key question is not just whether a model can be generated, but which deliverable best fits the downstream task.

Pix4D clearly distinguishes between result types: dense point clouds for accurate 3D points and measurement support, textured meshes for visualization, and orthomosaics as scaled 2D maps. Those outputs are not interchangeable in CAD, BIM, PV, or facade workflows.

This is where many deliverables break down: a visually strong mesh is delivered where a point cloud or orthophoto would have been more useful, or a standard orthophoto is used for facades even though orthoplanes are better suited to vertical surfaces.

Orthophoto of a real building from above, roof edges, skylights and chimney from the survey drawn in
Orthophoto · 1 cm per pixelPoint cloud, mesh, or orthophoto: the target output decides which format is actually needed.

Point cloud, mesh, orthophoto, and orthoplane compared

Pix4D describes dense point clouds as 3D point sets with coordinate and color information. Their strength is density and accuracy, making them strong technical reference outputs.

A textured mesh represents shape through surfaces and projected textures. It is excellent for visualization and communication, but according to Pix4D it is not the preferred basis for precise measurement.

An orthomosaic is a 2D map with uniform scale. It depends on DSM quality and image orientation. For vertical surfaces, Pix4D documents the orthoplane as an accurate scaled 2D representation for facades or floor plans.

System / datasetSuitabilityBest forPractical note
Point cloudExcellent for technical reference and downstream modelingBIM reference, CAD tracing, terrain models, quantities, as-built captureRevit commonly relies on indexed point clouds such as RCP/RCS. ArcGIS Pro supports LAS, ZLAS, and LAZ for scalable point-cloud sharing.
Textured meshExcellent for visualization and spatial understandingViewers, approvals, presentation, spatial coordinationMeshes are often the clearest visual format. For measurement-heavy workflows, a point cloud or orthophoto may still be needed in parallel.
Orthophoto / orthomosaicExcellent for scaled 2D interpretation of horizontal surfacesRoofs, terrain, sites, plans, documentation, early PV workPix4D builds orthomosaics from the DSM and the images. If the DSM is noisy, distortions usually show up in the orthophoto too.
OrthoplaneExcellent for vertical surfaces and planar sectionsFacades, interiors, preservation, precise elevationsPix4D explicitly positions orthoplanes as scaled 2D outputs for vertical and horizontal surfaces, which is often a better fit for facades than a classic top-down orthophoto.

Which output fits which use case

For roof and PV workflows, an orthophoto is often efficient for scaled 2D review, while heights, slopes, and complex roof geometry may still require point-cloud, mesh, or derived roof geometry support.

For CAD as-builts and BIM reference work, the point cloud is often the strongest technical intermediate product. Autodesk documents standard Revit point-cloud workflows through RCP/RCS and, from ReCap Pro 2026 onward, mesh workflows through RCMR as well.

For facades, elevations, and restoration, orthoplanes or carefully derived facade products are often more suitable than standard orthophotos. For client communication and approvals, textured meshes can be the clearest output.

  1. Define the target system before processing

    Revit, AutoCAD, GIS, PV*SOL, a viewer, or a report each imply a different delivery logic.

  2. Separate measurement from visualization

    If people need to trace, verify, coordinate, or model against the data, point clouds or derived products usually matter more than visual meshes alone.

  3. Think horizontally and vertically as separate problems

    Roofs and terrain often align with orthophotos and terrain derivatives. Facades and sections often align better with orthoplanes or point-cloud-based reference.

  4. Plan the import path, not just the file type

    In BIM and CAD workflows, the coordinate strategy and import method are as important as the output format itself.

Where deliverables fail in CAD, BIM, and planning

Orthophotos can be misleading because they look finished. Pix4D explicitly notes that orthomosaics depend on DSM quality and image positions, so edge artifacts and distortions can appear when the reconstruction is weak.

Point clouds are not immune either. Autodesk documented on February 10, 2026 that Revit does not simply use the GIS coordinate system stored in the ReCap RCP file, which is why alignment problems still occur in real projects.

The main risk with meshes is not that they are useless, but that teams ask them to do jobs better served by point clouds, orthophotos, or vectorized geometry.

Risk scenarioWhy it mattersTypical symptomCountermeasure
Mesh treated as a measurement baselinePix4D positions textured meshes more toward visualization than precise surveyingArguments about dimensions, edges, or slope based on a presentation outputUse point clouds, orthophotos, orthoplanes, or explicit vector derivations for technical measurement tasks
Orthophoto used for facades or complex verticalsTop-down orthomosaic logic is not ideal for vertical surfacesDistorted facade geometry or unclear elevation dimensionsUse orthoplanes or planar facade derivations instead
Revit import without a tested origin and coordinate pathAutodesk continues to document conflicts around point-cloud origin, shared coordinates, and project base pointsShifted point cloud, bad positioning, snapping issuesTest the RCP/RCS import path and point-cloud origin before delivery
Orthophoto derived from a weak reconstructionPix4D ties orthomosaic reliability directly to DSM and orientation qualityArtifacts at roof edges, distorted rooftop objects, unreliable boundariesValidate dense cloud and DSM quality before treating the orthophoto as planning-ready

How Voxelia derives the right output from existing imagery

Voxelia does not start from a rigid “we always deliver file X” mindset. The process starts with the downstream trade: planning, BIM, CAD, PV, viewer, or documentation.

Then the dominant geometry is reviewed. Roofs and terrain often benefit from strong 2D or 2.5D outputs. Facades, building shells, and BIM references often benefit from a 3D reference layer first.

Only then is the final delivery bundle defined. In many cases, the most efficient result is not a single export, but a deliberately combined delivery package.

When combining outputs is the better solution

Many real projects benefit from a combination rather than a single output. A roof project might need an orthophoto for fast 2D checks, a 3D model for spatial review, and a derived geometry package for CAD or PV software.

For existing buildings, a point cloud plus mesh can be particularly effective: the point cloud acts as the technical reference while the mesh supports coordination and review. Facade work may add an orthoplane on top.

This becomes economical when the combined package removes follow-up questions and avoids manual rebuilding in downstream tools.

FAQ on choosing photogrammetry outputs

Is a point cloud always better than a mesh?
No. Point clouds are often stronger for technical reference and modeling tasks, while meshes are often better for communication and visual review. The better output depends on the downstream task.
When is an orthophoto enough on its own?
When horizontal or slightly inclined surfaces need scaled 2D interpretation, such as roofs, terrain, or documentation. Once facades, complex 3D coordination, or reference modeling matter, an orthophoto alone is often not enough.
Should Revit workflows use point clouds or meshes?
Classic Revit reference workflows still rely heavily on point clouds, often through RCP or RCS. Autodesk also documents RCMR mesh workflows from ReCap Pro 2026 onward. The right choice depends on whether the workflow is primarily reference-based or already mesh-oriented.
What is the common facade mistake?
Treating a standard top-down orthophoto as a good facade deliverable. Orthoplanes or other planar facade derivations are usually the cleaner option.
Can Voxelia choose the right output from existing imagery?
Yes. That is the core service: assess existing or provided imagery and derive the output that best supports CAD, BIM, PV, orthophoto, or viewer workflows.
  • Point Cloud
  • Mesh
  • Orthophoto
  • BIM
  • CAD
  • Photogrammetry

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.