Work the face of the asset.
Set the wall dimensions, bearing, standoff and overlap. Choose the starting side and vertical direction.
Command & autonomy
HelloGeo Nexus
Plan the mission. Build the library. Manage the operation.
PRODUCT OVERVIEWWhat it brings
What it brings
to the workflow.
Plan façade, building, circular and survey missions with HelloGeo Nexus. Organise revisioned mission libraries, reuse routes and review connected operations.
MISSION DESIGN / UPDATED 17 OCTOBER 2026
Make the route
fit the structure.
Site → Route → Preview. Inspect the geometry from isometric, top, front and side views, then refine the mission before handoff.
Plan every side together.
Build a four-sided route from measured dimensions. Choose the start corner, travel direction and height levels.
Keep the subject in context.
Adjust radius, altitude, start angle and direction, with inward camera heading and sampled capture waypoints.
Planning illustrations. Building previews use entered measurements; circular plans use sampled waypoints. Review site clearance and transit paths before execution.
Beyond structures
Waypoint and freehand grids, target GSD, nadir and oblique passes, terrain context, camera timing and battery-aware sorties.
Explore planning capabilities ↗MISSION LIBRARY MANAGEMENT
Keep the plan.
Build on the work.
Save a named design, find it by family or search, and bring it back into the planner. Reuse creates an independent copy, keeping the original and its revision context intact.
Explore the mission librarySave. Search. Revise.
Named records, family filters, route previews and revision-aware editing.
A fresh copy. A clear history.
Review a compatible aircraft profile, camera settings and calibration. Track source revision, target profile and saved-copy status.
Pick up the next session.
Owner-scoped cloud sync, offline pending saves and explicit conflict recovery. Move library designs with portable planning JSON.
Sync runs while supported applications are active. Controller build availability applies. Planning JSON is separate from aircraft upload files; incompatible vendor formats require a new plan or explicit conversion workflow.
MISSION MANAGEMENT
From a saved design
to a reviewed operation.
Keep the route revision, preparation checks and available execution records connected throughout the workflow.
- 01
Prepare
Review the current aircraft, height reference, camera configuration and route changes.
- 02
Hand off
Check revision and checksum, then follow delivery acknowledgements in the supported controller workflow.
- 03
Review
Use mission history, saved-copy inventory, available RC receipts and live side-view telemetry where provided.
Loading a design does not transfer earlier flight permission. A saved copy or start acknowledgement does not establish a completed flight, captured media or full coverage.
NEXUS / SUPPORTED DEVICE CONFIGURATIONSDJI Dock 4.
Coverage updatedDJI Dock 4.
Matrice 5TD.
The new dock configuration joins the Nexus ecosystem with its own Cloud API 2 module.
17 October 2026
DJI Dock 4
Dock infrastructure with automated battery swapping.
DJI Matrice 5TD
The aircraft DJI specifies for Dock 4.
O4 Ground Station
Required for Dock 4, with video transmission and RTK functions.
| Dock | Supported aircraft | Nexus connection | Configuration |
|---|---|---|---|
| DJI Dock 2 | Matrice 3D / Matrice 3TD | Dock Cloud API pathway | Existing station and site commissioning |
| DJI Dock 3 | Matrice 4D / Matrice 4TD | Dock Cloud API pathway | Existing station and site commissioning |
| DJI Dock 4 | Matrice 5TD | Dedicated Cloud API 2 module | O4 Ground Station + licensed DJI base |
Nexus module scope
Dedicated Cloud API 2 configuration and commissioning workflows, with operation, recovery and history adapters. Device capabilities, licensed access and site acceptance govern availability; operational controls remain commissioning-gated.
Deployment configuration
Match the station, aircraft and firmware. Configure the licensed base, organisation access, power and network, then complete the site acceptance checks.
9 DJI RC profiles and 24 Autel profiles remain separate from the 5 dock-aircraft entries. Dock 4 uses a dedicated Cloud API 2 connection.
PLATFORM EXPLORER
The right path for your aircraft.
9 DJI RC profiles. 24 Autel profiles. Separate Dock and open-autopilot workflows.
NEXUS + VECTOR DJI
DJI enterprise, with a dedicated Dock pathway.
Plan routes, review aircraft context and pass missions through the compatible controller workflow. Dock 2, Dock 3 and Dock 4 are listed separately from the nine RC profiles.
DJI RC catalogue
Nine aircraft profiles for the NEXUS mission workspace.
- Matrice 30
- Matrice 30T
- Matrice 300 RTK
- Matrice 350 RTK
- Mavic 3 Enterprise
- Mavic 3 Thermal
- Matrice 4E
- Matrice 4T
- Matrice 400
Dock 2
Separate Cloud API aircraft pathway.
- Matrice 3D
- Matrice 3TD
Dock 3
Separate Cloud API aircraft pathway.
- Matrice 4D
- Matrice 4TD
Dock 4
Cloud API 2 configuration and commissioning. O4 Ground Station required; operational controls remain gated by site acceptance and device readiness.
- Matrice 5TD
Dock workspaces include camera/thermal, weather/RTK, power and HMS monitoring. Advanced Dock scope remains partial and requires site commissioning.
NEXUS + VECTOR AUTEL
One catalogue. Platform-specific integration.
Explore EVO II V2/V3 and enterprise families. Mission geometry, payload choices and controller handoff are checked against the selected aircraft profile.
EVO II V2
Seven V2 catalogue profiles with platform-specific controller integration.
- EVO II Pro V2
- EVO II Pro RTK V2
- EVO II Pro Enterprise V2
- EVO II Dual 640T V2
- EVO II Dual 640T RTK V2
- EVO II Dual 640T Enterprise V2
- EVO II 8K V2
EVO II V3
Six V3 catalogue profiles; verify the exact controller and payload configuration.
- EVO II Pro V3
- EVO II Pro RTK V3
- EVO II Pro Enterprise V3
- EVO II Dual 640T V3
- EVO II Dual 640T RTK V3
- EVO II Dual 640T Enterprise V3
Enterprise
Nine observed profile labels. Autel lists the EVO III Series publicly; the exact EVO III Enterprise and Titan catalogue labels still require manufacturer confirmation. A profile label does not confirm compatibility for every configuration.
- EVO Max 4T
- EVO Max 4N
- EVO Max 4T Pro
- EVO Lite 6K Enterprise
- EVO Lite 640T Enterprise
- Autel Alpha
- Autel Titan
- EVO III
- EVO III Enterprise
These 22 multirotor profiles and the two Dragonfish VTOL profiles form the 24-profile Autel catalogue. Catalogue presence is distinct from native flight qualification.
NEXUS + VECTOR AUTEL
Extend planning across longer survey areas.
Waypoint and grid planning bring camera footprint, overlap and JSON/GeoJSON mission geometry into a dedicated VTOL workflow.
Dragonfish VTOL catalogue
Two long-area survey planning profiles.
- DragonFish Standard
- DragonFish Pro
Validate the VTOL mission
Controller-specific mission conversion, transition behaviour, turns and wind limits need validation on the selected platform.
Use the exact Dragonfish aircraft, controller, payload and firmware combination for acceptance.
Source catalogue names are DragonFish Standard and DragonFish Pro. The listed planning profiles are not an all-configuration flight certification.
HELLOGEO FLIGHT
Open autopilot workflows, through Flight.
For compatible Pixhawk flight-controller hardware running ArduPilot or PX4, MAVLink provides the communication pathway. HelloGeo Flight is the published Android ground-control application in this ecosystem.
Hardware
Pixhawk is a flight-controller hardware family. Choose a board supported by the required firmware and vehicle configuration.
Firmware + protocol
ArduPilot or PX4 runs the vehicle. MAVLink carries the supported telemetry and mission exchange.
HelloGeo Flight
Mission, geofence and rally planning; vehicle setup, telemetry, diagnostics, flight logs and geotagging.
Technical references: PX4 / PixhawkArduPilot hardwareMAVLink
Flight is the MAVLink GCS pathway; VECTOR is the DJI/Autel controller layer. No universal Pixhawk board, vehicle, firmware or payload qualification is implied.
Validate your configuration. Exact aircraft, controller, firmware, payload and SDK deployment checks govern operational use. RC catalogue observations: 7 October 2026. Dock coverage updated: 15 October 2026.
CAPABILITIES / 9 FEATURE GROUPS
Go deeper into the product.
Explore the published capability areas. Product configuration and deployment scope determine availability.
01 Structure & circular planning
Turn measured site geometry into a route you can inspect and refine.
- Single façade: dimensions, bearing, standoff and image overlap
- Four-sided building: start corner, direction and multi-height levels
- Circular/orbit routes: radius, height, start angle and inward camera heading
- Site → Route → Preview, with isometric, top, front and side views
- Sampled circular waypoints; review clearance and transit before applying
02 Survey & terrain planning
Prepare coverage around the site, camera and required output.
- Waypoint and freehand grid planning
- Target GSD, overlap, heading and start/end controls
- Nadir or nadir plus four oblique passes
- DEM/DSM, surveyed launch reference and terrain review
- Camera timing and battery-aware sorties; terrain data is not live obstacle sensing
03 Mission library management
Keep reusable planning work organised in one revisioned library.
- Name, save, search and filter missions by aircraft family
- Edit, load and reload saved designs
- Retain revisions and review changes
- Import earlier vendor missions and export/import portable planning JSON
- Planning JSON is a library transfer file, not an aircraft upload file
04 Mission reuse & inventory
Create independent copies while preserving the original plan.
- Reuse with compatible same-format target profiles
- Review lens, camera interval, payload and calibration
- Saved-copy counts, source revision, target profile and copy status
- Delete records and restore as a new design
- No automatic conversion between incompatible vendors or SDK formats
05 Mission management & review
Keep preparation, delivery and review connected to the right revision.
- Current aircraft, height and camera readiness checks
- Checksum and revision checks before mission handoff
- Delivery acknowledgements and mission history
- Available RC receipts and live side-view telemetry
- A start acknowledgement is not proof of completed flight or image coverage
06 Cloud & controller continuity
Bring supported Nexus and VECTOR planning workflows together.
- Owner-scoped cloud-mediated bidirectional library sync
- Foreground sync while the application is active
- Offline pending saves and explicit conflict recovery
- Fresh execution checks after loading or reusing a plan
- Controller build and device qualification determine availability
07 DJI & Autel catalogue
Separate controller, dock and open-autopilot integration paths.
- 9 DJI RC profiles and 24 Autel-family profiles, including DragonFish
- DJI Dock 2: Matrice 3D / 3TD
- DJI Dock 3: Matrice 4D / 4TD
- DJI Dock 4: Matrice 5TD + O4 Ground Station
- Profile listings do not imply aircraft flight qualification
08 Dock 4 configuration
Dedicated Cloud API 2 configuration, commissioning/readiness, operation/recovery and extension workflows. Operational controls remain commissioning-gated.
- Matrice 5TD + DJI Dock 4 + O4 Ground Station
- Licensed base, organisation access and operator-device mapping
- Commissioning/readiness and approved-route review
- Operation/recovery history, telemetry and media adapters
- Deployment connectivity and hardware acceptance still required
09 Operational workspace
Use the mission context to coordinate supported field operations.
- Map, camera and split views with capability-bound payload choices
- Telemetry, stream health and operator authority checks
- Mission policies, finish behaviour and RC-loss review
- English, Korean and French interface preferences
- Exact aircraft/controller/payload acceptance governs live execution
Dock 4 pairs with Matrice 5TD and the required O4 Ground Station. Review the dedicated Cloud API 2 configuration, commissioning and operational workflow. Flight, capture and recovery controls require qualified hardware, site acceptance and current readiness.
PROJECT CONTEXTFrom capability
From capability
to useful work.
UAV mission planning
Define inputs, access requirements and acceptance criteria with the HelloGeo team before operational deployment.
Infrastructure inspection
Define inputs, access requirements and acceptance criteria with the HelloGeo team before operational deployment.
Geospatial operations
Define inputs, access requirements and acceptance criteria with the HelloGeo team before operational deployment.
PRODUCT RESOURCES
Explore it with your team.
IDEAS INTO OPERATIONS / 01
Change the plan.
See the difference.
Explore how a survey route, an inspection circuit and a field survey take shape. Adjust the spacing. Watch the geometry respond.
01 / SURVEY ROUTE
Coverage, by design.
A parallel survey pattern across a 220 × 140 m site. Tighter lines add distance and capture samples.
Capture sample interval: 10 m along the route.
- Site area
- 3.08 ha
- Route length
- 1,900 m
- Capture samples
- 191
- Traversal at 5 m/s
- 6 min 20 s
0%
Playback ×12. Estimate excludes turns, setup and capture dwell.
THE NEXT STEP STARTS WITH A CONVERSATIONBring us the challenge.
Bring us the challenge.
Let’s build the connection.
Your team knows the site. We know the spatial workflow. Together, we can define a practical way forward.