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

Prepare MM Data Optech

This page describes the Optech Lynx resources to be imported into Orbit using the according Orbit MM import template.
It is recommended to read first Understand Mobile Mapping data in Orbit.

Trajectory

Currently no trajectory export available.

Panoramas

Images

  • Image type : Ladybug 3 or Ladybug 5, equirectangular panoramas
  • Image resolution : ratio 2×1, 8000×4000 advised for Ladybug 5, 5400×2700 for Ladybug 3
  • File format : 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

Positions, orientations and metadata

  • File format : one asccii *.txt file
  • File structure Rows: each image is one record
  • File structure Columns : tab separated (char9), headers, with exact order as the example below
  • Value “GPS Time” : GPS week time, seconds from last Sunday 00:00:00, decimal notation
  • Value “Image Filename” : file name as on disk, with file extension
  • Value “East”, “North”, “Height” : any supported projected coordinate system
GPS Time	Image Filename	East	North	Height	Omega	Phi	Kappa
392074.509200	091208023637_LB-000000_000198.jpg	618960.017800	4848048.148000	152.792627	1.670330000	-0.258230000	-126.202420000
392075.509200	091208023637_LB-000000_000199.jpg	618960.056400	4848041.665000	152.664546	1.250657000	-0.680602000	-125.052279000
392076.509200	091208023637_LB-000000_000200.jpg	618960.199500	4848033.737000	152.529065	2.051135000	-0.734158000	-125.244292000
...

Planars

Image files

  • Image type : JAI distorted images
  • Image resolution : default 2058×2456 pixels1)
  • File format: each image is one *.jpg file
  • File name : exactly as “Filename” value of photo position file, see below
  • Folder structure : all files of each camera in a separated folder

Positions, orientations and image metadata

  • File format : one asccii *.txt file for each camera
  • File structure Rows: each image is one record
  • File structure Columns : tab separated (char9), headers, with exact order as the example below
  • Value “GPSTime” : GPS week time, seconds from last Sunday 00:00:00, decimal notation
  • Value “Filename” : file name as on disk, with file extension
  • Value “Latitude”, “Longitude”, “Altitude” : any supported projected coordinate system
ImNum	Cam	CamImNm	Rotate	Error	GPSTime 	Index	Filename	Longitude	Latitude	Altitude	Roll	Pitch	Heading	Width	Height	Var01	Var02
7	1	2	0	0	246142.1482	0	survey1_Cam1_000002.jpg	618921.0011	4849398.69	161.9710	93.266084	17.752664	-0.735097	2456	2058	0	0
11	1	3	0	0	246143.1493	0	survey1_Cam1_000003.jpg	618925.3284	4849400.029	161.9081	93.802148	18.479762	-0.727995	2456	2058	0	0
15	1	4	0	0	246144.1503	0	survey1_Cam1_000004.jpg	618930.3285	4849401.649	161.8526	94.432493	19.403512	-1.106034	2456	2058	0	0
...

Camera calibration

For each camera it is required to adjust the template camera calibration AttributeExpression values in the camera import Orbit Resource Description file.
Edit the template files prior to data import using a standard text editor (e.g. Notepad). Be meticulous regarding file structure and formatting.
<template_name>/planar<X>/import/import_locations.ord

[CameraNo1]
PIXEL_SIZE =3.450000
IMAGE_HEIGHT =2058.000000
IMAGE_WIDTH =2456.000000
Focal_Length =8.260648
Radial_Distortion_K1 =0.001692
Radial_Distortion_K2 =-0.000030
Radial_Distortion_K3 =0.000000
Principal_Point_Offsetx =1228.871105
Principal_Point_Offsety =1027.912449

Point Cloud

LiDAR files

  • File format : one *.las file, version 1.2
  • Value of Coordinates : same as images, see above
  • Value of Timestamps : same as images, see above
1)
Can be adjusted via Custom MM Import Configurations.
 
Last modified:: 2019/03/25 11:36