====== Import Mobile Mapping data in Orbit ======

This page describes how to use the desktop mobile mapping administration procedure "Import Run". 

The "Import Run" procedure imports and processes a set of raw mobile mapping resources according a well defined [[111:mobile_mapping:desktop:core:manage_import:templates|Orbit import template]] into an Orbit Run. \\
If you have one ore more already processed Orbit Runs you would like to add to your installation use the "[[111:mobile_mapping:desktop:core:manage:runs#add_run|Add Run]]" procedure. 

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

The import procedure consists out of 2 consecutive wizards :
  - Create a new Orbit Run directory
  - Import data according the selected template \\ The structure of the second wizard depend on the selected import template.

===== Create Run definition =====

{{  importrun_create.png?nolink&300|}}

**Name** \\ 
Enter a name for the run. \\ Only letters, numbers, dashes - and underscores _ are accepted.  \\
Special characters (like é # + & / * ...) are not allowed and will be replaced automatically into an underscore _. 

**Setup** (previously "Type") \\
Choose your import template. Read more about templates and customized import confiugrations : [[111:mobile_mapping:desktop:core:manage_import:templates|]]

**Directory** \\
Browse and select the directory where the new run and data will be stored. \\
A new run sub-directory will be created to group all files and directories belonging to the run. \\
If an already processed Orbit run directory or sub-directory is selected, Orbit will recognize the run and will just open that run. \\
Considerations :
  * While importing local resources (point clouds, imagery) Orbit will process the data into the Orbit Run folder. Be sure that there is enough disc-space and fast disc access to reduce the import process time.
  * When using Orbit Mobile Mapping in Client Server special attention is required for data management, storage, file access, system file permissions and network connectivity : [[111:mobile_mapping:desktop:core:manage:manage_mobile_mapping_cs|]].

**Create Run** \\
Click "Create Run" button to confirm. \\
The 2nd wizard to import the raw data will start automatically depending the selected template and type of mobile mapping data your are importing.

<note tip>The available steps in the second wizard, documented below, depend on the selected import templates.</note>

===== Import data =====

==== Import Trajectory ====

Use the "Choose File" button to browse and select the file containing the trajectory information.  \\
The import will start automatically after selecting the file. If the import is successful, proceed to the next step.

A trajectory is optional. Even if your template includes the import of a trajectory, you may wish to this step.

==== Import Imagery ====

{{  importrun_image.png?nolink&300|}}

**Import Positions** \\
Use the "Choose File" button to browser and select the file containing the positions of the currently imported camera. The import will start automatically after selecting the file. If the import is successful, proceed to "Move Images". \\
If the positions are already imported a new import will replace the previously imported positions. 
 
**Move Images**\\
Move or copy the image files to the indicated directory within the Orbit Run structure : <Orbit Run directory>/<camera>/original/. \\
Optionally an image redirect file can be used to avoid data copy, see l[[111:mobile_mapping:desktop:core:manage:runs_version|]]. 

**Datastructure / CRS**\\
This photo position file needs to be exactly as described by the used import template : data structure, column sequence, type of coordinates, coordinate reference system. If required contact your data supplier or Orbit administrator to adjust. 

==== Import Point Cloud ====

{{  importrun_pointcloud.png?nolink&300|}} 

**Import point cloud** \\
Since [[111:mobile_mapping:desktop:updates:update_1040|update 10.4]] Orbit processes a multi-resolution point cloud, read [[:technologies:resources:lidar:opc#Orbit Point Cloud processing|]].

"Choose File" \\
Use the "Choose File" button to browse and select the file(s) containing the point cloud information. \\
Use the Ctrl and Shift to select multiple point cloud files to be imported together. \\
All selected files must be exactly as described by the selected import template.

"Update" \\
The "Update" button will only be enabled for runs without a multi-resolution point cloud.

Re-Import of Point Cloud \\
If a point cloud is already imported a new import will replace the previously imported point cloud with the same internal name :
  * one resource file : Orbit internal name = file name
  * two or more resources file : fix Orbit internal name. \\ A new import will always replace a previous multiple file import.

**Datastructure / CRS**\\
These point cloud files need to be exactly as described by the used import template : data structure, column sequence, type of coordinates, coordinate reference system. \\
If required contact your data supplier or Orbit administrator to adjust. 

**Finish** \\
Because the point cloud import can take some time, it is the last step of the procedure. Start the point cloud processing if there is enough time to do so. \\ For example you can start the point cloud import just before leaving the office. Next day you can enjoy the results. \\
Since update 10.5 a newly imported point cloud is directly available.