Concepts of Mobile Mapping and UAS data in Orbit

To use mobile mapping data in Orbit, the raw data needs to be imported and processed into an Orbit Run using a corresponding import template.

Orbit imports and organizes mobile mapping data into runs, projects and categories.

• A Run is a single import.
• A Project is a combination of one or more Runs used by Orbit Desktop products.
• A Category is a combination of one or more Projects used by an Orbit Publisher products.

A complete overview of all supported mobile mapping resources, see Supported 3D Mapping Resources.

Depending on the mobile mapping system or setup you are using, you will collect trajectory, point cloud data and imagery either 360° images, planar images or both.
Before importing the captured mobile mapping data, the standard tools of your system should be used to prepare, correct, process and export the data. Mobile mapping imposes all captured data is correctly post-processed into a single reference frame.

Finally the prepared resources will be imported and converted into an Orbit Mapping Run using an according Import Template. The Import Template reflects exactly the structure of prepared resources, vehicle setup and used sensors.

• 3D Mapping Data Preparation and Import Templates
• Import 3D Mapping Data

• Organize
  A Run is the result of one import.
  At import, all resources are organized into one root folder. For each sensor or resource type there is a dedicated sub folder.
  Manage Mobile Mapping Runs
• Optimize
  At import, resources are optimized for performance and stored in Orbit's optimized native storage formats. After import CPU requirements are reduced to an absolute minimum for efficient and performant use of huge datasets on regular devices.
• Coordinate System
  Any supported coordinate system can be used.
  It is recommended that all resources of a run do have the same coordinate system. If required CRS conversions can be applied upon import using a proper template configuration.
• Size & Volume
  If runs are imported correctly, the length of trajectory or size of a single run is irrelevant to the performance in Orbit. There are no limitations on volume, size or resolution of point cloud and imagery.

• File access
  To import, process and use Runs direct file access is required by the Operating System User for Orbit Desktop products or for the Orbit Service user account for Orbit Publisher. Fast file access is required.
• Permissions
  Runs are available for administrators only, no user permissions can be set.
  Don't worry if you are using a standalone product, you are the administrator.
• Viewing
  There are no limitations on image nor point cloud viewing.
  The point cloud legend can be edited for both Map¹⁾ and Tabs²⁾.

• Create
  Projects are pointers to a list of Runs known by Orbit. Runs can belong to multiple projects, see Manage Mobile Mapping Projects.
  For example grouping by geographical area, mapping project, date or year, … .
  
• Coordinate System
  Run resources of the same type must have the same coordinate system. Convert CRS on import Run if required.
• Size & Volume
  If Runs are imported correctly, there are no limitation on volume nor size of Projects.
  Theoretically there is no limitation on the number of Runs combined by one Project, however make a wise decisions. Merging and optimizing Runs would be preferred in stead of combining thousands of Runs into one Project.
• Storage
  Projects are just pointer files and do not included data.

• Permissions
  Administrators have access to projects and can set user permissions to restrict access to projects. In Client-Server and Publisher users have a well defined role and level of use.
• Data matching
  Images and point clouds of all included Runs will be combined on the fly by resource type (trajectory, photo positions, point cloud) into a single master dataset.
  For example the entire combined project point cloud dataset will be used at all time for measuring, viewing or overlaying on images.
  
• Viewing
  There are no limitations on image nor point cloud viewing when having direct file access to the original Runs.
  The point cloud legend can be edited for Tabs³⁾ only. It is not possible to edit the Project point cloud legend on the Map⁴⁾ On the Map to original Run point cloud legend is used.
  If desktop user don't have direct file access to Runs viewing mobile mapping Projects is restricted to imagery only. Point cloud overlay and point cloud measurements on images remain possible.

• Create
  Categories are part of an Orbit Publication and managed by an administrator via the EOS Console, see Orbit MM Publisher.
• Coordinate System
  Project CRS is inapplicable for Categories, any crs combination is supported.
• Size & Volume
  If runs are imported correctly, there are no limitation on volume nor size of Categories.
  Theoretically there is no limitation on the number of Projects combined by one Category, however make a wise decisions.
• Storage
  Categories are just pointers and do not included data.

• File access
  No direct file access is possible. Categories and its including data are available as services, see Mobile Mapping Publisher.
• Permissions
  No Category permissions can be set. A user can access a Publication and its including Categories if the user has permissions to view at least one of the included Projects. However if a user can acces a Category, the user will only be able to view mobile mapping data of Projects for which permissions have been granted.
• Data matching
  Images of all included Runs will be combined on the fly into a single image dataset. But for point cloud overlay and point cloud measurements on images the point cloud of the according Run of the image will be used.
• Viewing
  Viewing is restricted to spherical imagery only. Point cloud overlay and point cloud measurements on images are possible as well.