Import Run

This page describes the desktop administration procedures “Import Run”.

Procedures > Aerial / Mobile / Oblique Mapping > Import Run

It is recommended to read first Orbit Mapping Resource.

The “Import Run” and “Import Project” procedures import and process a set of raw mapping resources according a well defined Orbit Import Template into an Orbit Mapping Run.

The “Add Run” and “Add Project” procedures can be used to link immediately already imported Orbit Mapping Runs to the Orbit setup.
More information on Add, Remove and Manage Runs, see Manage Mapping Runs.

The import procedure consists out of 2 consecutive wizards :

1. Create a new Orbit Run definition.
2. Import data according the selected Import Template.
   The available steps of this second wizard depends on the used Import Template.

Specify the directory where the new Run needs to be stored.
Remarks :

• Do not create a new Run inside an existing Run folder. If you do so, Orbit will recognize the structure and will Open the Run upon Create Run, see below.
• The original data will be organized and processed into the specified directory. Ensure fast access to storage access and sufficient disk space.
• On using Client/Server, special attention is required regarding data management and file access, see Manage Mobile Mapping in Client-Server.

Enter the Run name.
Only alphabet characters, numbers, space, dash and underscore are accepted.
Special characters (like é # + & / * …) cannot be used and are replaced automatically into underscore.

Select the Import Template to be used.

Use the according buttons to add, remove or get access to template download page.

• default available generic templates cannot be removed.
• download, unzip and point the *.omr file to add a new template.

Depending on the used Import Template, it might be required to select the coordinate system of the original import files. Do not use a Geographic template to import Projected resources and vice versa.

• For a geographical template, no CRS needs to be entered.
• For a projected CRS, the coordinate system of the original data to be imported needs to be entered.
• For original data in non-metric units of measurement, a conversion to the metric system is required upon import.
  • Source: the original non-metric CRS needs to be entered.
  • Target: the corresponding metric CRS needs to be entered.
• For original data in a metric system, the source and target CRS needs to be identical.

More information on Import Templates, see Mapping Resource Import Templates.

Click “Create Run” button to confirm. Upon confirmation the 2nd wizard to import data will start.

The below documentation describes the import of local resources.
The wizard and parameters to establish a connection to an online service are dedicated for each provider.

Import trajectory file.

Import photo positions file and move images of the current camera to the indicated directory: <Orbit Mapping Run>/<camera>/original/. Optionally an image link.ini redirect file can be used to avoid data copy, see Orbit Mapping Resources - Structure and Configs.

Repeat this for each available camera.

Import point cloud files by selecting the point cloud file(s). Choose to delegate the optimization to the task manager or directly start processing. All selected point cloud files will be merged into one Orbit Point Cloud file.

Import blur, erase or object annotations.

• XML/CSV per Run: There is one csv or xml file to be selected in which all annotations are described. An xml file is created for every original image.
• XML per Image: One xml file is available for every original image. Copy the xml files to the indicated directory.

Import Digital Elevation Model

• Estimated local ground height: Enter the estimated height of the local ground. This parameter will be used as default ground height for displaying the oblique imagery where there is no DEM coverage.
• Missing sample value: Insert the missing sample value (background value) of the DEM file.
• Choose file: Choose the DEM raster file. When clicking the “Open” button the DEM will be processed.
  

To overwrite the DEM file just choose the correct DEM file again. DEM is used to calculate image footprints so in case the DEM is overwritten it is recommended to reprocess footprints.

Open the metadata properties window of the mapping resource to autofill or complete the metadata.

Update the envelope and the simplified trajectory according to the current photo positions, trajectory and pointcloud.