====== Manage your Mobile Mapping Runs ======

This page describes the desktop mobile mapping administration procedures to manage your runs. \\
It is recommended to read first the Orbit concepts about mobile mapping data : [[110:mobile_mapping:about_mm_resources|]].

===== Open Run =====

**Open an available run / an imported run** 

A successfully imported run is available for the administrator for viewing via the "Open Run" procedure. 

{{orbitgis:how_to_find.png?25&nolink |}} Procedure > Administration > Mobile Mapping > Open Run

===== Import Run  =====

**Import a raw set of data**

To use mobile mapping data in Orbit, the raw data needs to be processed into a "run" using an "import template". \\
The administration procedure "Import Run" (previously "Create Run") allows the Orbit administrator to import a raw set of mobile mapping data. 

The import procedure will be different depending the selected import template according the type of Mobile Mapping data. All import configurations like the available components, camera heights, calibrations and coordinate systems are stored within this template. \\
It is necessary to prepare and structure the data properly in accordance to used import template : [[110:mobile_mapping:desktop:mobile_mapping:manage:import:templates|]]. All 

The Import Run procedure is not available for Orbit MM Explorer. \\
The Explorer is not able to import and process raw data. Data must be processed as Orbit Run to be added into an Explorer.

{{orbitgis:how_to_find.png?25&nolink |}} Procedures > Administration > Mobile Mapping > Import Run \\ [[110:mobile_mapping:desktop:mobile_mapping:manage:import:index|]]

===== Add Run ====


**Add / Append a processed Orbit Run**

The "Add Run" procedure can only be used by the administrator to append an Orbit processed run to the list of available runs in Orbit. \\ 
In other words, this procedures allows the Orbit administrator to point where the mobile mapping run is physically stored. 

If you are adding an Orbit processed run it will not be required to re-process photo positions and point cloud \\
The Add Run procedure is the only way to get mobile mapping data into an Orbit MM Explorer.

{{orbitgis:how_to_find.png?25&nolink |}} Procedures > Administration > Mobile Mapping > Add Run \\

  * **Run** \\ Browse and select the orbit_mm_run.omr file in the root directory of the entire run. This file *.omr file represent the Orbit Mobile Mapping Resource.  \\ To add an Orbit processed run from version 10.4 or older, select the panorama_positions.ovf file in the root directory.
  * **Name** \\ The name field will be filled in automatically after selecting the .omr file. \\  This name is a label for the run in Orbit. If required the name can be changed, it will not change the run directory name itself. 

===== Edit Run =====

**Re-import data to the opened Run**

The "Edit Run" procedure can be used only by the administrator if a run is opened to re-import data to the opened run.  

  * Photo Positions : New import will always replace previous import
  * Point Cloud : New import will replace a previous import only if the new imported file has the same new as an earlier import. \\ An import file with a different name will be added to the run.
{{orbitgis:how_to_find.png?25&nolink |}} Procedures > Administration > Mobile Mapping > Edit Run \\ For more information, review documentation on Import Run above. 

===== Remove Run =====

**Remove a Run from list, no data will be deleted**

The "Remove Run" procedure can only be used by the administrator to remove a run from the list with available runs. \\ 
This procedure will never remove the original data nor the Orbit processed data. It only removes the connection between application and data. \\
This to avoid removing hours of data with a single click. But it can be required to remove the run from the list in Orbit for example if the data has been moved.

{{orbitgis:how_to_find.png?25&nolink |}} Procedures > Administration > Mobile mapping > Remove Run