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/29 10:40]
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 54: Line 54:
     * Las (Usual Phoenix Lidar output, 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 : Any coordinate system. The user needs to fill it in the Source CRS field+  * 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. 
 +See [[dev:desktop_ext:mapping:manage_import:index|Import Run]] for more information on template usage and CRS selection
  
  
 
Last modified:: 2021/07/29 10:40