ReUseX  0.0.5
3D Point Cloud Processing for Building Reuse
Loading...
Searching...
No Matches
reusex::io::ColmapExportOptions Struct Reference

Options for COLMAP sparse model export. More...

#include <colmap.hpp>

Collaboration diagram for reusex::io::ColmapExportOptions:

Public Attributes

bool include_lidar_points = true
 Sub-sample the LiDAR cloud into points3D to seed PatchMatch + 3DGS init.
std::size_t max_lidar_points = 100'000
 Approximate cap on the number of seed points (uniform stride).
std::string lidar_cloud_name = "cloud"
 Name of the point cloud in ProjectDB to use as seed (typically "cloud").
int jpeg_quality = 95
 JPEG quality for the on-disk image dump (1..100).
bool include_panorama_slices = false
 Also emit perspective slices of content-aligned 360 panoramas as extra pinhole cameras (each aligned panorama is diced into overlapping tangent views via geometry::overlapping_views).
int pano_n_yaw = 8
 equator slices per panorama
double pano_fov_deg = 90.0
 per-slice horizontal FOV (deg)
int pano_tile = 1024
 slice size (px, square)

Detailed Description

Options for COLMAP sparse model export.

Definition at line 16 of file colmap.hpp.

Member Data Documentation

◆ include_lidar_points

bool reusex::io::ColmapExportOptions::include_lidar_points = true

Sub-sample the LiDAR cloud into points3D to seed PatchMatch + 3DGS init.

Set to false to write an empty points3D file (valid COLMAP input).

Definition at line 19 of file colmap.hpp.

◆ include_panorama_slices

bool reusex::io::ColmapExportOptions::include_panorama_slices = false

Also emit perspective slices of content-aligned 360 panoramas as extra pinhole cameras (each aligned panorama is diced into overlapping tangent views via geometry::overlapping_views).

Adds wide-FOV coverage for 3DGS. Only panoramas with a refined pose (pose_source == "aligned") are used.

Definition at line 36 of file colmap.hpp.

◆ jpeg_quality

int reusex::io::ColmapExportOptions::jpeg_quality = 95

JPEG quality for the on-disk image dump (1..100).

Used only when the stored frame is re-encoded; if the JPEG blob can be written verbatim we prefer that and ignore this knob.

Definition at line 30 of file colmap.hpp.

◆ lidar_cloud_name

std::string reusex::io::ColmapExportOptions::lidar_cloud_name = "cloud"

Name of the point cloud in ProjectDB to use as seed (typically "cloud").

Definition at line 25 of file colmap.hpp.

◆ max_lidar_points

std::size_t reusex::io::ColmapExportOptions::max_lidar_points = 100'000

Approximate cap on the number of seed points (uniform stride).

Definition at line 22 of file colmap.hpp.

◆ pano_fov_deg

double reusex::io::ColmapExportOptions::pano_fov_deg = 90.0

per-slice horizontal FOV (deg)

Definition at line 38 of file colmap.hpp.

◆ pano_n_yaw

int reusex::io::ColmapExportOptions::pano_n_yaw = 8

equator slices per panorama

Definition at line 37 of file colmap.hpp.

◆ pano_tile

int reusex::io::ColmapExportOptions::pano_tile = 1024

slice size (px, square)

Definition at line 39 of file colmap.hpp.


The documentation for this struct was generated from the following file: