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 Trimble MX3 Resources
This page describes Trimble MX3 files exported by Trident for Orbit.
Using the according Orbit Import Templates the described resources can be imported into Orbit.
It is strongly recommend to read first Concepts of Mobile Mapping and UAS data in Orbit.
Trajectory
Trajectory positions file
- File format : One ascii *.csv file.
- File structure Rows : Each timestamp is one record.
- File structure Columns : Tab separated (char9), no headers, with exact order as the example below.
- Value of Coordinates : any supported coordinate system can be used, Long/Lat order for geographical coordinates, decimal notation, without thousands separator.
000000 501148.806 4683829.287 30.018 56.066 -0.787 2.869 0 0 0 000001 501150.897 4683824.298 29.906 35.229 0.210 3.262 0 0 0 000002 501154.567 4683820.426 29.722 15.274 -0.028 3.154 0 0 0 000003 501159.351 4683818.013 29.551 353.409 -0.674 3.946 0 0 0 ...
Panoramas
Image files
- Image type : Ladybug 5, equirectangular panoramas.
- Image resolution : Ratio 2×1, advised 8000×4000 pixels.
- File format : Each image is one *.jpg file.
- File name : ladybug_panoramic_000000.jpg, ladybug_panoramic_000001.jpg, ladybug_panoramic_000002.jpg, …
- Folder structure : All files in one folder.
Image positions file
- File format : One ascii *.csv file.
- File structure Rows : One record for each image.
- File structure Columns : Comma separated (char44), headers, exact order as the example below.
- Value of “ImageName” : xxx_00000.jpg xxx_00001.jpg, xxx_00002.jpg, …
- Value of Coordinates : any supported coordinate system can be used, Long/Lat order for geographical coordinates, decimal notation, without thousands separator.
T3DFrameNo,AVIFrameNo,ImageName,X-Ori,Y-Ori,Z-Ori,H-Veh,R-Veh,P-Veh,X-Sensor,Y-Sensor,Z-Sensor,H-Sensor,R-Sensor,P-Sensor,Dist,ltx,lty,ltz,rtx,rty,rtz,lbx,lby,lbz,rbx,rby,rbz 0,0,00000.jpg,501148.788,4683829.274,29.327,163.753,2.819,-0.567,501148.806,4683829.287,30.018,56.066,-0.787,2.869,5.001,501148.065,4683833.691,33.127,501152.558,4683827.014,33.238,501148.367,4683833.793,26.999,501152.860,4683827.115,27.110 1,1,00001.jpg,501150.876,4683824.291,29.216,142.968,2.890,-1.639,501150.897,4683824.298,29.906,35.229,0.210,3.262,10.405,501148.670,4683828.102,33.098,501155.245,4683823.459,33.069,501148.853,4683828.400,26.972,501155.428,4683823.757,26.942 2,2,00002.jpg,501154.550,4683820.409,29.031,122.999,2.860,-1.378,501154.567,4683820.426,29.722,15.274,-0.028,3.154,15.753,501151.164,4683823.250,32.894,501158.929,4683821.130,32.898,501151.256,4683823.575,26.767,501159.021,4683821.455,26.771 ...
LiDAR
Point cloud files
- File format : One or more *.las files for each scanner.
- File structure : Las version 1.2.
- Value of Coordinates : Same CRS as Image Positions.
- Value of Timestamp : Same reference as Trajectory.
Last modified:: 2020/05/18 13:05