RTK vs PPK Drone Surveying: Accuracy & Workflow

A lone GNSS receiver cannot reach survey accuracy because the satellite signal is degraded on its way down by the ionosphere, the atmosphere, clock errors and orbit uncertainty. The fix for all of these is a second receiver at a known position, called a base, observing the same satellites at the same time. Because the base knows precisely where it sits, it can measure the error in each satellite signal and pass that correction to the moving receiver, the rover, on the aircraft. Resolve the carrier-phase ambiguity well and the rover positions can reach centimetre-class accuracy in good conditions, a vast improvement over standalone drone GPS.

The base reference can come from your own receiver set up over a surveyed point, or from a network. In India and elsewhere you can stream live corrections over the internet using NTRIP, drawing from a CORS network or a Continuously Operating Reference Station, so you do not always need to plant your own base. The accuracy of the whole survey ultimately rests on the quality of that reference position and the length of the baseline between base and rover; the longer and weaker the link to a known point, the more the centimetre promise erodes. This correction principle is identical for RTK and PPK.

• A known-position base measures satellite errors a lone rover cannot remove
• Carrier-phase resolution is what unlocks centimetre-class accuracy
• Base can be your own receiver or an NTRIP stream from a CORS network
• Survey accuracy depends on the reference quality and base-to-rover baseline

RTK drone GPS applies the correction in real time. The base, or an NTRIP correction stream, sends data to the rover continuously while the aircraft flies, so each photo is tagged with a corrected position the moment it is captured. The appeal is immediacy: you can see your fix status during the mission, confirm a centimetre-class solution before committing, and in some workflows skip a heavy post-processing step because the geotags are already accurate. For repetitive, time-sensitive or high-volume work where you want a finished result soon after landing, that live confidence is genuinely valuable.

The catch is dependence on an unbroken correction link throughout the flight. RTK needs a reliable radio or cellular connection between base and rover, and if that link drops, is shadowed by terrain, or suffers interference at range, the correction stops and those images revert to a coarse fix. The aircraft can fly out of radio range on a large site, and cellular NTRIP assumes usable mobile coverage at the field, which is not a given on remote Indian survey sites. RTK rewards good connectivity and punishes its absence, so it shines on accessible sites with dependable links and shorter baselines.

• Corrections arrive live, so photos are geotagged accurately in flight
• Lets you confirm fix status during the mission and reduce post-processing
• Depends on an unbroken radio or cellular correction link throughout
• Best on accessible sites with reliable connectivity and shorter baselines

PPK drone mapping flips the timing. The rover on the aircraft logs raw GNSS observations for the whole flight, the base logs its own observations independently, and no correction link is needed in the air at all. After landing you bring the two logs together in post-processing software, which aligns them in time and computes the corrected camera positions. Because the solution is calculated offline, it can run forward and backward through the data and use the full observation record, which often makes PPK more robust at recovering positions through brief satellite outages or marginal moments than a live-only RTK fix.

That resilience is PPK's headline advantage for difficult and remote work. With no real-time link to lose, the aircraft can fly long baselines and operate well beyond radio or cellular range, which matters across the large, sparsely covered survey areas common in India. The trade is workflow: you do not know the survey succeeded until you process it, so good field discipline, recording continuous logs and noting the base position carefully, is essential, and the processing step adds time and a little expertise. For demanding accuracy, weak connectivity or large sites, that extra step usually buys reliability worth having.

• Rover and base log raw data separately; no in-flight link required
• Offline processing uses the full record and is robust through brief outages
• Frees the aircraft to fly long baselines beyond radio or cellular range
• Cost is a post-processing step and disciplined field logging

Done properly, RTK and PPK reach broadly similar drone survey accuracy, often centimetre-class in good conditions, because they apply the same corrections and differ only in when. The practical accuracy difference between them is usually smaller than the difference good GCPs make. Ground Control Points, surveyed markers placed across the site, let you verify and tighten the result and are still recommended for the most demanding work and as an independent accuracy check. Even with RTK or PPK geotags, a handful of well-placed checkpoints turns a claimed accuracy into a measured, defensible one that withstands scrutiny.

Connectivity is what most often settles the choice in India. RTK over cellular NTRIP assumes usable mobile coverage at the site, and over a local radio assumes the aircraft stays within link range, neither of which holds on remote terrain, long corridors or large parcels. PPK sidesteps the live link entirely, which is why it is frequently the safer default for rural, remote and large-area Indian projects, while RTK suits well-connected urban and accessible sites where you want results fast. Either way, plan lawful operation, including DGCA and Digital Sky approvals, as part of scoping the survey rather than as an afterthought.

• Done right, RTK and PPK reach similar centimetre-class accuracy
• GCPs verify and tighten results and give an independent accuracy check
• RTK needs live coverage; PPK suits remote, low-connectivity Indian sites
• Build DGCA and Digital Sky compliance into survey planning from the start

Survey-grade positioning is a system, not a single part. A multi-frequency GNSS receiver and antenna on the aircraft capture the satellite observations, and the quality and stable mounting of that antenna strongly influence the result. The flight controller ties it together: modern open autopilots such as ArduPilot and PX4 support RTK and PPK workflows, time-stamping the camera trigger against GNSS so each photo links to a precise position, and a capable flight controller like the BotBit flight controller is the foundation that makes this possible on a custom build. For RTK specifically, a dependable correction link is part of the airframe, and BotBit telemetry antennas help maintain that data connection at range.

Let the survey requirement drive the hardware, not the reverse. Decide your accuracy target, your typical site connectivity and whether you will rely on a live link or post-process, then specify the receiver, antenna, flight controller and telemetry to match, and plan the camera-trigger timing carefully because a mistimed trigger undermines even perfect positioning. As an India-based components and UAV partner, BotBit supplies flight controllers, telemetry and GNSS-related hardware and helps operators assemble survey-capable aircraft, reviewing lawful use before configuring a complete, compliant system around your chosen RTK or PPK workflow.

• Multi-frequency GNSS receiver and a well-mounted antenna capture the data
• ArduPilot and PX4 flight controllers support RTK/PPK and camera-trigger timing
• RTK adds a reliable telemetry link; BotBit antennas help hold it at range
• Specify receiver, autopilot and telemetry from your accuracy and site needs