====== UAS Data Preparation and Import Templates ======

This page gives an overview on the Orbit UAS Mapping import templates and how to prepare your UAS data for import. 

<note tip>
Orbit imports post processed UAS resources into Orbit Mapping Runs using intelligent Import Templates.

An **Orbit Import Template** is a predefined set configurations, containing all technical details of the post processing bundle adjustment software or LiDAR processing tools. A template is exactly configured according well defined internal camera calibration parameters, image positions and external orientations and point cloud exports. This technique simplifies and standardizes the workflow to import a well known set of complex UAS data.</note>

===== Add Template to Orbit =====

Standard Import Templates are by default available. \\

===== Standard Templates =====

|< 100% 15% 25% 24% 9% 27% >|
^ Company ^ Prepare ^ Data ^ [[180:technology:core:crs|CRS]] ^
| Generic | Generic Point Cloud - Projected CRS | Point cloud | projected |
| ::: | Generic Point Cloud - Geographic CRS | Point cloud | geographic |
| [[http://www.agisoft.com/|Agisoft]] | [[170:desktop_ext:mobile_mapping:manage_import:agisoft|Agisoft - Projected CRS]] | Planar, Point cloud | projected |
| [[https://pix4d.com/|Pix4D]] | [[170:desktop_ext:mobile_mapping:manage_import:pix4d|Pix4D - Projected CRS]] | Planar, Point cloud | projected |
===== Custom Templates =====

In addition to the above listed Standard Templates, Custom Templates can be created to import any combination of supported UAS Mapping resources.

Contact sales at orbitgt dot com to request assistance on creating your own Customized Template.