====== Prepare MM Data 3D Laser Mapping ======

After capturing data with the 3DLM StreetMapper or V-Mapper, use the standard 3DLM tool SMProcess to process and prepare the data for [[110:mobile_mapping:desktop:mobile_mapping:manage:import:index|importing into Orbit]].

It is **strongly recommend** to read first following documentation :
  * [[110:mobile_mapping:desktop:mobile_mapping:manage:index|]]
  * [[110:mobile_mapping:supported_resources|]]

\\
===== Trajectory =====

  * File : one ascii .pos text file
  * Crs : default coordinate system is WGS84 geographic (EPSG 4326). To define a local projected crs contact (support at 3dlasermapping dot com) 
  * Data-structure : Flat ascii text file, tab separated, no column headers, with columns : timestamp, latitude, longitude, height, roll, pitch, heading, Y-accuracy, X-accuracy, Z-accuracy, pitch-accuracy, roll-accuracy, heading-accuracy

<code>
576914.5075  33.039202814  -97.282371203  164.913 -0.3929  2.3931  -69.6806  0.012  0.010  0.020  0.002  0.002  0.003
576914.5100  33.039202853  -97.282371325  164.914 -0.3865  2.3907  -69.6765  0.012  0.010  0.020  0.002  0.002  0.003
576914.5125  33.039202893  -97.282371448  164.914 -0.3809  2.3883  -69.6719  0.012  0.010  0.020  0.002  0.002  0.003
...
</code>

\\
===== Panoramas =====

==== Photo Positions ====

  * File : one ascii text file
  * Crs : default coordinate system is WGS84 geographic (EPSG 4326). To define a local projected crs contact (support at 3dlasermapping dot com) 
  * Data-structure : Flat ascii text file, tab separated, no column headers, with columns : timestamp, x, y, z, heading, pitch, roll, filename 
  * New data-structure from next version : timestamp, latitude, longitude, height, roll, pitch, heading, filename 



<code>
577729.913460	-97.28428505	33.03699795	167.312	14.6223	1.6618	5.2018	stream-000000_00000.jpg
577730.246772	-97.28428232	33.03700644	167.312	14.6550	1.6490	5.1536	stream-000000_00001.jpg
577730.580112	-97.28427957	33.03701482	167.311	14.6657	1.6493	5.2152	stream-000000_00002.jpg
...
</code>

==== Images ====

  * Files : *.jpg files, each panorama is one jpg image file.
  * Naming : exactly as described in photo position file (see above, last column) 

==== Export from SMProcess ====

  - Open your project in SMProcess
  - Add the ladybug streams to the project that need processing
  - Go to ‘Process Image Data’
  - Select the ladybug stream to process
  - Select the ‘Create Panoramic Images’ option
  - Click the ‘Add To Process Images’ button
  - Click on the ‘Event Options’ tab at the bottom
  - Select the ‘Create Orbit Photo List’ option
  - Click ‘Add To Process Events’ to create the Orbit Photo List
  - This file will be used in Orbit to import the panoramic image positions

{{  3dlm_smprocess_panorama_1.png?nolink&800  |}}

{{  3dlm_smprocess_panorama_1.png?nolink&800  |}}

\\
===== Pointcloud =====

  * File : one or multiple .las files
  * Crs : default coordinate system is WGS84 geocentric / ECEF (EPSG 4978). To define a local projected crs contact (support at 3dlasermapping dot com) 
  * Data-structure : default Las structure (v1.2)

==== Export from SMProcess ====

  - Open your project in SMProcess
  - Add the lidar data to the project
  - Go to ‘Create Point Cloud’
  - Select the lidar file to process
  - Select the options to process with and the coordinate system to GeoReference it in
  - Click ‘Add To Process List’ to start processing the point cloud

{{  3dlm_smprocess_pointcloud.png?nolink&800  |}}
====== Import ======

[[110:mobile_mapping:desktop:mobile_mapping:manage:import:index|]]