GNSS

PPK, RTK & Network RTK

All three improve on standalone GNSS by using differential corrections—but they differ in timing (real-time vs post-process), equipment (own base vs subscription network), and how you handle dropouts in the field.

RTK (real-time)

Corrections arrive over radio, cellular, or network link while you work. Best when you need immediate stakeout, live QC, or drone flights that require fixed status before shutter. Vulnerable to link loss, baseline length, and sky obstruction.

PPK (post-processed)

Store raw observations; apply corrections in software later. Often rescues epochs when real-time links failed. Adds office time and requires disciplined file management. Common for drone mapping and some mobile campaigns.

Network RTK

Uses a commercial or public CORS-style network (VRS, MAC, etc.) instead of a local base. Reduces setup time—verify subscription coverage, datum, and latency for your accuracy class. See also GNSS & RTK overview.

ModeBest forWatch for
RTK + own baseRemote jobs, full controlBaseline limits, setup time
Network RTKUrban / covered areas with NTRIPSubscription, multipath
PPKDrones, dropped linksProcessing workflow