commercial drone best practices: how to incorporate data and job specs
TRANSCRIPT
International LiDAR Mapping Forum 2015
UAS Best Practices: How to Incorporate Data and Job Specs
Colin Snow, CEO and Founder, Drone Analyst
February 23-25, 2015Denver, Colorado, USA
Produced by Diversified Communications
1
Helpful advice
2
Quick survey
Image courtesy of Event 38 Unmanned Systems
3
Questions / topics
What should you consider when adding a remotely piloted system to your practice?
Under which application scenarios do they provide advantages?
What are the practical job spec limits of using a LiDAR drone in a project – when is a project a bad fit?
What does flying a UAS do to the price point for job specs?
How can UAS data be incorporated into existing data and workflow?
What are the data processing and data accuracy issues?
4
UAS ‘system’ considerations
1. Aircraft type (fixed wing or multirotor)
2. Sensor / payload
3. Ground control station
4. Communication systems
5. Pilot and crew
6. Regulations• Safety
• Operational risk
• System deployment risk
• Privacy / data management
• SecuritySource: Drone Analyst
5
Sample use cases under proposed rules
Inspection / MonitoringBridgesOil rigsRefineriesCell towersWind turbinesRadio antenna
Surveying / MappingSmall minesStockpilesEasementsShopping centersStadiums
See article: Market Opportunity Winners and LosersImage source: Aerial Services, Inc.
6
Which UAS for what job?
Image source: DJI, 3D Robotics, Phoenix Aerial Systems
DIY / CONSUMER TURNKEY / COMMERCIAL
JOB GRADE Casual / Fast Inspection & Survey / Complex
PAYLOAD Low-res cameras / GoPro Hi-res cameras / LiDAR
GPS / IMU Aircraft GPS & IMU (1 – 3 meters) Aircraft GPS & IMU + Camera / Sensor GPS & IMU (centimeters)
AQUISTION Limited Higher
AVG COST < $2K > $12K
ROI Fast Measured
7
Transportation corridor mapping example*
RANGE PROJECT TIME(PERSON DAYS)
PRICE
GROUND 100 yards 30 days (5 – 6 tripods?) ~ $220K
MOBILE 5 – 7 miles 2 – 4 days ~ $30K
MANNED AIRCRAFT
~ 50 miles 2 day $ 25k +
UAS 1500 yards / pass 1 day $ 10K
*estimates for comparison purposes only!
8
Workflow
Specifies area, flight time, resolution
Specifies area, flight time, resolution
Site analysis, Route and waypoints,
Weather check
Site analysis, Route and waypoints,
Weather check
Map over X km2, Download
images and telemetry file
Map over X km2, Download
images and telemetry file
Load into software,
Generate point-cloud
measurements
Load into software,
Generate point-cloud
measurements
Send files ftp or cloud app
Send files ftp or cloud app
Customer Demand
Customer Demand
Mission Planning
Mission Planning
FlightFlight ProcessingProcessing DeliveryDelivery
Source: Drone Analyst
9
Data accuracy
Absolute AccuracyDescribes how much the whole point cloud is offset in any direction, leading to a constant error in geo-referencing. Depends almost exclusively on a correctly configured GNSS reference station.
Relative AccuracyIndicates how self-consistent the resulting point cloud is
Source: Phoenix Aerial Systems
10
Issues affecting aerial LiDAR accuracy
UAS are an aggregated technology and they ‘shake’ XYZ GPS (accuracy, down time) IMU (accuracy) Laser itself
Image source: Phoenix Aerial Systems
11
LiDAR IMU accuracy
Point Offset vs. Scan Range
12
Image source: Phoenix Aerial Systems
Combining data sets
Image source: Terrasolid
Image source: Phoenix Aerial Systems
13
A few recommended sessions
Keynote: UAS and the Internet of Things
GeoCue Technical Workshop: Implementing LAS V1.4 Support in Airborne LIDAR Workflows
LiDAR Scanning with Supplementary UAV Captured Images for Structural Inspections
Does Camera Quality Matter in sUAS Photogrammetry?
Trimble Technical Workshop: Data Alignment and Automated Information Extraction – Two Important Elements of an Efficient LiDAR Processing Workflow
Topcon Technical Workshop: Using Unmanned Aircraft Systems to Calculate Stockpiles
14
© 2014 Drone Analyst.All rights reserved.
Drone Analyst products and services mentioned herein as well as their respective logos are trademarks of Drone Analyst.
These materials are provided by Drone Analyst for informational purposes only, without representation or warranty of any kind, and Drone Analyst shall not be liable for errors or omissions with respect to the materials.
In particular, Drone Analyst has no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and Drone Analyst strategy and possible future developments, products, and/or research directions are all subject to change and may be changed by Drone Analyst at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, research notes, or web content.
Copyright 2014 – Drone Analyst 16