Comment on page
A corridor scan mission must contain at least one Corridor Scan pattern. The corridor is a path marked out on the map (shaded in green above). The white line indicates the grid flight path. The green circular markers indicate the points where the vehicle enters and exits the pattern.
The Mission editor on the right is used to set the corridor: width, altitude, required image resolution, and other properties, and to specify camera settings appropriate for creating geotagged images.
This topic shows how to define a corridor scan mission and the various settings that can be configured in the Corridor Scan Editor.
The easiest way to define a corridor scan mission is to use the Plan view > Pattern > Corridor Scan tool from the Plan Tools.
This creates a template for a simple end end-to-end structure corridor scan mission for the current vehicle type. Often all the user has to do is define the scan area (any items that require configuration are shown with a red border in the mission item list).
If a more complex mission is needed, the basic mission can be extended by adding other items before the return item.
To create a corridor scan mission:
- 1.Open the Plan View, select the Pattern and then Corridor scan.
- The green part of the line is the area being scanned while the white line is the proposed flight path.
- Move a filled circle (vertices) at one end of the line to the beginning of the desired path, and the other to the end (drag/drop on the map).
- Select the unfilled circle between the two ends (vertices) to create a new vertix. Move the vertix to the first point in the path where the direction changes.
- Repeat the last step, creating new vertices and moving them onto the desired path.
The Mission Editor is used to configure Camera and Grid settings. The trash/bin icon on the top left can be used to delete the whole item.
- 1.Select the Mission tab to edit your Corridor scan pattern.
Set the camera first, before configuring the grid (camera capabilities affects the grid settings).
Users can select a predefined, custom, or manual camera. The main difference is that using a predefined or custom camera allows Mission Control to calculate an optimal layer height for a trigger distance, and visa versa, while using a manual camera means that these parameters need to be manually calculated (and are therefore harder to change).
Corridor Scan Camera Settings: Manual Camera
The Grid tab is used to set the properties of the scan.
Corridor Scan Grid Settings: Predefined/Custom Camera
For a predefined or custom camera the scan settings allow users to choose a desired image overlap and set either desired scan altitude or image resolution for the ground surface (automatically calculating the other value).
For a manual camera, the grid settings are instead specified as shown. Note that if any of these settings need to change, then they may all need to be manually recalculated.
The Corridor section is used for grid settings that are independent of the camera. Changes in the settings are reflected in the map.
Terrain Following makes the vehicle maintain a constant height relative to ground throughout the scan (by default, a flying vehicle will follow the corridor path at a fixed altitude).
Terrain following uses terrain heights queried from AirMap servers.
The Statistics section shows the calculated survey area, photo count, interval, and resolution.