3D Photo Engine

The 🆕 3D Photo Engine is LP360's fully integrated photogrammetry workflow to process imagery alongside existing LiDAR data to generate enhanced geospatial products through a guided interface. The workflow guides users through selecting photo inputs, optional point cloud integration, product configuration, and job submission, thereby enabling outputs such as aligned imagery, orthomosaics, and colorized point clouds. 

This wizard is accessed via the Ortho Photo , Colorize Point Coud , 3D Mesh , BBA Only , or Custom Photo tools on the Photo tab of the ribbon. Each exposing the applicable products within the guided interface.

For convenience, the Photo tab also includes supporting tools such as Cycle Import and Add Photo Layer , which are commonly used to prepare photo inputs prior to launching the 3D Photo Engine.

The Photo Inputs step is where source imagery is selected and prepared for photogrammetric processing. It lists available photo layers in the project and allows you to choose which images will be used, along with their spatial reference information. In this step, you can enable image masking, apply color corrections, and configure photo alignment options such as bundle block adjustment and camera calibration updates. These settings establish the foundation for accurate alignment and high‑quality downstream products.

Fixed Mask Folder

The Fixed Mask Folder is a directory that contains predefined image masks used when Use Fixed Mask for All Photos is enabled. When enabled, the same mask geometry is applied to every photo in the selected photo set, ensuring consistent exclusion of non‑reconstructible features during alignment and reconstruction.

Configuring a Fixed Mask Folder

To use a fixed mask, the folder must contain mask images that correspond to the input cameras. The following requirements apply:

• Mask format
  Masks must be standard image files (JPG, JP2, JXL, PNG, TIF, BMP, EXR, or TGA) where:
  • White (or non‑transparent) areas represent regions to keep
  • Black or transparent areas represent regions to exclude
• Image dimensions
  Each mask image must match the pixel dimensions of the photos it will be applied to. Masks are applied in image pixel space, not geographic space.
• Naming convention
  Mask filenames must exactly match the camera serial number, followed by _mask. This allows the 3D Photo Engine to correctly associate each mask with its corresponding camera. For example, "CameraSN_mask.jpg" or "D83ADDE7CADB1_mask.jpg"
• Folder structure
  All mask images should be placed in a single folder, which is then selected as the Fixed Mask Folder in the Photo Inputs step of the wizard.

Once configured, the selected masks are automatically applied during photo alignment and downstream processing.

When to Use Fixed Masks

Using a Fixed Mask Folder is recommended when:

• Obstructions appear in the same location in every image
• Imagery is collected from sensor‑mounted or aircraft‑mounted platforms
• Consistent feature exclusion is required across the entire dataset
• Automatic sky masking alone is insufficient or not applicable

Photo Alignment

Photo alignment performs a bundle block adjustment (BBA) to refine camera positions, orientations, and internal calibration based on image tie points. Alignment accuracy controls the image resolution used during matching, balancing precision and processing time. LP360 can update camera calibration as part of this process, improving geometric consistency across the block. If alignment fails for individual images, prior orientation information can be used to prevent gaps in derived products, particularly in challenging areas such as vegetation or low‑texture surfaces.

Alignment Accuracy - Selects the input photo resolution that is used in the Block Bundle Adjustment (BBA) step. Higher resolutions result in a more accurate BBA but increases the processing time. High is recommended. Select from:

Highest	2:1
High	1:1
Medium	1:2
Low	1:4
Lowest	1:8

The Point Clouds step allows you to select existing LAS layers to be used in the photogrammetry workflow. Selected point clouds provide spatial context and enable integration between image‑derived products and LiDAR data. This step displays key information such as point count, trajectory availability, and spatial reference, ensuring the correct datasets are included before generating combined or enhanced outputs. 

Note: To colorize a LiDAR point cloud using imagery, an associated trajectory must be available for the selected LAS layer.

Trajectory

The Select Trajectory file(s)... option allows you to explicitly select external trajectory files (*.TRJ) when associating LiDAR data with photo‑based workflows. This is useful when trajectory data is not already embedded or discoverable through the LAS Layer metadata.

When selected, LP360 opens a file browser so you can locate and select the appropriate trajectory file(s) (*.TRJ). Once loaded, the trajectory is validated and associated with the selected LAS Layer for use in operations such as point cloud colorization and other LiDAR‑integrated photo products.

Trajectory Status and Indications

The Point Clouds step provides indication verbiage describing trajectory availability and usability for the selected LAS layers. These indicators help confirm whether a dataset is ready for trajectory‑dependent operations.

