This is documentation of an archived release.
For documentation on the current version, please check Knowledge Base.
For documentation on the current version, please check Knowledge Base.
Prepare MM data Generic Import
This page describes how to prepare mobile mapping resources for a generic import.
Using the generic Orbit import templates prepared mobile mapping resources can be imported into Orbit.
It is strongly recommend to read first Understand Mobile Mapping data in Orbit.
Trajectory
Currently not supported on generic import.
Imagery
Panoramas
Image files
- Image type : equirectangular panoramas
- Image resolution : ratio 2×1
- Files : *.jpg files, each image is one jpg file
- File name : exactly as “Filename” value of photo position file, see below
- Folder structure : all files in one folder
Image positions and orientations file (projected, pan-tilt-roll)
- Files : one asccii *.txt or *.csv file
- Rows : each image is one record
- Columns : tab separated (char9), headers, with exact order as the example below
- Value “Filename” : file name as on disk, without file extension
- Value “X”, “Y” : any supported coordinate system can be used, but all mobile mapping resources should have the same crs
Filename X Y Z Pan Tilt Roll Timestamp Brussel_1000000 4.404878286326054 50.85106227753124 128.33142823723782 88.132974310915699 0.095102381910084 -359.06942401248796 0 Brussel_1000001 4.404918241374241 50.85107702770032 128.37570893339338 39.507857332631851 -1.084923642050256 -359.32845731111627 1 ...
Planars
Image files
- Image type : rectified images
- Image resolution : camera calibration setting
- Files : *.jpg files, each image is one jpg file
- File name : exactly as “Filename” value of the photo position file, see below
- Folder structure : all files in one folder
Image positions and orientations file
See above, image positions and orientations file for panoramas.
Camera specifications
- SensorPixelSize : physical size of pixels on the sensor CCD, expressed in mm
- SensorPixelCountX : number of pixels in widht of the camera sensor and image
- SensorPixelCountY : number of pixels in height of the camera sensor and image
- SensorPixelPPX : principal point value along the sensor width
- SensorPixelPPY : principal point value along the sensor height
- FocalLength : focal length of the lens, expressed in mm
For every camera it is required to review and adjust the default Orbit template camera calibrations, prior to the import.
<Orbit installation directory>/program/ext/mobile_mapping/project/template/<template name>/planar<1,…>/import/import_locations.ord
LiDAR
Point cloud files
- Files : one or more supported LiDAR resources
- File name : free of choice
- Latitude, Longitude : any supported coordinate system can be used, but all mobile mapping resources should have the same crs
- File structure if point cloud file is imported as *.txt or *.csv file
- Flat ascii text file, comma or tab separated, column headers, with exact columns : X, Y, Z, R, G, B, I
- R, G, B, I value ranges 0-255, values may be empty
- All lines are terminated by a carriage return char(13) / newline char(10) sequence
- Name of headers are not free of choice
Longitude Latitude Z R G B I 4.40487692010655 50.8510926423286 125.763312461527 16 17 19 46 4.40487698750245 50.8510916370433 125.761583937394 16 17 19 46 ...
Last modified:: 2019/03/25 11:36