This is documentation of an archived release.
For documentation on the current version, please check Knowledge Base.

Orbit Point Cloud

An Orbit Point Cloud (*.opc) is Orbit's native point cloud storage format.

Structure

It is a single file grouping both spatial and attribute component.

Reasons to use

The OPC is been developed for encoding, fast viewing and querying using Orbit's 2D and 3D tools and map engine. This very powerful and unique technology makes it possible to view and use unlimited point cloud files at once without loading :
Navigate in mobile mapping 3D point cloud view

Create and Update

The Orbit processes raw point cloud file(s) into a multiresolution Orbit Point Cloud (*.opc).

There are several ways to create OPC files:

Importing a point cloud dataset is a one time process and will take some time. Processing time is affected by :

  1. Storage format of original data.
  2. Computing power, 64bit is recommended.
  3. Orbit installation (64bit or 32bit) and memory configuration.
  4. Speed of Access to source data and target location.

Example import of 292.258 million point cloud points using Orbit 10.5.1, 64Bit, 4GB Memory, read and write on SSD

  • Las - 5.44 GB : 8m 31s (reading) + 4m 42s (writing)
  • Laz - 675 MB : 39m 46s (reading) + 4m 42s (writing)
    Reading Laz = 4.67x Reading Las. It is all about compression and decompression.

Related documentation :

The import procedure displays the progress bar of the current import phase (Reading, Writing or Writing Multi-resolution). The time required for each phase depends the above listed topics. You may wish to do this overnight for very large point cloud datasets or using the Task Manager.

Legend and Georeference

The resource can be accompanied by an Orbit Legend File and Orbit Resource Descriptor.

 
Last modified:: 2019/03/25 11:36