Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
dev:technology:supported_formats:pointcloud:opc [2022/09/09 08:08] paulien [Write Options] |
dev:technology:supported_formats:pointcloud:opc [2024/03/29 20:52] glen [Legend and Georeference] |
||
---|---|---|---|
Line 92: | Line 92: | ||
write.attribute.intensity=true | write.attribute.intensity=true | ||
intensity.8bit=true | intensity.8bit=true | ||
- | write.attribute.classification=true | + | write.attribute.Classification=true |
For this configuration: | For this configuration: | ||
Line 105: | Line 105: | ||
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. | ||
+ | |||
+ | ===== 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/ | ||
===== Legend and Georeference ===== | ===== Legend and Georeference ===== | ||
The resource can be accompanied by an [[dev: | The resource can be accompanied by an [[dev: |
Last modified:: 2024/05/07 12:36