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/27 16:00]
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 folderPhoenix usual folder names are: cam0 and cam1 +  * Folder structure : All image files of one camera in one folderPhoenix Lidar usual folder names are: cam0 and cam1 
  
 === Image positions files === === Image positions files ===
  
-  * File format : One ascii file (*.csv or *.txt fileper 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 : Semicolon seperated (char59), 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, without file extension. +  * Value of Filename : File name as on disk with *.jpg file extension. 
-  * Value of Coordinates : Any [[dev:technology:core:crs|supported coordinate system]] can be used, Long/Lat order for geographical coordinates, 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. 
-  * Value of Timestamps : Same Time Reference as in the point cloud, see below+
  
 <code> <code>
-Filename;Timestamp;X/Long;Y/Lat;Z;Omega;Phi;Kappa +... 
-1000000;0;4.404878286326054;50.85106227753124;128.33142823723782;88.132974310915699;0.095102381910084;-359.06942401248796 +# Columns: Filename, Vehicle Latitude, Vehicle Longitude, Vehicle Altitude, Vehicle Yaw, Vehicle Pitch, Vehicle Roll, Receptor Latitude, Receptor Longitude, Receptor Altitude, Receptor Yaw, Receptor Pitch, Receptor Roll, P4D Omega, P4D Phi, P4D Kappa, Time GNSS Week, Time GNSS TOW, Time GNSS Abs, Time GNSS Rel, Time GNSS Int, Time Cam Abs, Time Cam Rel, Time Cam Int, Time Host Retrieval, FrameCount Cam, Error Code, Error String 
-1000001;1;4.404918241374241;50.85107702770032;128.37570893339338;39.507857332631851;-1.084923642050256;-359.32845731111627+cam0-000-000000-0.jpg, 55.789414897, 37.797834321, 167.893, 170.157, -178.135, -178.630, 55.789416393, 37.797834304, 167.824, 82.213, -57.384, -92.826, 4.955, 32.278, -12.047, 2119, 387535.306630, 1 281 958 735 306 630, 0, , -1, 0, , 1 281 958 737 654 000, -1, 0, 
 +cam0-000-000001-0.jpg, 55.789414897, 37.797834321, 167.893, 170.157, -178.130, -178.634, 55.789416393, 37.797834304, 167.824, 82.221, -57.380, -92.834, 4.951, 32.283, -12.048, 2119, 387537.406949, 1 281 958 737 406 949, 2 100 319, 2 100 319, -1, 0, , 1 281 958 739 668 000, -1, 0,
 ... ...
 </code> </code>
-=== Camera calibration file === 
  
-  * File format : One ascii file for each camera+=== Camera calibration information === 
 + 
 +  * 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 67: 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/27 16:00