Recent Changes

Differences

This shows you the differences between two versions of the page.

--- dev:technology:supported_formats:pointcloud:opc [2021/02/16 06:11]
jeroen [Write Options]
+++ dev:technology:supported_formats:pointcloud:opc [2024/05/07 12:36] (current)
maarten [Remove Header]
@@ Line 47: / Line 47: @@
 ==== Strip Attributes ====
-Options to remove source attributes in the target point cloud file. \\
+Options to exclude source attributes in the target point cloud file. \\
-Removing timestamps if available will significantly reduce the point cloud file size.
+Excluding the source timestamps in the target file will significantly reduce the point cloud file size.
 ==== Filtering  ====
@@ Line 65: / Line 65: @@
 ==== Block Size ====
-A Block is a spatial entity to store point cloud points within a level of the multi-resolution OPC file. The Block Size is the cubical dimension of Blocks at the lowest level of the OPC file. The best block size is found when the ratio between the number of points in one level and the next level is between 2 to 4. \\
+A Block is a spatial entity to store point cloud points within a level of the multi-resolution OPC file. The Block Size is the cubical dimension of Blocks at the lowest level of the OPC file. The Block Size unit is defined by the target Dataset CRS and metric when using Geographical CRS. The best block size is found when the ratio between the number of points in one level and the next level is between 2 to 4. \\
-The Block Size affects storage, performance, and defines Voxel filtering if set.
+The Block Size affects the multi-resolution performance, the file size, and defines Voxel Filtering if set.
   * Auto define density by random samples for optimized performance.
@@ Line 74: / Line 74: @@
     * ALS (Airborne LiDAR Scan) / Low density / Block size 50
   * Custom block size ((Once the handler of a slider is selected, the left-right arrow keys can be used for precise adjustments.))
+==== Mapping Resources ====
+The write options for a point cloud that is part of a mapping resource in the pointcloud/point_cloud.write.options.ini. The example configuration:
+  density.filter.treshold 1
+  block.size 1.0
+  write.attribute.GPSTime 0
+  write.attribute.color 1
+  write.attribute.intensity 1
+  intensity.8bit 1
+  write.attribute.classification 1
+Or
+  density.filter.treshold=1
+  block.size=1.0
+  write.attribute.GPSTime=false
+  write.attribute.color=true
+  write.attribute.intensity=true
+  intensity.8bit=true
+  write.attribute.Classification=true
+For this configuration: the point cloud filtering is enabled, block size is set to 1, the timestamp attribute is stripped, the color, intensity and classification attribute are written and the intensity values are clipped to an 8-bit range.
 ===== Processing Time =====
@@ Line 84: / Line 107: @@
 For example, reading a LAS file from SSD to write an OPC to SSD storage using Intel i7 processor and 4GB Memory will take 2 Seconds per Million points.
+===== Remove Header =====
+The CRS header can be removed from the Resource via the Dataset Properties Window. Unique upload situations may require OPC data to not have the CRS header.  Some situations include:
+  * Geospatial Alignments in iModels
+    * iModels with custom CRS
+    * Local Scan Data
+    * Scan data referenced and tied to custom iModel CRS
+    * No available CRS to assign local data
+Clearing the Point Cloud header enables the OPC data to be placed within the local/custom CRS grid from these iModel(s). Take note, extra care, knowledge, and information is required for these geospatial alignments.
+If the iModels requires this, the import Mapping Template can have the pointcloud.write.options.ini updated with:
+   remove.crs.header true
 ===== Legend and Georeference =====
 The resource can be accompanied by an [[dev:technology:supported_formats:other:olg|]] and [[dev:technology:supported_formats:other:ord|]].

Last modified:: 2021/02/16 06:11