Orbit Mapping Resources - Structure and Configs

This page describes basic technical configurations of Orbit Mapping Runs and Oblique Projects.
It is strongly recommended to read first about_resources.

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”.

Orbit is constantly improving tools and software which may result in an update of the files and structure of an.
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.

An Orbit Run version 3 uses the “orbit_mm_run.omr” file as reference resource file.
This updated structured has been developed to optimize performance and to use new tools of the Orbit 3DM Content Manager and 3D Mapping Cloud.

Structure updates compared to run version 2 :

• Point Cloud : ../pointcloud/point_cloud.opc
• Trajectory : ../trajectory/trajectory.ovf
• Simplified Trajectory : ../trajectory_simplified
• Trajectory Adjustments : ../trajectory_adjustment

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_formats.

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.

• maximum.distance : coordinate will be added if its perpendicular drop distance to the segment between previous and next coordinate is larger than maximum.distance (meter).
• part.separation : two consecutive original coordinates won't be connected if segment length is larger than part.separation (meter).
• photo.sequence.key : Initial sort of coordinates before connecting to lines is based on the string value of the photo.sequence.key attribute(s). Add prefix zero characters to obtain expected sort when using integer value as sort reference. A combination of attribute values can be used as well, e.g. OrbitTimeStamp+ObjectId.

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) ¹⁾.
<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\