Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
dev:technology:supported_formats:pointcloud:opc [2021/02/15 14:39] jeroen |
dev:technology:supported_formats:pointcloud:opc [2024/05/07 12:36] (current) maarten [Remove Header] |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Orbit Point Cloud ====== | ====== Orbit Point Cloud ====== | ||
- | The Orbit Point Cloud (*.opc) is Orbit' | + | This page documents the Orbit Point Cloud (OPC) storage format. |
- | An OPC stores point geometry and attribute. | + | |
===== Structure ===== | ===== Structure ===== | ||
- | An Orbit Point Cloud file has extended data structure capabilities compared to other point cloud storage formats like LAS and E57. | + | An OPC stores point geometry and attribute. \\ |
+ | The OPC file has extended data structure capabilities compared to other point cloud storage formats like LAS and E57. | ||
An Orbit Point Cloud is built up of several OPC levels and depending on your zoom level when viewing the points, you see the OPC level which is best for rendering then. Level 1 consists of the least number of points, which is rendered when you're looking at the point cloud when you're zoomed out completely. The highest level consists of the highest number of points, which is rendered when looking very close to the points. If filtering is off, the highest level consists of all the points of the original point cloud. | An Orbit Point Cloud is built up of several OPC levels and depending on your zoom level when viewing the points, you see the OPC level which is best for rendering then. Level 1 consists of the least number of points, which is rendered when you're looking at the point cloud when you're zoomed out completely. The highest level consists of the highest number of points, which is rendered when looking very close to the points. If filtering is off, the highest level consists of all the points of the original point cloud. | ||
Line 20: | Line 21: | ||
===== Create ===== | ===== Create ===== | ||
+ | An OPC can be generated by importing 3rd party point cloud source files or by exporting a selection or subset of another OPC | ||
+ | |||
+ | Point Cloud Reference Resources | ||
* [[dev: | * [[dev: | ||
* [[dev: | * [[dev: | ||
- | * Mapping | + | * [[dev: |
+ | |||
+ | Mapping | ||
+ | * [[dev: | ||
===== Read Options for Ascii files ===== | ===== Read Options for Ascii files ===== | ||
Line 40: | Line 47: | ||
==== Strip Attributes ==== | ==== Strip Attributes ==== | ||
- | Options to remove | + | Options to exclude |
- | Removing | + | Excluding the source |
- | ==== Filter Points | + | ==== Filtering |
- | Option to filter point cloud to avoid extreme point density peaks and to obtain | + | The spatial filer option targets |
+ | A single point cloud point per Voxel will be retained. One Block has 64x64x64 Voxels. | ||
+ | |||
+ | ==== Classification ==== | ||
+ | |||
+ | Generate a dedicated OPC target file for each source point cloud class. \\ | ||
+ | More information about Point Cloud Classification, | ||
+ | * https:// | ||
+ | * https:// | ||
+ | * https:// | ||
==== Block Size ==== | ==== Block Size ==== | ||
- | The Block Size is a kind of cluster size for clustering | + | 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 | ||
* Auto define density by random samples for optimized performance. | * Auto define density by random samples for optimized performance. | ||
Line 56: | Line 73: | ||
* MLS (Mobile LiDAR Scan) / Medium density / Block size 1 | * MLS (Mobile LiDAR Scan) / Medium density / Block size 1 | ||
* ALS (Airborne LiDAR Scan) / Low density / Block size 50 | * ALS (Airborne LiDAR Scan) / Low density / Block size 50 | ||
- | * Custom block size. Choose a block size of your choice using the slider. | + | * Custom block size ((Once |
- | ==== Processing Time ==== | + | ==== Mapping Resources ==== |
+ | |||
+ | The write options for a point cloud that is part of a mapping resource in the pointcloud/ | ||
+ | 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: | ||
+ | |||
+ | |||
+ | |||
+ | ===== Processing Time ===== | ||
Importing a point cloud resource file to OPC is a one time process. \\ | Importing a point cloud resource file to OPC is a one time process. \\ | ||
Line 68: | Line 108: | ||
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. | 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. | ||
- | ==== Legend and Georeference ==== | + | ===== 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. | ||
+ | * 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/ | ||
+ | |||
+ | If the iModels requires this, the import Mapping Template can have the pointcloud.write.options.ini updated with: | ||
+ | |||
+ | | ||
+ | |||
+ | ===== Legend and Georeference | ||
The resource can be accompanied by an [[dev: | The resource can be accompanied by an [[dev: |
Last modified:: 2021/02/15 14:39