Explore

Week 03 Skydio scan

Report: Skydio Mapping Missions

Team Members: Ryan, Maddie, Collin, and Kenzie

Introduction

For this lab, our team engaged in two mapping missions using the Skydio platform. The purpose of the exercise was to practice mission planning, data collection, and troubleshooting while executing both a 2D lawnmower grid scan and a cross-hatch with perimeter scan. These flights were designed to simulate real-world mapping applications and build on our prior experiences with Skydio flight operations. Compared to earlier platforms we have flown, the Skydio offers more advanced autonomous mapping capabilities but also relies heavily on mission software, which we learned can present challenges when issues arise.

Study Area(s)

The mapping missions took place at the Student Garden, approximately a 10-minute drive from campus. The site was open but surrounded by vegetation, with several hazards nearby such as trees and human activity within the garden. Weather: Sunny, no wind, clear skies Site Conditions: Dry turf, moderate student activity in the area Potential Hazards: Trees along the perimeter, unexpected pedestrian interaction, expired software issue

Table 1. Site Conditions

Table 7

Table 7

Location

Weather

Hazards

Notes

Student Garden

Sunny

Trees, garden users

One pedestrian interaction

There are no rows in this table

⁠

Methods

We conducted two mapping missions: 1. Red Rectangle (Lawnmower Grid) Mission - Altitude: 200 feet - Overlap: 80% frontal and side - Lens Angle: 90° (Nadir) - Flight took approximately 20 minutes. 2. Blue Rectangle-Size Area (Cross Hatch + Perimeter) - Altitude: 60–80 feet (adjusted for clearance of obstacles) - Overlap: 80% - Lens Angle: 75° bevel - Settings: Cross-hatch enabled, perimeter enabled - Flight required correction after initial boundary error near tree line. Issues Encountered: - The mapping software license had expired, which delayed operations for over two hours. The issue was eventually solved by borrowing two working drones from another team. - A member of the Student Garden approached our team during the mission. Ryan handled the interaction professionally by providing the professor’s contact information. The individual was not upset but requested notice in the future.

Data Collection Outcomes / Expected Deliverables

Despite setbacks, both missions were successfully executed. The flights allowed us to collect a usable image set for future stitching into orthomosaics and 3D models.

Table 2. Data Collection Summary

Table 8

Table 8

Mission Type

Drive + Setup

Flight Time

Notes

Lawn Mower Grid

10 min

20 min

Completed with no major issues

Cross Hatch + Perim.

10 min

~20 min

Flight corrected near tree line

There are no rows in this table

⁠

*Exact numbers not recorded due to troubleshooting delays, but will be included in later mapping deliverables.

Conclusion

This lab provided valuable experience in both mission execution and troubleshooting. Our team demonstrated resilience and cooperation under pressure, especially when faced with software and hardware issues. The challenges reminded us of the importance of preparing backup plans and communicating with bystanders who may be affected by drone operations. Overall, the exercise successfully trained us in 2D and 3D mapping workflows while highlighting the need for attention to overlap settings, boundary placement, and software readiness.

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.