Choosing a capture stack isn’t just a camera decision; it shapes everything downstream — how quickly teams can share scans, how easily geometry lands in authoring tools, and whether the organization keeps long-term custody of data. Today, three families dominate practice: turnkey platforms (e.g., Matterport), open photogrammetry (COLMAP/AliceVision), and AI-first pipelines (NeRF/Gaussian Splatting, often via Nerfstudio). Each has a clear sweet spot, and understanding the trade space helps avoid expensive rework later.
Matterport is designed for speed and predictability. The Pro3 camera couples with a guided mobile workflow and cloud processing to produce polished “digital twins” suitable for immediate sharing with non-technical stakeholders. The current product page positions Pro3 starting at $5,995, signaling a CAPEX-plus-subscription model rather than purely pay-as-you-go.
Interoperability is better than it used to be, but still gated by add-ons. The E57 export option yields a vendor-neutral point cloud aligned with ASTM E2807, while MatterPak provides OBJ/PNG/XYZ assets; Matterport also offers a Revit plug-in to bring E57/XYZ directly into projects. These pathways are robust, yet they sit behind plan tiers and add-on purchases — so neutral deliverables remain an intentional choice, not the default.
Where Matterport shines is field efficiency and predictable outcomes across varied crews. The trade-off is recurring OPEX, plus a viewer-centric ecosystem that encourages staying within the platform unless you consistently export neutral formats.
Open stacks expose every stage of the pipeline — feature extraction, matching, bundle adjustment, dense stereo, meshing — so teams can tune behavior for difficult scenes. COLMAP continues to evolve with performance and robustness improvements (e.g., multi-GPU feature extraction and matching, determinism options, and CUDA-enabled pycolmap on Linux), making it viable for scripted or semi-automated production.
On the user-interface side, Meshroom (AliceVision) offers a node-graph workflow and, in its 2025 line, emphasizes a more general “visual programming toolbox” with a plugin architecture. That matters for BIM teams because it lowers the barrier to standardizing capture recipes without hiding the knobs needed for edge cases.
The upsides are control and neutral outputs (OBJ/PLY natively and E57 via converters), along with local custody. The downsides are GPU/VRAM demands and the need for careful acquisition plans (coverage, angle diversity, exposure control). Teams must budget time for calibration, parameter sweeps, and occasional reprocessing — но once tuned, these pipelines scale well in steady-state operations.
Neural pipelines enable compelling view synthesis from casual phone video and short image sequences, often with faster capture than structured photo sets. Nerfstudio centralizes training and — increasingly — export: ns-export can emit point clouds, TSDF volumes, Poisson or marching-cubes meshes, cameras, and gaussian-splat PLYs, feeding lightweight web viewers or engines.
For splats specifically, the documentation calls out PLY export and lists multiple third-party viewers — useful for design reviews and remote walkthroughs without heavy meshing. But there are caveats: export capabilities are feature-gated (e.g., splats exported from trained splat models, not from all NeRF methods), and metric scale usually requires markers, surveyed control, or post-hoc alignment.
The broader GSplat ecosystem is also maturing (CUDA-accelerated rasterization, memory/perf improvements), which helps with throughput but does not, by itself, guarantee BIM-grade geometry. Expect to fuse with SfM/photogrammetry or add control points when hard tolerances matter.
Interoperability hinges on a few formats:
If long-term custody or cross-tool collaboration is a priority, plan the path from capture to one of these neutral endpoints before field work begins, so image/scan metadata, scale references, and alignment strategies are part of the acquisition plan.
Every stack has characteristic failure modes:
Regardless of path, enforce basic QA: check reprojection error distributions, validate registration against control points, and compute alignment RMSE before scans flow into authoring.
Turnkey platforms convert uncertainty into subscriptions and per-space add-ons. Hardware is an upfront cost (e.g., Pro3), but the predictability of guided capture and cloud processing reduces on-site risk and training time — valuable when deadlines or mixed-skill crews are the constraint.
Open photogrammetry shifts cost toward staff time and GPUs. The software is free, cameras can be commodity, and once a recipe is standardized, incremental jobs are inexpensive — ideal for teams running frequent scans with consistent conditions.
AI/NeRF stacks can minimize capture overhead (walk-through video; few minutes on site) but still incur compute during training and, if meshes are required, extra steps for extraction and cleanup. Export surfaces are improving, yet they remain the gating factor for strict BIM tolerances.
Highly regulated or sensitive sites may require local processing and strict custody. Even in cloud-friendly contexts, define an exit ramp: always archive raw images/video, project metadata, and neutral exports (E57, OBJ/PLY). Matterport’s support pages explicitly position E57 as a vendor-neutral escape hatch; treat it — and its associated imagery — as part of the official record.
| Aspect | Matterport | Open Photogrammetry | AI/NeRF/GSplat |
|---|---|---|---|
| Capture | Pro3 + guided app | DSLR/phone; planned photo sets | Phone video / short image sets |
| Processing | Cloud automated | Local GPU/cluster | Local or cloud |
| Exports | E57 add-on; MatterPak | OBJ/PLY; E57 via tools | PLY splats; meshes via ns-export |
| Strength | Speed, polish, support | Control, neutrality, custody | Fast capture; strong visualization |
Sources: Matterport Pro3 & E57 pages; COLMAP releases; Nerfstudio export docs.
If the priority is fast capture with predictable outcomes and a shareable viewer, a turnkey platform is hard to beat. If neutral deliverables, tunability, and local custody matter most, open photogrammetry is a strong default — especially once a team codifies its recipe. And where quick, photoreal view synthesis is the goal, AI/NeRF pipelines are now practical additions to the BIM toolbox, provided you anchor scale and mind the export surface.
ns-export) and splat export notes. docs.nerf.studio/reference/cli/ns_export.html