GM_P2PFlags_t32 Enumeration |
Define option flags for P2P setup
Namespace:GlobalMapper.Lidar
Assembly: GlobalMapperWrapperNET45 (in GlobalMapperWrapperNET45.dll) Version: 19.1.0.0 (19.1.0.0)

C#
Copy
public enum GM_P2PFlags_t32

Member name | Value | Description | |
---|---|---|---|
P2P_AdjustZUsingControlPoints | 1 | Should we use our Lidar QC tool process to adjust the Z using the control points? We should get an even better Z match with this approach than similarity transform that has more error | |
P2P_DeleteWorkFiles | 2 | Should we delete the files when finished? | |
P2P_KeepWorkFilesOnSuccess | 4 | Keep work files on success even if GM_P2P_DeleteWorkFiles is set. Use if you will delete work folder externally | |
P2P_IgnoreExif | 8 | Should we drop the EXIF data in the images (like if it's a DJI Spark with inaccurate positions?) | |
P2P_UseRelativeAltitudes | 16 | Should we use relative altitudes offset by a base rather than EXIF values? | |
P2P_UseColorHarmonization | 32 | Harmonize colors between images before processing | |
P2P_CloudCreateFromMesh | 64 | Create point cloud from mesh rather than using original densified cloud. This takes longer but produces point clouds with less 'thickness' | |
P2P_AddCloudLayer | 128 | Should we automatically load and add the cloud layer even if not saving to a file? | |
P2P_LoadSparseCloud | 256 | Should we load the sparse point cloud in addition to the dense one? | |
P2P_UseSceneClustering | 512 | Should we use scene clustering to break up very large jobs? | |
P2P_ImageCreateFromMesh | 1024 | Create ortho-image from mesh rather than point cloud? | |
P2P_ImageCreateSeparate | 2048 | Create a separate ortho-image from each separate image rather than combining them? | |
P2P_DensifyUseSemiGlobal | 4096 | Use semi-global matching for DensifyPointCloud | |
P2P_HideProgress | 8192 | Don't show progress for this operation | |
P2P_RecursiveImageSearch | 16328 | Recursively look for images in mImageFolder | |
P2P_Default | 1155 |

Reference
GlobalMapper.Lidar
Namespace