This page describes some technical information about the Orbit mobile mapping Run files and structure.
Orbit is constantly improving tools and software which may result in an update of the files and structure of an Orbit mobile mapping Run.
Backwards compatibility is guaranteed. A newer Orbit release supports mobile mapping runs imported in a previous Orbit version. However to take advantage of new feature updates it may be required to use the latest Orbit run version.
It is strongly recommended to read first Concepts about Mobile Mapping data in Orbit.
An Orbit run version 3 uses the “orbit_mm_run.omr” file as central mobile mapping run resource file.
Run version 3 has been developed to optimize performance and to use new tools of the Orbit MM Content Manager.
Structure updates compared to run version 2 :
All advanced technical configurations related to the used resources and mobile mapping system are managed via the import template and applied on import, so called “Import configurations”.
Some additional configurations can be added or updated after import, so called “Optional configurations”.
An Orbit training is required to create and update your proper import configuration files. Contact sales at orbitgt dot com.
Add/edit and save the listed files using a standard text editor (e.g. Notepad).
The Orbit run identifier file (required).
<Orbit Run directory>/orbit_mm_run.omr
Camera height
photo.camera.height
Height of camera above the road surface expressed in meters, use dot as decimal separator. This height is used to display 2D vector data in the 3D mobile mapping views and for the point drop measure function.
Image file extension
photo.file.extension
File extension of original images, default “jpg”. However any supported image resource can be used, see Supported Geodata Resources.
Simplified trajectory
simplified.trajectory.maximum.distance
simplified.trajectory.part.separation
photo.sequence.key
At import photo positions or trajectory the trajectory simplified (coverage) will be created automatically if not yet exists. The above settings can be used to adjust the defaults, as used in the example below.
Example
version 3 project.type generic project.file orbit_mm_run.omr photo.camera.height 2.20 simplified.trajectory.maximum.distance 1 simplified.trajectory.part.separation 10 photo.sequence.key OrbithPhotoId fixed.local.crs {PARAM_CRS} template.parameters=PARAM_CRS
The image redirect file (optional) 1).
<Orbit Run directory>/<camera>/original/link.ini
<Orbit Run directory>/<camera>/processed/link.ini
Redirect images
To avoid file copy into the appropriated Orbit run folder structure a single line ascii text file can be used to specify the image file path prefix. The file path prefix combined with the OrbitFileName attribute value will be used as file pointer.
Example
\\192.168.0.1\images\
An Orbit run version 2 uses the “orbit_mm_run.omr” file as central mobile mapping run resource file.
Run version 2 has been developed to optimize performance and to use new tools like Optimize Imagery of Mapping Run and Process Point Cloud Image.
Structure :
An Orbit run version 1 uses the “panorama_positions.ovf” file as central mobile mapping run resource file.
Structure :
A new import using a run template version 3 is required.
A version 2 point cloud can be selected as source file to import your new run.
A new import using a run template version 2 is required.
A version 1 point cloud can be recovered, copy ../pointcloud/processed/*.opc and *.opcmr files to your new run.