UgCS 6.3 is here: A single planning process handles thousands of acres of LiDAR surveying, with terrain matching and automatic calibration doubling efficiency—If you've ever taken off and landed repeatedly across hundreds of hectares, adjusting parameters yet still ending up with inconsistent point cloud data, this article is worth a read.
The pain points of surveying teams are well-known: battery life splits a large area into several segments; varying takeoff and landing points, sensor parameters drifting between flights, and lost pose tracking can mess up the entire point cloud; terrain undulations create height differences between main flight lines and bypass segments, leading to misalignment during stitching; in a multi-person, multi-task environment, version control and job visualization often feel like a bottomless pit, with the costs of information loss being astonishingly high once it occurs.
Overview of Core Improvements in UgCS 6.3
The new version extends the “large project” workflow to LiDAR measurements, allowing management of sites over 100 hectares as a single project while splitting into sub-areas; support for DJI’s Zenmuse L2 and other LiDARs automatically adds inertial measurement unit calibration actions to each sub-area; the software can configure LiDAR echo and scanning modes, reducing manual switches on site; allows for setting independent return points for each sub-area, supporting point migration operations and cross-point completion; upgraded terrain following functionality enables ground flight in bypass and overfly segments; compatible with other manufacturers' payloads and supports importing terrain elevation models and surface elevation models to assist planning. Some advanced features require expert or corporate authorization.
Why These Improvements Matter
Uniform sensor settings and automatic calibration significantly improve data consistency and reduce system errors between flight segments; single overall planning and sub-area assignments minimize repeated takeoffs, landings, and parameter adjustments; in vegetated areas, a reasonable multi-echo and scanning mode helps separate vegetation from ground points, improving ground point recovery rates; organizing processes in advance for beyond visual line-of-sight and other complex tasks aids in compliance preparation, though it does not equate to obtaining the permission itself.
Understanding Technical Details Clearly
Why is inertial measurement unit calibration crucial? Because small pose errors can be projected and magnified into point cloud coordinate offsets, minor roll errors at several hundred meters can lead to significant lateral displacements. The difference between echo mode and scanning mode is that multi-echo can record subsequent echoes that pass through vegetation, allowing recovery of obscured ground points; terrain following maintains the expected measurement height by real-time adjustments of flight altitude, reducing coverage loss over undulating terrain; importing terrain elevation models can be used to estimate power consumption, avoid obstacles, and determine a safe minimum flight height.
Demonstration of Typical Workflow (Executable Steps)
Step 1: Create a large project and import boundary and terrain elevation models; Step 2: Division of sub-areas based on terrain and battery life, assigning takeoff and return points; Step 3: Set sensor parameters (echo, scanning rate) within each sub-area and enable automatic inertial measurement unit calibration; Step 4: Export tasks to the ground station and synchronize to each aircraft, launching in sequence on site; Step 5: Data collection, stitching, and quality checks, recording calibration logs for each sub-area for subsequent post-processing traceability.
Practical Recommendations and Checklist
- Mandatory inertial measurement unit and reference star positioning checks before each large-scale operation;
- Prioritize enabling multi-echo and denser lateral overlaps for vegetated plots;
- Reserve backup batteries for critical sub-areas and plan reasonable return points;
- Utilize terrain elevation models in UgCS to simulate minimum safe heights before flights;
- Retain snapshots of sensor and calibration parameters for each sub-area for easier comparisons later.
Software can optimize workflows but cannot replace regulatory permissions: independent return points do not equate to obtaining beyond visual line-of-sight permissions; some features depend on specific payloads or advanced authorizations; complex terrain and strong winds still require manual intervention and ground measurement verification; the final data quality still relies on the sensor's performance and post-processing software.
Summary and Action Guidance
Who benefits the most? Teams engaged in large-scale infrastructure surveying, forestry, and power inspections, particularly those needing to cross battery cycles, conduct multi-point returns, or extract ground points under vegetation. When to upgrade? Consider upgrading to UgCS 6.3 and acquiring the appropriate authorizations when you frequently face the same site being broken down into countless small segments, when data consistency is hard to ensure, or when high-quality point clouds are needed in complex terrains. Future updates worth noting include deeper integration of software and sensors, automated post-processing, and advancing regulatory supports.
Appendix: Suggested search terms—principle of inertial measurement units, multi-echo point cloud processing, differences between terrain elevation models and surface elevation models. Remember this: UgCS 6.3 is not just about adding a few settings, but transforming hundreds of hectares of surveying from “doing multiple scattered tasks” into a “puzzle-like” holistic operation.