• Available – A valid set of trajectories is available and will be used during processing.
• Select Trajectory file(s)... – The selected operation (such as colorization) requires a trajectory, but none is currently associated.

These messages update dynamically as trajectories are added, browsed, or changed, providing immediate feedback before job submission and reducing failed or incomplete jobs.

---

---

Refine Seamlines

Refine Seamlines controls how seamlines are optimized when stitching overlapping images into an orthomosaic. Adjusting seamlines helps reduce visible transitions caused by parallax, elevation changes, or lighting differences.

The following options are available:

• Disabled
  Uses default seamline placement without additional optimization. This provides the fastest processing and is suitable for simple terrain or quick‑look orthomosaics where visual blending is not critical.
• General
  Optimizes seamline placement to avoid image edges and elevated features such as buildings and vegetation. This option improves overall visual continuity and is recommended for most mapping and general orthomosaic workflows.
• Roof Edges
  Applies specialized seamline refinement focused on preserving sharp building and roof boundaries. This option is optimized for urban or built‑environment datasets where clean roof edges and reduced façade artifacts are important. Note: More processing‑intensive than General or Disabled. For faster processing or non‑urban terrain, General or Disabled is recommended.

Seamline refinement is applied automatically during orthomosaic generation and does not require additional configuration.

The 3D Mesh Model product option generates a textured 3D surface model from the processed imagery using photogrammetric reconstruction. When enabled, you can specify the output folder and control mesh generation parameters such as reconstruction method, overall quality, and face count to balance visual detail against file size and performance. The resulting mesh is suitable for visualization, inspection, and downstream 3D workflows in third party software.

3D Mesh Model Options

When Generate 3D Mesh is enabled, the following parameters control how the mesh is created and optimized.

Method

Quality

Face Count

Controls the density and complexity of the resulting mesh geometry.

• Low – Fewer faces for smaller file sizes and improved performance.
• Medium – Balanced mesh density for most use cases.
• High – Higher face density for detailed visualization at the cost of larger files and reduced performance.

Other Products provides auxiliary, interoperability-focused outputs rather than end-user deliverables.

 

Save Custom Settings opens a confirmation dialog asking whether you want to save the current Photo Processing settings as the Custom Job Settings. Choosing Yes saves these settings and automatically applies them the next time the Custom Photo command is launched from the Photo tab of the ribbon. Selecting No closes the dialog without saving any changes.

Submitting the job sends the 3D Photo Engine processing (MfE or MfEC) to the Job Manager queue. Open the Job Manager to monitor the progress. When the job finishes processing and is in the Ready state, select Complete Job to add the generated outputs to the current project based on the settings used at submission time. Completing the job also updates the photo EXIF metadata with the bundle block adjusted values.

How to Use the 3D Photo Engine

The 3D Photo Engine guides you through a streamlined, step‑by‑step workflow to generate photogrammetric and LiDAR‑enhanced products from imagery and optional point cloud data.

1. Launch the Wizard
   Open the 3D Photo Engine from the Photo tab using one of the product‑specific tools (Ortho Photo , Colorize Point Coud , 3D Mesh , BBA Only , or Custom Photo ). Each entry point exposes the relevant product options.
2. Select Photo Inputs
   Choose the True Pose® photo layers to process, configure optional masking and color corrections, and set photo alignment options such as bundle block adjustment accuracy and camera calibration behavior.
3. Add Point Clouds (Optional)
   Select existing LAS layers to integrate LiDAR data with imagery‑derived products. A valid trajectory is required when colorizing point clouds.
4. Configure Products
   Enable and configure the outputs you need, including:
   • Photo Products (orthomosaics, image‑derived point clouds)
   • LiDAR Products (colorized LAS layers)
   • 3D Mesh Models (textured meshes with adjustable method, quality, and face count)
   • Other Products (such as exporting a COLMAP package for external workflows)
5. Submit and Process
   Review the job summary, choose local or cloud processing, and submit the job. Progress is tracked in the Job Manager, where completed results are added back into your project.
   1. A message will appear showing the job (MfE for local or MfEC for Cloud) has been sent to the Job Manager .
   2. Open the Job Manager to monitor the status of each MfE or MfEC job. Once a job has finished processing, select the job and then Complete Job to complete the job and where applicable, add the results to your project.

This guided workflow ensures consistent setup, efficient processing, and high‑quality outputs while allowing advanced control where needed.