Inspection, Monitoring & Surveying with FlightHub 2
Collect consistently. Compare intelligently. Deliver something useful.
A drone image can show a site condition. A repeatable workflow can help a team understand what changed, where it happened and what needs attention next. DJI FlightHub 2 connects mission planning, cloud modelling and analysis tools so that field data can be reviewed in a shared operational context.
The opportunity is not simply to collect more photographs. It is to make recurring inspection, monitoring and mapping work easier to organize, compare and hand over. The limits matter too: a visual change is not automatically a defect, and a measurement displayed on a model is not automatically a validated survey result.
New to the series? Begin with Part 1: Starting and Scaling a Drone Program with DJI FlightHub 2 for project structure, team permissions, fleet visibility and mission handovers. This article focuses on what happens to the collected data.
Inspection, monitoring and surveying need different evidence.
They can share a platform without sharing the same acceptance criteria.
| Workflow | Typical question | Useful FlightHub 2 tools | What still needs checking |
|---|---|---|---|
| Inspection | What visible condition needs attention at this asset? | Waypoint planning, image/model linkage, defect tagging and reviewed reporting. | Coverage, image detail, location confidence and specialist interpretation. |
| Monitoring | What changed between visits? | Timeline comparisons, paired imagery and AI-assisted change detection. | Comparable viewpoints, lighting, seasonal effects, occlusion and whether a change matters. |
| Mapping / surveying support | What is the site's geometry, elevation, quantity or relationship to a design? | Mapping routes, cloud reconstruction, model measurements and design overlays. | Control, coordinate systems, checkpoints, accuracy requirements and deliverable suitability. |
For example, documenting visible damage on a structure is different from assessing structural integrity. A construction-progress comparison is different from a contractual quantity measurement. Define the decision and its acceptance requirements first, then choose the aircraft, sensor, collection geometry and review process.
Repeatability starts before takeoff.
A saved route is useful. A documented collection method makes the results easier to trust.
DJI describes 3D waypoint editing, area routes for broad mapping and linear routes for corridor work. Its FlightHub 2 overview also lists specialist collection options such as slope and geometric routes. Availability depends on the aircraft, payload and supported workflow; a route type appearing in a product overview is not proof that every connected device can execute it.
Plan around what must remain visible.
For repeat inspection, identify the asset or area to be compared and aim for consistent coverage, camera direction and useful detail. For mapping, set the collection method around the required outputs rather than choosing settings solely to minimize flight time.
Record the conditions that affect interpretation.
Keep context about weather, lighting, access restrictions, obstructions and meaningful site changes. A new shadow, wet surface or parked vehicle can change the appearance of a scene without indicating a damaged asset. These collection and review practices are recommendations, not automatic guarantees from the platform.
Repeat the evidence, not just the route. A repeated flight path does not ensure identical imagery if camera settings, visibility or conditions differ. Review comparability before drawing conclusions from a side-by-side view.
Use Analyzer to move from “something changed” to a reviewable finding.
DJI’s 2026 updates add comparison, search, image/model linkage and reporting capabilities.
Timeline and side-by-side comparison
DJI describes a split-screen timeline for comparing two inspection periods from the same waypoint route, plus synchronized photo and panorama comparison with the viewing angle locked.
AI Change Detection Pro
The August public-cloud update describes comparison of non-nadir photographs taken from the same waypoint. Teams can select two collection periods and draw an area of interest to focus the comparison.
Defect tagging and spatial context
DJI describes linking photographs to positions in a 3D model and surfacing historical images likely to show a selected location. That can help reviewers connect a finding to the asset context.
Search and report preparation
Manufacturer-described tools include intelligent media search and structured AI reports based on confirmed results. Use these to assist review, not to bypass it.
A flagged change is a prompt to investigate.
DJI presents Change Detection Pro for changes such as facility modifications, construction progress and material stockpiling. It also provides for manually tagging missed items. That is an important reminder: an AI result may omit something relevant, and a highlighted difference may have an ordinary explanation.
Review the original imagery, the collection context and the confidence you have in the location. Where the result affects maintenance, engineering or site decisions, assign a qualified reviewer. Creating an item in a feature called “defect tagging” does not itself establish that a physical defect has been diagnosed.
For more on this distinction, read Can AI Really Find Infrastructure Defects from Drone Images?
Deployment scope matters. DJI states that the capabilities in its August 2026 update are available in the latest public-cloud version. Do not assume matching availability in On-Premises, every plan or every aircraft configuration. Confirm the exact feature, entitlement and prerequisites before making it part of a contract or standard procedure.
A model can support surveying work. It does not validate itself.
Keep model convenience separate from demonstrated positional and measurement accuracy.
DJI describes cloud generation of 2D and 3D reality models and point clouds, alongside Analyzer tools for distance, area and volume. Its 2026 enhancements also describe surface-area measurement and design-file elevation settings. These can help a team review geometry and communicate site conditions without immediately moving every task into a separate tool.
Check the coordinate framework before comparing designs.
FlightHub 2 supports design-file overlays, including PDF and DXF in DJI’s overview. A later update describes reference-point height assignment and elevation offsets. Before using an overlay for a decision, verify the drawing version, horizontal and vertical references, scale and alignment. A drawing that looks aligned on a screen is not, by itself, proof of dimensional agreement.
Specify the measurement method.
Surface area, plan area and volume answer different questions. State which quantity is required, how it will be measured and what reference surface or boundary will be used. For repeat quantities, make the comparison method consistent and document relevant changes in coverage.
Validate against the deliverable requirement.
Agree on required accuracy, control and independent checks with the responsible survey or geospatial professional. Image resolution describes image detail; it does not establish positional accuracy. Any manufacturer's general mapping claim still needs to be evaluated against the actual sensor, collection, processing and validation method.
DJI is particularly explicit about one Analyzer feature: its target-coordinate back-calculation results are for reference only and do not replace professional surveying. Do not repurpose an image-derived coordinate as a validated survey observation.
Use our drone mapping deliverables checklist for Canadian clients to define outputs, coordinate information and quality documentation before collection.
Ask for evidence, not a label. “Survey-grade” is not a substitute for an agreed accuracy requirement, a documented method and results that demonstrate the requirement was met.
Example: recurring infrastructure-site review.
An illustrative workflow for a team checking visible conditions and site progress over time.
Define the questions and recipients.
Identify which asset views must be captured, what changes matter and whether the recipient needs photographs, a model, measurements or a reviewed finding list.
Establish a useful baseline.
Collect the initial dataset using an appropriate supported route and sensor. Check coverage and image quality before treating it as a comparison baseline.
Repeat and organize the collection.
Use a consistent mission method on later visits. Record important condition changes and identify periods that are not directly comparable.
Compare, tag and verify.
Use the supported Analyzer comparison tools to focus review. Inspect both flagged and unflagged areas, relate observations to the asset and confirm findings with the appropriate reviewer.
Deliver a reviewed result.
Provide the evidence, its collection dates, location context, limitations and the action owner. Review any generated report for unsupported conclusions or missing context.
Where the value appears
The useful outcome is a clearer handover: the recipient can see what was observed, compare it with an earlier visit and understand what needs follow-up. This is a proposed process, not a customer deployment or a guarantee that the platform automatically performs every step.
For construction monitoring, that could mean documenting a visible layout change. For an inspection team, it could mean organizing evidence for a specialist's review. For mapping support, it could mean delivering a model with documented validation rather than an unexplained measurement screenshot.
Test the full path from collection to deliverable.
Do not stop the evaluation when the aircraft connects or the model appears.
Collection and platform
- Confirm the aircraft, payload, route type and firmware support the intended workflow.
- Check public-cloud or On-Premises feature availability and applicable plan entitlements.
- Budget storage, mapping and other applicable usage allowances for repeat visits.
- Test uploads, processing and access with realistic connectivity and dataset sizes.
Evidence and handover
- Agree on coverage, image quality and comparison requirements.
- Validate coordinates, control and accuracy where measurements matter.
- Assign responsibility for reviewing AI suggestions and approving reports.
- Test required exports, client access and downstream software before promising a deliverable.
DJI’s August update also describes a configurable workflow canvas for chaining scheduled collection, analysis and notifications. That can be relevant after a manual process is proven. Treat automation as a separate commissioning task: test its triggers, exceptions and recipients, and retain the human review needed for consequential findings.
For the organizational foundation, return to Part 1 of our FlightHub 2 series. For sensitive datasets, consult your responsible IT/security team and our DJI Enterprise data-security guide for Canadian buyers.
Inspection, monitoring and mapping FAQs
Can FlightHub 2 compare oblique photographs?
DJI’s August 2026 public-cloud update describes Change Detection Pro support for non-nadir photographs taken from the same waypoint, with two collection periods and a selectable comparison area. Confirm availability and data prerequisites in your deployment.
Does AI change detection prove an asset is damaged?
No. It can highlight differences for review. A difference may reflect normal site activity, lighting, occlusion or a physical change. Determining significance or diagnosing a defect requires appropriate evidence and interpretation.
Can a repeated route guarantee a valid comparison?
No. Consistent viewpoints help, but visibility, camera settings, coverage and environmental conditions still affect the result. Check comparability rather than relying only on the route name.
Can FlightHub 2 support surveying workflows?
It offers mapping, modelling, measurement and design-review tools that can support parts of a workflow. Whether an output meets a survey requirement depends on the complete method and validation. DJI explicitly says target-coordinate back-calculation does not replace professional surveying.
Does FlightHub 2 replace every specialist processing tool?
Do not assume that. Test required outputs, formats, coordinate information, quality checks and downstream use against the actual assignment. Retain specialist tools where the workflow requires capabilities you have not demonstrated in FlightHub 2.
Are these features identical in public cloud and On-Premises?
No feature parity is assumed here. The August source explicitly identifies its capabilities as public-cloud features. Verify current documentation and entitlements for the architecture you intend to use.
Build the program and the deliverable together.
Part 1: Fleet and program foundations
Start and scale a FlightHub 2 drone program with clear projects, permissions and handovers.
Define the mapping output
Know what to request from a mapping assignment, including coordinate and quality documentation.
Understand AI's limits
Separate AI-assisted observations from confirmed defects before reporting them.
Learn from a documented project
Read our Toronto Pearson 2022 M300 RTK runway-inspection case study for collection and deliverable context. It is not presented as a FlightHub 2 deployment.
Part 3 of this planned FlightHub 2 series will focus on public safety and security: shared live information, coordination and responsible operational use. Its link will be added when the article is available.
Official DJI sources
- August 2026 FlightHub 2 update: Copilot, Change Detection Pro and a smarter Analyzer. Supports non-nadir comparison, defect tagging, model/media linkage, reports, reference-only target coordinates and the stated public-cloud scope. Source of the Change Detection Pro screenshot.
- 2026 FlightHub 2 update: Analyzer enhancements. Supports timeline split-screen, synchronized comparisons, surface-area measurement and design elevation settings. Source of the construction comparison screenshot.
- FlightHub 2: A New Era of Cloud-Based Drone Intelligence. Supports route-planning, cloud-modelling, PDF/DXF overlay and analysis descriptions.
- FlightHub 2 Master Video Series. Manufacturer tutorials covering setup, modelling, collaboration and construction-project analysis.
- FlightHub 2 public-cloud release notes. Current-version reference linked by DJI's update; consult it when checking deployment compatibility.
Prepared November 2026. Product descriptions are based on DJI manufacturer sources, not independent performance validation. Features, entitlements, device support and processing requirements can change. Examples and recommended review processes are editorial guidance, not documented customer deployments. Image credits identify DJI Enterprise as the source; no open reuse licence is asserted. The images are manufacturer interface illustrations, not evidence of Canadian adoption. This article does not certify survey accuracy, diagnose asset condition or grant flight authorization.
Make repeat missions deliver better decisions.
Talk with Unmanned Canada about your assets, collection needs and reporting requirements. Start with the output you need, then evaluate the aircraft, software and review process that can support it.
