[[111:uas_mapping:index#Orbit UAS Mapping Documentation|{{ :orbitgis:return_overview.png|Return to Overview - Orbit UAS}}]] ====== postflight: import your flight data ====== Steps to be taken:\\ 1. [[111:uas_mapping:post:importflightdata_microdrones_nir#1. save your flight data|Save your flight data]] \\ 2. [[111:uas_mapping:post:importflightdata_microdrones_nir#2. import flight data|import your flight data for processing]] & [[111:uas_mapping:post:post|continue the postprocessing]] ---- \\ \\ ==== 1. save your flight data ==== Having a look at the folder structure of your generated project, you can easily see where to put your 'flight' files after the flight. Put the images in the flight directory together with the [[111:uas_mapping:manage:supported_resources#Positions and orientations of reference frame at time of recording|EO file]] that you generated in the most recent version of your hardware manufacturer. \\ \\ {{nir_import.png?nolink|}} \\ \\ If you used the preflight tab to plan your flight (microdrones), delete the "flight1" folder and put the images directly in the "imagery_and_photolist folder. The photolist need to be changed to a EO file (Image name, X, Y, Z, Roll, Pitch, Yaw) (see below). Change your UAV type to generic and start the import (CRS = WGS 84 (4326), long/lat, order = roll pitch yaw; yaw = pointing North cw; z = above sealevel). \\ \\ Photolist Flight #1009 2014-05-21 08:08 Photo GPS Time Timecode Latitude Longitude GPS-A. Height Roll Pitch Yaw Pitch servo Roll servo 001 08:11:39 181.910 +51.08674752 +4.01096161 113.9 64.6 +0.3 -1.1 +93.1 +34.6 +45.0 002 08:11:53 195.413 +51.08674537 +4.01107521 114.3 64.6 +0.6 +0.4 +92.0 +35.5 +45.0 003 08:12:06 208.676 +51.08674224 +4.01117978 113.9 64.5 +0.5 -1.2 +91.9 +34.6 +45.0 004 08:12:20 222.154 +51.08674074 +4.01129193 113.2 64.6 +1.0 -0.5 +92.7 +35.1 +45.0 005 08:12:33 235.160 +51.08673975 +4.01140176 112.9 64.5 +0.7 +0.1 +91.7 +35.1 +45.0 006 08:12:46 248.410 +51.08673302 +4.01151126 112.8 64.6 +0.5 -0.1 +92.6 +35.1 +45.0 \\ EO File TTC00071 +51.08674752 +4.01096161 64.6 +0.3 -1.1 +93.1 TTC00072 +51.08674537 +4.01107521 64.6 +0.6 +0.4 +92.0 TTC00073 +51.08674224 +4.01117978 64.5 +0.5 -1.2 +91.9 TTC00074 +51.08674074 +4.01129193 64.6 +1.0 -0.5 +92.7 TTC00075 +51.08673975 +4.01140176 64.5 +0.7 +0.1 +91.7 TTC00076 +51.08673302 +4.01151126 64.6 +0.5 -0.1 +92.6 \\ \\ \\ ==== 2. import flight data ====
\\ {{111:uas_mapping:post:importflightdata.png?nolink|}}\\ After saving your flight data at the right folder, the processing can start. Push the import flight data button and click on start. Window will appear with generic import choices. * Fill in the estimated average ground height in m. * The source CRS of your GPS XYZ data. * The order of the coordinates (lat long or long lat) (XY or YX) * The interpretation of Z-value: above sea-level (tick on) or barometric height (tick off) * The order of the orientations of roll, pitch, and yaw * The interpretation of the Yaw direction (pointing north or east; clockwize or counterclockwize)\\ \\ {{111:uas_mapping:post:importgeneric.png?nolink|}}
Once accepted, the software will now: * Check for missing images, or wrong EO files and send back an error * Transform all given orientation data into the format (e.g. CRS) for Orbit UAS Mapping. * Covert the *.jpg or *.tif images to the [[111:technologies:resources:image:omi|*.omi]] format. OMI stands for Orbit Multiresolution Image. This resource type is developed by Orbit GT for encoding and fast viewing of rasters and images (any size). \\ If import has already been done, you will get the warning of import. \\ \\ {{import_already.png?nolink|}} \\ \\ The postprocessing project will be created and shown in your [[111:orbitgis:index|mapcanvas]]. You will see that two extra layers will be add to your [[111:orbitgis:datasetlist:index|datasetlist]]. * Post - Projection Centra: X, Y, Z position during image shot * Post - Photo Footprint You can change colors or transparancy of these layers via the [[111:orbitgis:datasets:legend:index|legend editor]] of Orbit (right mouse click on the layer). These layers are created based on the values given by EO file. To check the raw material (image and XYZ coordinates), please have a look at the video tutorial below. Via the '[[111:orbitgis:inspector:object:focus#Editing Object Attributes|show hyperlink document]]' you can open all raw images and check the quality. If you get an error "check input", be sure that the number of photo's in the flightlog are equal to the number of photo's in the flight directory. Delete also manual triggers out of flightlog. More information can be found at [[111:uas_mapping:manage:supported_resources|generic import data page]]. \\
\\ \\ \\ ------ \\ To continue the postprocessing, go to [[111:uas_mapping:post:post|posttab page]].
[[111:uas_mapping:index|{{:orbitgis:return_overview.png|back to overview - Orbit UAS Mapping}}]] \\ To get back to the overview, click this icon.