Knowledge Base
Recent Changes

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
dev:desktop_ext:mapping:manage_import:phoenixlidar_uas [2021/07/28 14:43]
lucas 		dev:desktop_ext:mapping:manage_import:phoenixlidar_uas [2021/08/03 17:04] (current)
lucas [LiDAR]
Line 1: Line 1:
 ====== Phoenix Lidar UAS ====== ====== Phoenix Lidar UAS ======
  
-This page describes the original generic mobile mapping resources for Orbit import.+This page describes the original Phoenix Lidar aerial mapping resources for Orbit import.
  
 Use the corresponding [[dev:desktop_ext:mapping:manage_import:templates|Orbit Import Template]] to import the described original data. \\ Use the corresponding [[dev:desktop_ext:mapping:manage_import:templates|Orbit Import Template]] to import the described original data. \\
Line 11: Line 11:
  
   * Image type : Original files.   * Image type : Original files.
-  * Image resolution : 6000x*4000 pixels.+  * Image resolution : 6000x4000 pixels.
   * File format : Each image is one *.jpg file.   * File format : Each image is one *.jpg file.
   * File name : Exactly as "Filename" value of photo position file, see below.   * File name : Exactly as "Filename" value of photo position file, see below.
-  * Folder structure : All image files of one camera in one folder, Phoenix Lidar usual folder names are: cam0 and cam1 +  * Folder structure : All image files of one camera in one folder. Phoenix Lidar usual folder names are: cam0 and cam1 
  
 === Image positions files === === Image positions files ===
  
-  * File format : One ascii file (*.csv or *.txt file) per camera.+  * File format : One ascii *.csv file per camera.
   * File structure Rows : Each image is one record.   * File structure Rows : Each image is one record.
   * File structure Columns : Comma seperated (char44), headers, with exact order as the example below.   * File structure Columns : Comma seperated (char44), headers, with exact order as the example below.
-  * Value of Filename : File name as on disk with .jpg file extension.+  * Value of Filename : File name as on disk with *.jpg file extension.
   * Value of Coordinates : WGS84 geographical Lat/Long order (EPSG:4326), as exported by Phoenix Lidar, decimal notation, without thousands separator.    * Value of Coordinates : WGS84 geographical Lat/Long order (EPSG:4326), as exported by Phoenix Lidar, decimal notation, without thousands separator. 
  
Line 32: Line 32:
 </code> </code>
  
-=== Camera calibration file ===+=== Camera calibration information ===
  
-  * File format : One ascii file for each camera+  * File format : the camera calibration parameters are in each camera position file header (csv, see above)
  
 <code> <code>
-SensorSizePIX=2046,2046 +# Camera settings at export: ... ,"receptors":[{"distortion":{"k1":-0.06567,"k2":0.0773,"k3":0.01971,"p1":0,"p2":0},"focalLength":{"x":15.89,"y":15.89},"pixelCount":{"x":6000,"y":4000},"principalPoint":{"x":2987.96,"y":1959.91},"size":{"x":23.4,"y":15.6},"transform"...
-SensorSizeMM=1.12530000000E+001,1.12530000000E+001 +
-PrincipalPoint=-2.61956763602E-001,-1.56800990463E-001 +
-FocalLenghtMM=8.22273991883E+000 +
-DistortionType=6 +
-Dist_CV_K1=-1.846504319177130E-001 +
-Dist_CV_K2=1.285589751369390E-001 +
-Dist_CV_K3=-2.821016417454580E-002 +
-Dist_CV_K4=0.000000000000000E+000 +
-Dist_CV_K5=0.000000000000000E+000 +
-Dist_CV_K6=0.000000000000000E+000 +
-Dist_CV_P1=-3.798480723832470E-004 +
-Dist_CV_P2=3.031639898513610E-004 +
-Dist_CV_CX=9.753714975268900E+002 +
-Dist_CV_CY=1.051509270993260E+003 +
-Dist_CV_FX=1.495043621605830E+003 +
-Dist_CV_FY=1.495043621605830E+003 +
-Dist_CV_HEIGHT=2046 +
-Dist_CV_WIDTH=2046+
 </code> </code>
  
-The camera calibration parameters must be entered before Create Run, the 1st step of the Import Run procedure. \\  
-To facilitate import, your specific camera calibration values can be registered inside the Orbit template to avoid entering these values at import each time. Contact Orbit Support if assistance is needed.  
  
-{{:dev:desktop_ext:mapping:manage_import:generalplannerimport.png?nolink&850|}}+The camera calibration parameters from this file must be entered before clicking Create Run, the 1st step of the Import Run procedure. \\  
 +To facilitate import, your specific camera calibration values can be registered inside the Orbit template to avoid entering these values at each import. Contact Orbit Support if assistance is needed. 
 + 
 +{{:dev:desktop_ext:mapping:manage_import:phoenix_lidar_camera_settings.jpg?800|}} 
 ===== LiDAR ===== ===== LiDAR =====
  
Line 68: Line 52:
   * File format : One or more [[dev:technology:supported_formats:index|supported point cloud]] file formats.    * File format : One or more [[dev:technology:supported_formats:index|supported point cloud]] file formats. 
   * File structure : Las/Laz or Ascii *.txt, *.csv file.    * File structure : Las/Laz or Ascii *.txt, *.csv file. 
-    * Las (recommended) or Laz :  Las version 1.2.+    * Las (Usual Phoenix Lidar output, recommended) or Laz :  Las version 1.2.
     * Ascii File : Space separated (Char32), headers, with exact order as the example below. Line ends by carriage return char(13) and newline char(10) sequence.     * Ascii File : Space separated (Char32), headers, with exact order as the example below. Line ends by carriage return char(13) and newline char(10) sequence.
-  * Value of Coordinates : Same reference as Trajectory.  +  * Value of Coordinates : Any coordinate system (usually a projected metric CRS for Phoenix Lidar). The user needs to fill the imported point cloud CRS in the Source CRS field. 
-  * Value of Timestamp : Same reference as Trajectory. +See [[dev:desktop_ext:mapping:manage_import:index|Import Run]] for more information on template usage and CRS selection 
  
 <code> <code>
 
Last modified:: 2021/07/28 14:43