Understand Mobile Mapping data in Orbit

Orbit organizes mobile mapping data into runs and projects. A Project is a combination of one or more runs. A Run is a single import.
During import Orbit will optimize the data for performance. After import, point cloud and imagery can be used in a single access. No limitation on numbers or volumes.

The Orbit desktop solutions use Projects and Runs. The Orbit Publisher combines one or more project in a Publication.

All technical information about supported mobile mapping resources, see Supported Resources for Mobile Mapping.

Before importing the captured mobile mapping data, use the standard of your Mobile Mapping System to process and prepare the data.

Orbit's mobile mapping solutions require the mobile mapping resources to be properly captured, post-process and precisely documented.

Depending on the system or setup you are using, you will be collecting point cloud data with a certain density, range and accuracy, and/or imagery either 360° or planar or both. Mobile Mapping imposes that all captured data is post-processed with the GPS and IMU registrations synced with the lidar and imagery registrations. Here again, quality and accuracy of GPS and IMU influence the end result. To improve positional accuracy (due to poor or drifting GPS reception), some systems will use odometers, other require ground control points or other techniques.

In all cases, the captured Mobile Mapping data needs to be post-processed in order to achieve the accuracy you require for the job. The resulting data can then be prepared for import into Orbit solutions. It is strongly advised to have all data expressed in the same CRS.

Finally, an import template needs to be prepared that reflects the vehicle setup and used sensors.

From version 10.4 Orbit introduced the Multi-Resolution Orbit Point Cloud. This unique and very powerful technology makes it possible to view and unlimited point cloud files at once. No restrictions on file size nor functionalities.

To view point cloud data without a view depth restriction in the 3D View mode, the point cloud needs to be imported or in version 10.4 or higher.

A run may be the result of a one day drive, half a day or one hour. You may organize that as you wish, but each run is one separated import in Orbit.
Runs are stored in an open file structure. Each runs has one root directory and multiple sub-folders for each resource type and MMS sensor.
Trajectory, photo positions, bounding boxes and related metadata are stored in Orbit Vector File Tiled or Orbit Vector File, LiDAR data is stored as Orbit Point Cloud, other metada as XML.

The length or size of one single run are irrelevant to the use and performance of Orbit. There are no limits on the volume of the data nor the number or size of images.
Within one run the point cloud will be used as is. If the point cloud at a location is the result of multiple passes at that location, this entire combined point cloud will be used.

Runs :

• Contain the physical MM data.
• Require direct file access by the Orbit desktop application to be processed and used.
• The entire point cloud can be viewed at once.
• Are imported by the Orbit administrator using the desktop mobile mapping administration procedures, see Manage your Mobile Mapping Runs.
• Are only available for the Orbit administrator (for client-server setups), no permissions can be set.

Technical information about the run versions, see : Orbit Run Versions.

A project is a logical grouping of runs. You may organize that as you wish. Runs can be a part of several projects at the time. For example, all runs from the whole city, a highway, a given year, an area of interest, … .
Projects are just pointers managed by Orbit, to a list of runs known by Orbit.

The total number of runs is irrelevant to the use and performance of Orbit. There are no limits on the volume of the data as long good and fast data access is available.
Within one project the data of one run (point cloud and imagery) is always linked together. When overlaying the point cloud on top of an image point clouds from the other composing runs will not be displayed nor used for measurements.

Projects :

• Do not contain the physical MM data, it is just a list of imported runs.
• Do not require direct file access by the Orbit desktop application to be used.
• The entire point cloud can be viewed at once solely if direct file access is available. Point cloud measurements and overlay are always possible.
• Are managed by the Orbit administrator using the desktop mobile mapping administration procedures, see Manage your Mobile Mapping Projects.
• Are available for operators and users (read only) if permissions are granted by the administrator.

Publications :

• Do not contain the physical data, it is a list of parameters and configurations.
• Do not required direct file access to be used.
• Entire point cloud viewing is not supported. Point cloud measurements and overlays are possible.
• Are managed by the Orbit administrator via the EOS Console > Publish.
• Are available for users (read only) if permissions are granted by the administrator.