Define the Decision
Clarify who will use the result, what they need to assess and which measurements or observations matter.
Enterprise Sales & Technical Support Across CanadaFast product access · Configuration · Training · After-sales support
Unmanned Canada helps organizations plan and execute purpose-built aerial data collection for mapping, LiDAR, inspection, thermal, multispectral and recurring site-documentation projects—then organizes the captured data around the required deliverable.
Project scope matters: Data products, accuracy, regulatory requirements, site access, privacy controls and processing depend on the project. Professional surveying, engineering certification, legal opinions and regulated professional services are not implied and must be explicitly scoped with appropriately qualified professionals where required.
The right aircraft and sensor depend on the decision the client needs to make. Before mobilization, the project should define coverage, detail, coordinate reference, timing, file format, acceptance checks and intended use.
Clarify who will use the result, what they need to assess and which measurements or observations matter.
Agree on coverage, detail, coordinate reference, completeness, timing, formats and review responsibilities.
Select the aircraft, RGB, LiDAR, thermal or multispectral sensor and positioning workflow around the site.
Check capture completeness, processing assumptions, limitations, file organization and supporting metadata.
Select the closest project goal. The recommendation identifies a likely capture workflow and the questions that must be confirmed before quoting or mobilization.
Collect calibrated, overlapping imagery for an orthomosaic, surface model, point cloud, mesh or visual site record.
Use LiDAR when terrain, vegetation, vertical assets, corridor geometry or point-cloud analysis is central to the project.
Capture consistent wide, zoom, oblique or video records around an asset without implying an engineering diagnosis.
Collect thermal and corresponding visual data under suitable environmental conditions for qualified downstream interpretation.
Collect calibrated multispectral data for vegetation-index, variability or environmental workflows that will be interpreted with project context.
Services are configured around the site, required output, regulatory path and downstream user—not a fixed flight package.
High-overlap aerial imagery for mapped surfaces, site records, progress comparison and 3D reconstruction.
LiDAR and supporting imagery for terrain, vegetation, corridors, vertical assets and complex geometry.
Repeatable wide, zoom, oblique and video capture for qualified asset review and documentation.
Radiometric thermal and paired RGB capture for utilities, buildings, equipment and response workflows.
Calibrated multispectral capture for crop, vegetation, environmental and recurring monitoring workflows.
Repeat missions using controlled routes, viewpoints, naming and handoff standards across project dates.
Not every project includes every output. The statement of work should define source data, processing, quality checks, coordinate reference, file formats, limitations and acceptance responsibility.
Organized RGB, thermal or multispectral files with capture logs and available positioning metadata.
A georeferenced image mosaic processed from suitable overlapping imagery and the agreed positioning workflow.
Photogrammetric or LiDAR point data delivered in agreed formats, with classification only where scoped.
DSM, DTM or other elevation-oriented outputs where the dataset, processing and project scope support them.
Mesh, textured model or another spatial visualization prepared for the agreed review or communication use.
Indexed wide, zoom, thermal or oblique imagery organized by asset, location, viewpoint or observation.
Calibrated band products, index maps or field-variability layers prepared for qualified interpretation.
Scope assumptions, capture conditions, processing context, checks, file inventory and known limitations.
The collection plan connects the deliverable to the site, aircraft, sensor, crew, processing and handoff. Changes are reviewed before they affect coverage or output quality.
Every industry uses aerial data differently. The same sensor can require a different route, timing, quality check and deliverable when the decision changes.
Progress documentation, site context, earthwork records and repeatable project imagery.
Visual, zoom, thermal and spatial records for qualified asset-review workflows.
Site mapping, terrain, stockpile, pit, haul-road and recurring change documentation.
Terrain, canopy, vegetation, habitat, erosion and project-specific monitoring data.
Field mapping, multispectral variability, drainage context and repeat seasonal capture.
Site awareness, damage documentation, thermal context and time-sensitive aerial records.
Useful data is traceable. The project should record how it was collected, what checks were completed, which assumptions apply and where qualified interpretation is still required.
Confirm horizontal and vertical reference, units, control context and required transformations.
Review coverage, blur, alignment, control/checkpoints, density or thermal context as applicable.
Retain flight, sensor, weather, calibration, site and deviation information appropriate to scope.
Plan access, storage, transfer, retention and privacy controls around the client’s requirements.
State occlusions, inaccessible areas, environmental effects, processing assumptions and exclusions.
Identify who checks the handoff and what evidence confirms the agreed deliverable is complete.
Aerial data quality depends on the complete workflow—not only the aircraft or camera.
Projects can be considered for RGB mapping, oblique imagery, visual inspection, LiDAR, radiometric thermal, multispectral and recurring progress capture. Feasibility depends on the site, system, regulatory path and intended deliverable.
Either can be scoped. A project may include organized source data, processing, selected outputs, QA notes and metadata. The quotation will identify exactly what is and is not included.
No. Accuracy depends on the aircraft, sensor, flight geometry, positioning, control, coordinate reference, processing and validation. Any regulated surveying requirement must be identified and completed under the appropriate professional framework.
Thermal capture can document apparent temperature patterns under the collection conditions. Diagnosis, compliance determination or engineering interpretation must be completed by the appropriately qualified client or professional.
Yes. Recurring projects can use controlled routes, viewpoints, settings, naming and delivery structures. Weather, site change, airspace and sensor availability can still affect repeatability.
The operating path is reviewed during project planning. Additional compliance, controlled-airspace, Level 1 Complex or SFOC-RPAS support can be scoped when the mission requires it. Final permissions remain with the responsible authorities.
Collection purpose, access, personal information, storage, transfer and retention requirements should be established before flight. Confidentiality and secure-transfer requirements can be addressed in the project scope.
Provide the site location and area, decision or deliverable, accuracy/detail expectations, coordinate reference, preferred timing, sensor preference, access conditions, required formats and downstream software.
Share the location, required output, timing and intended use. Unmanned Canada can recommend an appropriate capture and delivery workflow.
Unmanned Canada can also help organizations configure the aircraft, payload, software, training and compliance needed to build data collection in-house.
