Position, Velocity, and Time (PVT) represents the three fundamental outputs that GNSS receivers provide from processing satellite signals, together forming a complete description of the receiver’s state in space and time. While ‘position’ often dominates discussion of GNSS applications, velocity and time outputs are equally important for many use cases and are inherently computed as part of the positioning process.
Position output specifies where the receiver is located, typically expressed as latitude, longitude, and altitude (LLA) or as Cartesian coordinates (X, Y, Z) in Earth-centered reference frames. The position solution results from processing pseudorange measurements to multiple satellites, solving for three spatial coordinates plus the receiver clock offset. Position accuracy ranges from several meters (standalone GNSS) to centimeters (RTK/PPP) depending on techniques and corrections applied.
Velocity output specifies how fast and in what direction the receiver is moving. GNSS receivers derive velocity from Doppler shift measurements, the frequency change of satellite signals caused by relative motion between satellites and receiver. Doppler-derived velocity is actually more accurate and more immediately available than position, since velocity computation doesn’t require the same extensive error modeling. Velocity information is essential for navigation, trajectory planning, attitude estimation (when combined with antenna arrays), and dynamic applications.
Time output specifies when the position and velocity apply, synchronized to GNSS time systems traceable to Coordinated Universal Time (UTC). The timing solution is inherently computed as part of position determination since the receiver clock offset is solved simultaneously with spatial coordinates. GNSS timing accuracy, typically tens of nanoseconds for standard receivers, enables applications including telecommunications network synchronization, financial transaction timestamping, power grid coordination, and scientific data correlation. Many critical infrastructure systems depend on GNSS for timing even when positioning capability is irrelevant to their mission.
