metashape-reconstruction

Metashape Dense Reconstruction via MCP

Overview

Build dense products from aligned cameras in Metashape using MCP tools. This covers everything AFTER alignment: depth maps, dense point cloud, mesh, texture, DEM, and orthomosaic. All MCP tool calls block until complete — no polling, no timeouts.

When to Use

• Building depth maps, point cloud, mesh, or texture in Metashape
• Generating DEM or orthomosaic survey products
• Any processing step after photo alignment is complete

Golden Rules

1. CPU OFF for all dense operations. set_gpu_config(cpu_enable=False) before depth maps, point cloud, meshing, texturing, DEM, orthomosaic. CPU slows GPU operations. CPU is ONLY for alignment (match_photos, align_cameras).
2. NEVER write pipeline scripts. Call each MCP tool individually, check the result, adapt. This is an AGENT workflow.
3. No timeouts. Dense operations can take hours or days. MCP calls block until done.
4. No polling. Don't call get_processing_status in a loop.
5. Save after every step. The MCP tools auto-save, but verify with save_project() after major operations.
6. Check prerequisites. Each step requires the previous step's output. Verify before proceeding.

Standard Dense Pipeline

Step 0: Verify alignment is complete

get_alignment_stats()
# Check: alignment_rate should be >95%
# Check: tie_point_count_valid should be reasonable

Step 1: GPU config — CPU OFF

set_gpu_config(cpu_enable=False)

Step 2: Build depth maps

build_depth_maps(
    downscale=2,          # 1=Ultra, 2=High, 4=Medium, 8=Low, 16=Lowest
    filter_mode="mild",   # mild for complex terrain, moderate default, aggressive for clean scenes
    reuse_depth=True      # Reuse existing depth maps for aligned cameras
)

Quality guide:

• downscale=1 (Ultra): Final production, small projects. Very slow.
• downscale=2 (High): Standard production quality. Good balance.
• downscale=4 (Medium): Quick results, large projects, testing.