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 version of the Orbit Run structure.
It is recommended to read first Understand Mobile Mapping data in Orbit and Manage your Mobile Mapping Runs.
An Orbit run version 3 uses the “orbit_mm_run.omr” file as central resource file.
This latest version has been developed for optimized performance and to use the new tools of the Orbit Mobile Mapping Content Manager.
The current structure is in place since Orbit version 11.0.
Structure updates compared to run version 2 :
Advantages of an 11.0 run:
Next to the advanced import configurations templates some basic runtime configurations are stored in the central Orbit run file : “orbit_mm_run.omr”.
Edit and save using a standard text editor, e.g. Notepad.
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.
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 or Panorama Ortho 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.