Overview
DroneDeploy processes data captured with Real-Time Kinematic (RTK) and Post-Processed Kinematic (PPK) technology. While these methods enhance drone positioning accuracy, proper flight planning ensures optimal results. For critical projects, combine RTK or PPK with a few well-placed Ground Control Points (GCPs) used as checkpoints to add a layer of quality control.
Flight Planning Considerations
To ensure the highest level of accuracy for your drone surveys, follow these guidelines:
Image Overlap: Maintain a consistent image overlap between 60% and 80% between adjacent flight paths. This ensures complete coverage and sufficient imagery for processing with RTK/PPK corrections.
Flight Path Boundary: Ensure at least a 50ft (15m) boundary from the edge of the target area if you capture GCPs. This ensures the software captures enough images of each GCP for accurate tagging.
Flight Altitude: Higher altitudes offer better coverage and reduce flight time, but they also reduce resolution. Adjust altitude based on the required level of detail and the physical size of your GCP markers.
Flight Settings: Enhanced 3D is only necessary if the model or point cloud requires extra facade detail.
Optimizing for RTK and PPK Flights
Maintain a Solid Internet Connection: Spotty connectivity may cause the drone to lose the RTK connection mid-flight. Use PPK workflows in areas with limited or no RTK coverage.
Check RTK Signal: Review the RTK coverage in the flight plan settings before you begin an RTK flight.
Use GCPs for Validation: While RTK improves accuracy over standard GPS, well-placed GCPs significantly improve elevation (z-axis) accuracy.
Convergence Time for PPK: Ensure the map plan allows enough time for GPS convergence based on your specific region.
Additional Tips
Disable Dewarp: Disable the Dewarp setting in the DJI Pilot 2 Camera settings when using a Mavic 3 Enterprise.
Consistent Terminology: Always use the term Ground Control Points (GCPs) on first mention and GCPs thereafter.
Visual Aids: Crop all screenshots tightly around the action to exclude proprietary information.
For further information on specific hardware, see our Mavic 3 Enterprise RTK workflow or the Phantom 4 Pro/M300/M350 RTK workflow guides.
v2.2