====== Prepare MM Data Trimble TIMMS ======

This page describes how to prepare Trimble TIMMS mobile mapping resources for Orbit. \\
Using the according [[195:desktop_ext:mapping:manage_import:templates|Orbit import templates]] the described resources can be [[195:desktop_ext:mapping:manage_import:index|imported into Orbit]].

It is **strongly recommend** to read first [[195:technology:3d_mapping:about_resources|]].

===== Trajectory =====

=== Trajectory file  ===

  * File format : One ascii *.txt file.
  * File structure Rows : One record for each trajectory timestamp.
  * File structure Columns : Tab separated (char9), headers, with exact order as the example below.
  * Value of Coordinates : WGS84 geographical coordinates, decimal notation, without thousands separator.
  * Value of Timestamp : Any [[195:technology:3d_mapping:supported_resources|supported time reference]] can be used, decimal notation without thousands separator.

<code>
Time(s)	Latitude(degrees)	Longitude(degrees)	Altitude(m)	Roll(radians)	Pitch(radians)	True-Heading(radians)	North-Position-Error(m)	East-Position-Error(m)	Down-Position-Error(m)
 1010.201665	 45.59368539	 13.80746235	 73.350	 0.000847	 0.004895	 1.189491	 0.008522	 0.008890	 0.008072
 1010.301688	 45.59368539	 13.80746235	 73.350	 0.000861	 0.004907	 1.189475	 0.008522	 0.008890	 0.008072
 1010.401712	 45.59368539	 13.80746235	 73.350	 0.000855	 0.004892	 1.189485	 0.008522	 0.008890	 0.008072
...
</code>
===== Panoramas =====

=== Image files ===

  * Image type : Ladybug 3, equirectangular panoramas.
  * Image resolution : Ratio 2×1, advised 5400x2700 pixels
  * File format :One *.jpg file for each image.
  * File name : Concat("ladybug_panoramic_",LPad([Photo ID],6,"0")), e.g. ladybug_panoramic_000000.jpg, ladybug_panoramic_000001.jpg, ...
  * Folder structure : All files in one folder.

=== Image positions file ===

  * File format : One ascii *.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 "Photo ID" : Image id according image file name.
  * Value of Coordinates : any [[195:technology:core:crs|supported coordinate system]] can be used, Long/Lat order for geographical coordinates, decimal notation, without thousands separator. 
  * Value of Timestamp : Same reference as Trajectory, see above. 

<code>
Photo-ID	POS-Time	Long(M)/Easting(M)	Lat(M)/Northing(M)	Ellisp-Altitude(M)	Roll(Deg)	Pitch(Deg)	Heading(Deg)	Lat(Deg)	Long(Deg)
0	1420.922556	406985.4245	5049596.2538	   75.0160	  179.4120	    0.0989	  143.0824	 45.59368459	 13.80745991
1	1969.347713	406983.9365	5049595.0566	   75.0189	  179.6278	   -0.0014	  158.7005	 45.59367361	 13.80744106
2	1971.048055	406983.1119	5049594.4337	   75.0210	  179.4668	   -0.0462	  163.0412	 45.59366790	 13.80743061
3	1972.948436	406982.2397	5049593.8956	   75.0226	  179.5295	   -0.0256	  168.3631	 45.59366294	 13.80741953
...
</code>

===== LiDAR =====

=== Point cloud files ===

  * File format : One or more *.las or *.laz files.
  * File structure : Las version 1.2.
  * Value of Coordinates : Same reference as Trajectory, see above. 
  * Value of Timestamp : Same reference as Trajectory, see above.