Manage Mapping Runs

This page describes the desktop administration procedures to manage your mapping runs.
It is strongly recommended to read first Orbit Mapping Resource.

Procedures > Administration > Aerial, Mobile or Oblique Mapping > XXX

• A previously opened Run or Project will be closed and the selected run is opened.
• Search and filter the list of available Runs.
• Open the selected Run via the according button or just double click the name in the list.

• Add one or folder containing multiple ready to use Orbit Runs to the application's list of available Runs.
• The original data doesn't need to be re-processed.
• The Add Run procedure is the only way to get mobile mapping data into an Orbit MM Explorer.

• Run
  Browse and select the orbit_mm_run.omr file in the root directory of the Orbit run folder.
  For runs of version 1, select the select the panorama_positions.ovf
• Name
  The name of the Run as on disk is used automatically after selecting the omr file. This name can no longer be changed to avoid any confusion or mistakes due to a different names on disk and in Orbit.

• The import procedure differs depending the selected import template representing the Mapping resources to import.
  All import configurations like available resources, sensors, sensor specifications and coordinate system are configured and defined by this import template.
• It is required to prepare the data properly according the template specifications, see Mapping Resource Import Templates.

Complete documentation on the Import Run procedure, see Import Run.

• Import & Process Run is activated when original data is available in the mapping run and the corresponding mapping resource hasn't been imported yet.
• Every mapping resource has specific conditions to import & process:

(1) No point_cloud.opc file in the pointcloud directory
(2) One or more original files in the pointcloud\original directory. A priority list defines in which order formats are checked: las, pod, laszip, e57, txt. The link.ini file can be used to direct to another directory including the original pointcloud files.

(1) No locations.ovt file in the camera directory
(2) import_locations.csv in the <camera>\import directory

(1) No trajectory.ovf file in the trajectory directory
(2) A csv or xml in the trajectory\original directory

(1) No dtm.omi file in the dtm directory
(2) One or more image files in the dtm/original directory

(1) No ortho.omi file in the ortho directory
(2) One or more image files in the ortho/original directory

(1) A mesh.json file in the mesh directory
(2) Missing ord, ini or 3dtiles files in the mesh directory

(1) No trajectory_simplified.ovt file in the simplified_trajectory directory

(1) No envelope.ovf file in the envelope directory

(1) No metadata.xml file in the metadata directory

• Update mapping resources of the opened Run by re-importing original data files.
• The initially imported mapping resources are replaced upon importing the new files. If only the photo positions file is re-imported, then the initial point cloud resources aren't replaced and visa versa.
• This procedure is inactive if no Run is opened.

For more information, review documentation on Import Run above.

A bug prevents update of a point cloud via this procedure.
To do so apply following workaround.
Delete the existing <Orbit Run>/pointcloud/point_cloud.opc manually prior to Open and Edit Run.
This issue is fixed by version 18.0.

• Close the mapping run and remove the corresponding mapping resources from the datasetlist.
• This procedure is inactive if no run is opened.

• The selected Run is removed from the application's list of available Runs.
• The removed Run is deleted from all Projects it belongs.
• The data files as stored on disk is not deleted, no data is removed from disk.