This is documentation of an archived release.
For documentation on the current version, please check Knowledge Base.

Customized Mobile Mapping Run, version 1 / 10.4

Configurations of an Orbit Mobile Mapping Run or import template.

Panorama.ini

Parameter Necessity Fall back value Description
project.type essential not applicable Type of mobile mapping data.
generic - topcon - …
PANORAMA.LOCATION.PREFIX optional ./images/ Prefix and suffix for accessing the image files on disc (prefix&PHOTOID&suffix)
PANORAMA.LOCATION.SUFFIX optional .jpg
PHOTO.CAMERA.HEIGHT optional 2.0 Height of camera above the ground.
Used to calculate an approximated Z for 2D objects on panorama or point cloud overlay.

panorama_positions_panorama.ini

<PARAMETER>.ATTRIBUTESET.NAME
<PARAMETER>.ATTRIBUTE.NAME

Parameter Necessity Fall back value Description
PHOTOID essential not applicable Name of the jpg image in the images sub directory
NORTHPAN optional 0 Value for image pan.
NORTHTILT optional 0 Value for image tilt.
NORTHROLL optional 0 Value for image roll.
PHOTOCENTERX optional spatial X
from photo position object
Value for photo position X
PHOTOCENTERY optional spatial Y
from photo position object
Value for photo position Y
PHOTOCENTERZ optional spatial Z
from photo position object
Value for photo position Z
PHOTO.ORIGIN.X optional 0.5 Value in the range of 0.0 to 1.0 that specify the pixel on the horizontal axis in the panorama image
that need to be used to apply all image orientation angles (pan, tilt and roll)
PHOTO.ORIGIN.Y optional 0.5 Value in the range of 0.0 to 1.0 that specify the pixel on the vertical axis in the panorama image
that need to be used to apply all image orientation angles (pan, tilt and roll)
POINT.CLOUD.DATASET.NAME essential not applicable Name of the dataset in the current folder.
From version 10.1 default point_cloud.ocp
Before version 10.1 default point_cloud.ovt
TIMESTAMP optional no Displayed timestamp attribute in left lower corner on panorama image.

If (Timestamp > 900,000,000) and (Timestamp < 2,000,000,000) and (Timestamp = Integer value) then Orbit will read the value as GPS time and will show the well-known UTC syntax : GPS time 2,000,000,000 will be displayed as 2043-05-23 03:33:04.
Note that leap seconds are not taken into account, read Wikipedia, GPS Timekeeping and Wikipedia, Leap seconds.

panorama_positions.ord

In the panorama_positions.ord file it is possible to calculate the attributes values using the Orbit attribute rules : Attribute Formulas

text_import.ini

The point cloud import configuration file makes it possible to define the structure of an Ascii file used as point cloud resource file.

.pts files

ColumnNames x;y;z;i
Separator 32

.xyz files

ColumnNames x;y;z
Separator 32
 
Last modified:: 2022/04/15 06:19