For documentation on the current version, please check Knowledge Base.
This is an old revision of the document!
Orbit Mapping Resources - Structure and Configs
This page describes basic technical configurations of Orbit Mapping\UAS Runs and Oblique Projects.
It is strongly recommended to read first
Concepts
Import Templates
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”.
Backwards compatibility and New Features
Orbit is constantly improving tools and software which may result in an update of the files and structure of an Mapping Run\Project.
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.
An Orbit Oblique Project version 3 uses the “orbit_oblique.oop” file as reference resource file.
This updated structure has been developed to optimize performance and to use new tools of the Orbit 3DM Content Manager and 3D Mapping Cloud.
For previous version or to convert existing runs\projects into the updated structure, see Orbit Run Versions.
Mapping Run Version 3
The current structure is in place since Orbit version 11.0.
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
Configurations for Mapping\UAS Runs and Oblique Projects
Add/edit and save the listed files using a standard text editor (e.g. Notepad), respect file formatting and structure.
Redirect image file directory
To avoid file copy into the appropriated Orbit run folder 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.
- File :
./panorama<x>/original/link.ini
./panorama<x>/processed/link.ini
./planar<x>/original/link.ini
./planar<x>/processed/link.ini
- Parameter : not applicable
- Values : directory path
- Default Value :
- Example
\\192.168.0.1\images\
Original image file extension
Used image storage format of original images (panorama or planar).
- File : <Orbit Run>/orbit_mm_run.omr (orbit_oblique.oop for Oblique Project)
- Parameter :
photo.file.extension
- Values : Any supported image resource can be used, see supported_formats.
- Default Value : *.jpg
Camera Parameters
Height of the camera above ground 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.
- File : <Orbit Run>/orbit_mm_run.omr (orbit_oblique.oop for Oblique Project)
- Parameter :
photo.camera.height
- Default Value : 2.2
- Unit : meters
2D Vector Visualization Parameters
Possible range of the offset of 2D vector data to the height of the photo position (presented as a slider in the vector overlay parameters pop-up of the photo viewer).
- Parameters :
data2d.overlay.min.offset
data2d.overlay.max.offset
- Default value : 5
- Unit : meters
Mostly need to be changed for UAS Runs depending on the flying height.
Configurations for Mapping Runs Only
Camera height
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.
- Parameter :
photo.camera.height
Simplified Trajectory
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.
Coordinate will be added if its perpendicular drop distance to the segment between previous and next coordinate is larger than maximum.distance (meter).
- Parameter :
simplified.trajectory.maximum.distance
- Values : Inter value, units meter.
- Default Value : 1
Two consecutive original coordinates won't be connected if segment length is larger than part.separation (meter).
- Parameter :
simplified.trajectory.part.separation
- Values : Integer value, units meter
- Default Value : 10
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.
- Parameter :
photo.sequence.key
- Values : Any photo position attribute, a combination of attributes can be used, e.g. OrbitTimeStamp+ObjectId.
- Default Value : OrbitPhotoId
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
Configurations for Oblique Projects Only
orbit_oblique.oop
reference.z
Mean terrain height. The value is used as a fall back value for the areas with missing DEM
- Unit : meter
- Default value : na
reference.pan
Photo orientation offset (heading) between the reference north direction and the actual north flying axis.
- Unit : degrees
- default value : 0°
- Positive rotation : clockwise
near.margin
Photo orientation maximal deviation (heading) from the corrected reference directions (see above reference.pan) and the according flying axes (north, east, south, west).
- Unit : degrees
- Default value : 10°
- Positive rotation : not applicable as this is an absolute value