1. Why this question actually matters
Replace with your field photo showing both RTK base and drone
Every professional drone survey operator eventually faces the RTK vs PPK decision — often under pressure, on-site, with a client waiting for results. The answer they find in most online content is a polished non-answer: both methods deliver centimetre-level accuracy, it depends on your project, here is a comparison table. That is technically correct and operationally useless.
The real question is not which technology is better in a vacuum. It is: given your specific environment, equipment, infrastructure, and deliverable requirement — which method is actually going to give you reliable, defensible survey data on this mission? The answer changes depending on whether you are mapping a construction site in Georgetown with 4G coverage and a clear sky, or flying a stockpile survey 200 km into Guyana’s interior with no CORS network, intermittent radio contact, and a charter flight window that does not accommodate re-flights.
2. What RTK and PPK actually are — the technical foundation
Replace with a diagram showing real-time vs post-processed correction paths
Both RTK and PPK are methods for achieving centimetre-level GNSS positioning accuracy. Standard GPS — the kind built into consumer electronics — delivers accuracy in the range of 1–5 metres outdoors. Professional survey work requires accuracy of 1–3 cm horizontal and 2–4 cm vertical. The gap between those two figures is bridged by carrier-phase correction techniques, of which RTK and PPK are the two dominant variants in UAV operations.
Both methods work on the same underlying principle: a base station at a known, fixed location on the ground records GNSS satellite observations simultaneously with the drone in flight. The base station’s known position allows calculation of the exact error affecting the GNSS signal at that moment — atmospheric delays, satellite clock errors, orbital errors — and those corrections are applied to the drone’s raw position data to produce centimetre-accurate geotagged image coordinates. The difference between RTK and PPK is entirely about when those corrections are applied.
2.1 RTK — Real-Time Kinematic
In RTK, the base station transmits its correction data to the drone in real time during the flight, via radio link from the base station to the remote controller, and from the controller to the aircraft. The drone’s GNSS receiver fuses these corrections on the fly, producing corrected image geotags as each photo is taken.
This requires four simultaneous communication links to be maintained at all times:
- Satellite signals to the drone’s GNSS receiver
- Satellite signals to the base station
- Base station to remote controller (radio/internet correction stream)
- Remote controller to drone (link between correction data and onboard receiver)
If any of these links degrades or breaks, the RTK solution downgrades from ‘fixed’ to ‘float’ or drops to standalone GPS entirely. This is the critical operational vulnerability of RTK, and it is far more common in field conditions than most pre-sale demonstrations suggest.
2.2 PPK — Post-Processed Kinematic
In PPK, the base station and the drone each independently record their raw GNSS observation data throughout the flight. No real-time communication link between them is required during the mission. After the flight, the two raw data files are combined in post-processing software, which resolves the carrier-phase ambiguities and applies corrections retroactively.
The critical structural advantage of PPK is that it decouples data collection from correction. If the drone’s radio link to the base station is interrupted mid-flight, the raw GNSS logs from both receivers continue uninterrupted. Nothing is lost. The corrections are applied in the office, to complete data, not to a fragmented real-time stream.
2.3 RTK fix vs float — the number most reviews skip
The single most important technical distinction that operators need to understand is the difference between an RTK fixed solution and an RTK float solution. It determines whether your RTK data is survey-grade or nearly useless, and the distinction is invisible in the imagery itself — it only appears in the flight log.
| Solution type | Typical H accuracy | Typical V accuracy | Survey-grade? |
|---|---|---|---|
| Standalone GPS | 1–5 metres | 3–10 metres | No |
| RTK Float | Decimetres to ~1 m | Decimetres to metres | No |
| RTK Fixed / PPK Fixed | 1–2 cm | 2–4 cm | Yes |
A float solution can have errors of decimetres to over a metre. It is not centimetre-accurate data, regardless of what the drone’s display shows. When the solution transitions from fixed to floating conditions, errors can reach decimetre or even metre level. There is additionally a documented phenomenon called a ‘false fix’, where the receiver reports a fixed solution but the underlying ambiguity resolution has failed — producing errors at metre scale while displaying centimetre-level confidence.
3. Accuracy numbers — what the research actually shows
Both RTK and PPK, when properly executed, deliver comparable final accuracy: 1–2 cm horizontal and 2–4 cm vertical under good conditions with a fixed solution. Post-processed volumetric accuracy for stockpile surveys is typically within 1–3% of ground-truth methods. These numbers assume correct execution.
3.1 Baseline length — the distance factor
RTK accuracy degrades with increasing distance between the drone and the base station, following a predictable formula: approximately 0.5 mm of additional horizontal error per kilometre of baseline (0.5 ppm), and 1.0 mm of additional vertical error per kilometre (1.0 ppm).
| Baseline | H accuracy | V accuracy | Practical note |
|---|---|---|---|
| 0 km (at base) | ~0.6 cm | ~1.0 cm | Optimal — stable fix |
| 5 km | ~0.9 cm | ~1.5 cm | Standard coastal ops |
| 10 km | ~1.1 cm | ~2.0 cm | Acceptable single-base |
| 20 km | ~1.6 cm | ~3.0 cm | Marginal — monitor fix |
| 50 km | ~3.1 cm | ~6.0 cm | Use PPK; RTK unreliable |
PPK is substantially more tolerant of baseline length because the corrections are resolved post-flight using full observation data and more sophisticated atmospheric modelling. PPK maintains survey-grade accuracy at baselines up to 100 km under good satellite geometry — a practical distinction that matters enormously for Guyana interior operations.
3.2 What happens when RTK signal is interrupted
A one-second interruption does not just degrade that one second of data. RTK requires re-initialisation to recover a fixed solution after a dropout — typically 30–90 seconds in good open-sky conditions. During re-initialisation the system is in float mode. In obstructed environments, re-initialisation may not complete before the next interruption.
Images geotagged during an RTK float or standalone period are included in the photogrammetric reconstruction with incorrect coordinates. In Metashape or DJI Terra, they are processed alongside correctly geotagged images without any visual flag. The resulting orthomosaic and point cloud will contain positional errors that are impossible to detect without independent checkpoints.
Always verify RTK solution status in the flight log before declaring a dataset survey-grade. Never rely on visual inspection of the imagery alone.
4. When to use RTK — the conditions that actually support it
Replace with your photo of M4E flying an accessible site with RTK 3 visible
RTK is the right primary method when the following conditions are genuinely met, not just assumed:
- Clear sky above the survey area — less than 20% obstruction above 15° elevation angle throughout the entire mission, not just at the launch point
- Stable communication link — radio link between base and controller confirmed at all points in the flight plan before takeoff
- Short baseline — base station within 10 km of the survey area for reliable fixed solution in tropical atmospheric conditions
- Confirmed RTK fix before takeoff — do not begin the mapping mission until the aircraft has reported fixed solution status for at least 60 continuous seconds
- Real-time results required — the client or workflow needs corrected data immediately on landing
- CORS network available — or own base station on a known point within baseline limits
4.1 RTK on active construction sites
For construction earthworks progress monitoring, RTK offers a genuine workflow advantage: the site manager can review preliminary data on the remote controller immediately after landing. For clients who need to make same-day decisions — continue grading, pause for survey, re-sequence earthworks — the immediacy of RTK data has real operational value.
4.2 RTK for smaller, well-defined sites
Sites under approximately 50 hectares, well within radio range of the base station and with good sky visibility, are the natural RTK use case. The entire site is covered before atmospheric conditions or link stability have opportunity to degrade.
5. When to use PPK — the cases where it is the superior method
PPK is not a fallback for when RTK fails. It is the technically superior method in a significant range of professional survey scenarios.
5.1 Remote operations without CORS infrastructure
Replace with your own interior field deployment photo
Guyana has no national CORS network. This is not unusual — the majority of developing-world mining, O&G, and construction markets operate without continuous GNSS reference infrastructure. In these environments, PPK removes the requirement for a stable real-time link. The base logs continuously and independently. If the radio link drops, the logging continues. In Guyana interior operations, where radio link reliability over forest clearings is unpredictable and re-flight is not an option, PPK is the only workflow that provides reliable survey-grade results.
5.2 Large-area surveys and extended baselines
When a survey area is large enough that the drone is consistently flying at the edge of reliable radio range, PPK is structurally more reliable. The drone and base station operate independently; the only requirement is that both are logging continuously.
5.3 High-value missions where re-flight is not viable
For mining clients paying for a helicopter mobilisation to an interior site, or for O&G clients with a narrow access window, a failed RTK dataset is not just inconvenient — it is a contractual and commercial problem. PPK eliminates the single point of failure that causes RTK datasets to fail: the real-time communication link.
5.4 PPK as the QA backstop for RTK data
On the DJI Matrice 4E, the aircraft logs raw GNSS observation data simultaneously with RTK correction reception. The DJI RTK 3 base station logs raw observation data continuously. This means that every RTK mission is also, automatically, a PPK mission in waiting — as long as the operator collects the base station log file before departing the site.
6. The workflows — step by step
6.1 RTK workflow — DJI M4E + DJI RTK 3
- Position the DJI RTK 3 at a known surveyed point with full sky view. If no known point is available, allow minimum 15–30 minutes of position averaging.
- Set the RTK 3 to base station mode. Confirm it is logging satellite observations continuously.
- Record the base station coordinates and logging start time. You will need these for PPK processing if required.
- Establish radio link to the RC Plus 2. Confirm signal strength in DJI Pilot 2.
- Power on the M4E. In DJI Pilot 2, confirm Fix RTK (not Float or Single) is selected.
- Wait for RTK Fixed solution status. Do not begin the mission until ‘Fixed’ has been stable for at least 60 seconds.
- Verify satellite count (aim for 12+ on both drone and base station).
- Note the RTK solution status at takeoff — photograph the RC Plus 2 screen as a timestamped record.
- Launch automated mapping mission. Monitor RTK solution status throughout — the top bar shows Fixed, Float, or Single at all times.
- If status drops to Float, note the timestamp. Do not abort unless Float is sustained for more than 2 minutes.
- Sustained Float triggers PPK post-processing as primary accuracy method for affected flight lines.
- Complete mission. Do not power down the base station before the drone lands.
- Download mission images from M4E storage to laptop.
- Connect DJI RTK 3 via USB. Download the base station raw observation file (DAT format).
- Review the flight log in DJI Pilot 2. Note all timestamp ranges where solution was Float or Single.
- If any Float periods are present, proceed to PPK processing for the complete dataset.
6.2 PPK workflow — DJI M4E + DJI Terra
Replace with your own screenshot of the PPK quality report in DJI Terra
- Set DJI RTK 3 to base station mode and confirm it is logging raw satellite observations. The base must log continuously for the entire duration of all flights.
- Record base station start time, coordinates, and antenna height above the monument or benchmark.
- If using an Emlid RS2+ or third-party receiver: configure to log RINEX format observations at 1-second intervals.
- Execute the mapping mission normally. RTK corrections can be active during flight for navigation quality.
- The M4E records a PPKRAW.bin file in the same folder as the mission images. Do not delete it.
- Verify at mission completion that the PPKRAW.bin file is present in the image folder.
- Download images and PPKRAW.bin from the M4E to a dedicated mission folder.
- Download base station raw data — DAT file from DJI RTK 3, or RINEX .obs from third-party base.
- For Emlid RS2+: export RINEX from Emlid Flow. Rename file extension from .YYO or .23O to .obs — DJI Terra requires this specific format.
- Place both the aircraft PPKRAW.bin and the base station file in the same mission folder.
- Open DJI Terra. Create a new Photogrammetry mission and import the image folder.
- Select ‘Local PPK’ under GNSS settings. Add the base station file (DAT or .obs).
- Enter the base station known coordinates in the correct CRS. For Guyana: WGS84 / UTM Zone 21N.
- Click ‘Calculate’. Review the PPK quality report: target >95% fixed-solution images, check baseline length, confirm RMS residuals.
- Proceed with normal photogrammetric reconstruction in DJI Terra, or export corrected-geotagged images to Metashape.
- In Metashape: import corrected geotags as reference coordinates for camera alignment.
- Place at least 1–2 independent checkpoints (surveyed with GNSS rover) to validate absolute accuracy.
- Document the PPK processing log, base coordinates, baseline length, and fixed-solution percentage in your deliverable metadata.
7. Full RTK vs PPK comparison
| Factor | RTK | PPK |
|---|---|---|
| When corrections applied | During flight (real-time) | After flight (post-processing) |
| Real-time link required | Yes — radio or NTRIP to base | No — base and drone log independently |
| Typical accuracy (fixed) | 1–2 cm H, 2–4 cm V | 1–2 cm H, 2–4 cm V |
| Float/dropout consequence | Data degraded to dm–m | No impact — full log intact |
| False fix risk | Yes — rare but documented | Lower — post-processing has more checks |
| Max practical baseline | 10–20 km (single base) | Up to 100 km with good processing |
| CORS network required | Needed for long baselines | Not required — own base sufficient |
| Results availability | Immediate on landing | After office processing (30–90 min) |
| Single point of failure | Yes — communication link | No — both receivers log independently |
| Suitable for CORS-free | With own base, if baseline <20 km | Yes — primary method |
| PPK backstop possible? | Yes — if base is logging raw data | Yes — this IS the PPK workflow |
| Ideal sectors | Construction, accessible sites | Mining, O&G, remote terrain |
| DJI M4E + RTK 3 support | Yes — native integration | Yes — DJI Terra Local PPK |
| Emlid RS2+ as base | Yes — Local NTRIP Caster | Yes — RINEX export to Terra |
8. The Guyana context — operating without CORS infrastructure
Guyana has no national continuously operating reference station (CORS) network. This is relevant not just as a local detail but as a proxy for a large class of operating environments: resource-sector markets in the developing world where the survey infrastructure that operators in North America or Europe take for granted does not exist.
8.1 Coastal belt operations
In accessible coastal belt operations — construction sites on the East Bank Demerara, infrastructure surveys around Georgetown — RTK with the DJI RTK 3 on a known point is viable as a primary method. Sky view is generally good on flat coastal terrain. Baselines are typically under 5 km. RTK fix acquisition is fast and maintenance is reliable.
8.2 Interior operations — mining and O&G sector
Replace with your aerial capture of an interior mining or O&G site
Interior operations present the full range of conditions that make RTK unreliable as a primary method:
- No CORS network means the base station position is established by averaging or by occupation of a previously surveyed benchmark
- Forest clearings and riverside airstrips mean partial sky obstruction — RTK fix maintenance over sites adjacent to tall secondary growth is unpredictable
- Charter flights mean mission windows are fixed — a failed RTK dataset cannot be recovered if raw GNSS logs were not collected
- Radio link over forest terrain is less reliable than over flat coastal land
9. Where GCPs fit into this
9.1 GCPs alongside RTK/PPK
RTK and PPK both reduce the number of GCPs required — from the 8–12 typical for standard photogrammetry to 0–2 for validation checkpoints. The distinction matters:
- GCPs for accuracy correction: Placed before the flight, their coordinates correct the photogrammetric model during processing. Required when base station position accuracy is uncertain.
- Checkpoints for accuracy validation: Placed before the flight but not used in processing. Their known coordinates are compared against the processed model to generate an independent accuracy statement.
For mining stockpile volumetrics and construction earthworks, the minimum professional standard is 1–2 checkpoints per survey area, measured independently with GNSS rover or total station.
9.2 GCPs without RTK/PPK
Standard photogrammetry without RTK or PPK relies entirely on GCPs — typically 6–8 well-distributed points. The field time to place, measure, and recover them on every mission is significant. RTK and PPK exist precisely to eliminate this operational burden.
10. Decision guide — which method for your mission
RTK as primary method with PPK backstop. Confirm Fixed for 60+ seconds before starting. Place 1–2 independent checkpoints. Review flight log on landing — fall back to PPK if Float periods observed.
PPK as primary method. RTK active for navigation quality. Base station on known point — allow 30 min averaging if no benchmark. Confirm PPKRAW.bin before departing. Target >95% fixed-solution images in PPK quality report.
PPK as the only viable method. Base on surveyed benchmark; if unavailable, allow 60 minutes averaging. Pre-flight: confirm base logging active. Post-flight: collect base log before aircraft departure. Do not declare mission complete until base log file is in hand.
This is the professional risk scenario. If RTK data contains float periods and no PPK backstop exists, the dataset cannot be independently validated. Never deliver volumetric or earthworks data without a documented accuracy statement. If the base log was not collected and float periods are present: disclose to the client, recommend re-survey, and do not certify the dataset.
11. Common mistakes that compromise survey accuracy
- Declaring survey-grade results from RTK data without checking the flight log for float periods. The RTK status display during flight is not a sufficient record — download and review the full flight log.
- Forgetting to collect the base station log file before leaving the site. Once overwritten on the next mission, the PPK backstop is gone permanently.
- Setting the base at an unknown point and assuming averaged position is good enough. Averaging improves relative accuracy but absolute position may be off by metres. For audit-quality mining inventory, this matters.
- Using an incorrect coordinate reference system. Guyana operations should use WGS84 / UTM Zone 21N. Mixing CRS silently shifts the entire dataset.
- Not verifying PPKRAW.bin exists before departing the site. Check on the drone’s storage via the RC Plus 2 before powering down.
- Assuming a second flight corrects a bad first flight. If the base position was wrong, the error propagates to both datasets equally.
12. Equipment for this workflow
13. Frequently asked questions
Can I use PPK without a local base station if I download CORS data later?
Yes, in markets where CORS networks exist and make their observation data publicly available (NOAA NGS CORS in the US, for example), you can download the CORS RINEX file after the mission. In Guyana, no such network exists, so a locally deployed base station is required on every mission.
How long does PPK processing take in DJI Terra?
For a standard mapping mission of 200–500 images, PPK computation takes 2–8 minutes on a modern laptop. Full photogrammetric reconstruction (DEM, orthomosaic) takes 30–90 minutes regardless of whether input geotags are from RTK or PPK.
Does the M4E automatically save the raw GNSS log for PPK?
Yes, if the logging setting is enabled in DJI Pilot 2. The PPKRAW.bin file is created automatically in the image folder. Verify this setting before the first mission on a new aircraft or after a firmware update — it is a pre-flight checklist item, not a guaranteed default.
What accuracy can I certify from PPK data without checkpoints?
Without independent checkpoints, you cannot make a certified absolute accuracy statement — you can only report relative accuracy and theoretical accuracy based on baseline length and fixed-solution percentage. For audit-quality mining inventory, at least 1–2 independently measured checkpoints per survey area are required.
Is RTK suitable for O&G pipeline corridor surveys?
Pipeline corridors extending 20–50 km present a specific challenge: the baseline grows progressively longer as the drone moves down the corridor. PPK is the more reliable method. An alternative is pre-surveying temporary benchmarks along the corridor and using them as successive base station setups.
14. Summary
RTK and PPK achieve the same final accuracy when executed correctly. The difference is in reliability and execution requirements, not in the physics of the correction.
RTK is faster to result, better suited to accessible sites with good sky view and stable communications, and delivers immediate on-site feedback. PPK is more robust, tolerates communication failures and longer baselines, and is the standard production method for any operation where re-flight is expensive or impossible.
The answer to ‘PPK vs RTK’ is not a binary choice. It is a unified workflow: fly with RTK active, log PPK data simultaneously, review the flight log on landing, and process PPK if any doubt exists.
The redundancy is free. The confidence it provides is worth the habit.