Why Radar Speed Readings Differ from GPS Speed

A radar sensor and a Global Positioning System (GPS) receiver can show different speeds even when both are working correctly. A stationary Doppler radar measures the vehicle’s speed component along the radar beam at a particular moment. A GPS receiver estimates speed over ground from satellite measurements and then applies its own update rate, filtering, and display logic. Mounting angle, signal conditions, timing, target selection, rounding, and acceleration can therefore create a visible difference.

The right question is not simply “Which one is correct?” It is “Are both devices measuring the same vehicle, over the same time interval, under suitable conditions?”

What Does a Doppler Speed Radar Measure?

A continuous-wave (CW) traffic radar transmits a radio signal toward the road. When that signal reflects from a moving vehicle, its frequency shifts. The radar uses this Doppler shift to calculate relative radial speed: the part of the vehicle’s motion directed toward or away from the antenna.

For a stationary roadside radar, the ideal geometry is a vehicle moving directly along the radar beam axis. If the vehicle path and beam form an angle, the sensor measures:

Radar speed = true vehicle speed × cos(θ)

where θ is the angle between the vehicle’s direction of travel and the radar beam axis. This is the stationary cosine effect. It normally makes the radar value lower than the vehicle’s true road speed, not higher.

The effect is small at a few degrees but grows as the angle increases:

These are theoretical values before rounding and any configured angle compensation. They show why a radar mounted far to the side of a lane, pointed across a curve, or tilted incorrectly can disagree consistently with GPS.

What Does GPS Speed Measure?

A GPS receiver determines motion relative to the Earth using signals from multiple satellites. Receiver implementation varies: speed may be derived from changes in satellite measurements, changes in calculated position, or a combination processed by the receiver’s navigation engine. The value shown to the user is usually speed over ground rather than wheel speed.

GPS itself can support very accurate velocity information, but the number displayed by a phone, navigation unit, tracker, or test instrument also depends on:

• Satellite geometry and the number of usable signals
• Buildings, bridges, trees, tunnels, and terrain blocking the sky
• Reflected signals, known as multipath
• Receiver antenna, chipset, firmware, and navigation algorithm
• Update rate and smoothing
• Whether the device uses GPS alone or several Global Navigation Satellite Systems (GNSS)
• How the application rounds and refreshes the displayed value

GPS.gov states that end-user speed accuracy depends on satellite geometry, blockage, atmospheric conditions, and receiver design. Its published in-space user range-rate performance is not a guarantee for a particular phone or vehicle receiver. A high-quality test receiver on an open road and a consumer phone beside a windshield pillar should not be treated as equivalent reference instruments.

Radar Speed vs. GPS Speed at a Glance

Seven Reasons the Numbers May Differ

1. Radar Installation Angle

Cosine error is the first item to check when radar reads consistently lower. Measure the real horizontal and vertical angle between the radar axis and the vehicle path at the comparison point. Do not estimate it only from the bracket. Road slope, lateral offset, sign height, and curvature all contribute to the three-dimensional angle.

Angle compensation can be useful when supported, but it should match measured geometry. Excessive compensation can create a new error, especially where the target angle changes substantially as the vehicle approaches.

2. The Two Devices Are Not Showing the Same Moment

Radar data may update several times per second, while a GPS display may refresh at 1 Hz or another configured rate. The GPS application may also smooth several measurements before changing the screen. During acceleration or braking, the radar could be showing a recent instantaneous value while the GPS screen still represents an earlier or averaged value.

This is why a valid comparison requires steady speed for several seconds. Photographing two screens at an arbitrary instant during acceleration does not establish measurement error.

3. GPS Signal Quality and Multipath

Trees, buildings, bridges, sound barriers, and tunnels can block satellite signals. Signals reflected from walls or other structures travel a different path before reaching the receiver, which can degrade the navigation solution. The speed display may jump, freeze, lag, or briefly become less stable.

Run comparison tests under open sky. Record the receiver’s satellite status and reported accuracy if available. A phone mounted deep inside a vehicle is useful for everyday navigation, but it is not automatically a traceable speed reference.

4. The Radar May Be Measuring Another Vehicle

A radar beam can contain more than one moving target. Depending on the radar design and target-selection logic, a larger truck, closer vehicle, faster vehicle, or stronger reflection may dominate the output. The GPS receiver, however, reports only the motion of the vehicle carrying it.

Use an isolated test vehicle whenever possible. If other traffic enters the beam, a difference between radar and GPS may be a target-association problem rather than a speed-calculation problem. A wide beam that covers several lanes does not automatically identify which lane produced the displayed value.

5. Radar Alignment, Vibration, and Surroundings

A loose mounting bracket can move the beam and introduce vibration-related responses. Fans, swaying signs, moving gates, and nearby machinery can create unwanted Doppler components. Metal barriers, sign structures, and unsuitable covers can reflect, block, or redirect radio-frequency energy.

Inspect the mechanical installation before changing software parameters. Point the antenna toward the intended approach, keep its forward field clear, and confirm that the enclosure material is suitable for the radar frequency.

6. Display Filtering, Hold Time, and Rounding

The raw radar value may not be the value shown on an LED speed sign. A controller can apply direction selection, minimum speed, frame validation, averaging, peak capture, hold time, or overspeed logic. It may then round a decimal radar value to a whole number.

The GPS application performs its own filtering and rounding. A raw radar result of 49.6 km/h, a controller display of 50 km/h, and a GPS screen of 49 km/h may all originate from values that differ by less than one displayed unit.

Before troubleshooting the sensor, compare raw timestamped radar frames with logged GPS data rather than comparing only two rounded screens.

7. Units and Configuration

A km/h-versus-mph setting creates an obvious large discrepancy, but smaller configuration differences are also possible. Confirm the speed unit, output direction, baud rate, angle compensation, sensitivity, controller scale, and decimal handling. Check whether the display is programmed to hold the maximum detected value while the GPS screen continues updating.

Do Not Use the Vehicle Speedometer as the Only Reference

A dashboard speedometer is a third measurement system. It generally estimates vehicle speed from wheel or drivetrain information, so tire circumference, pressure, wear, wheel size, calibration, and manufacturer display strategy can affect the result. The dashboard, GPS, and radar may therefore show three different numbers.

For engineering validation, use an appropriate calibrated or validated reference method and document its uncertainty. A consumer GPS application can be valuable for initial checks, but it should not automatically be treated as the final calibration standard. Requirements for legal metrology or enforcement are separate and depend on applicable regulations, approvals, test procedures, and jurisdiction.

A Better Way to Compare Radar and GPS

Use a repeatable test instead of a single drive-by observation:

1. Choose a straight, level section of road with open sky and minimal surrounding traffic.
2. Confirm the radar model and settings, including unit, direction mode, sensitivity, output rate, and any angle compensation.
3. Measure the installation geometry rather than estimating the beam-to-road angle.
4. Use one isolated test vehicle and keep other moving targets outside the beam.
5. Use a suitable GPS/GNSS logger with known update rate and access to timestamped data.
6. Maintain several stable speeds for long enough to remove acceleration and display-lag effects.
7. Log raw radar frames and GPS records with synchronized time where practical.
8. Repeat each speed in both directions if the application uses approaching and departing targets.
9. Compare stable intervals statistically, not only the largest difference between two screens.
10. Adjust one variable at a time and repeat the test after any mounting or parameter change.

The test report should include the radar position, vehicle path, angle, distance, GPS receiver, update rate, weather, traffic, software versions, and raw records. Without this context, a statement such as “GPS showed 52 and radar showed 50” is difficult to diagnose.

Troubleshooting Radar-GPS Differences

ZLYRADAR Speed Sensor Integration Notes

The ZLYTR20 is a 24GHz CW speed measurement radar commonly integrated into LED radar speed signs and traffic warnings. It supports RS485 and 3.3V TTL UART, with a default baud rate of 9600 bps. Under suitable target and installation conditions, its specified detection distance can exceed 180 meters, its speed range is 1–240 km/h, and its specified measurement error is within ±1 km/h when target motion is aligned with the radar beam.

Those conditions matter. A completed speed sign combines radar measurement with installation geometry, communication parsing, and display-controller logic. System integrators should validate the entire chain rather than treating the sensor specification as a guarantee for every road layout.

For a focused long-range approach, ZLYTR22 may be considered depending on the project. It supports RS485 and RS232, covers 2–320 km/h, and has a narrow road-horizontal beam in its standard orientation. Model selection should be based on road geometry and target behavior, not on a GPS comparison alone.

Frequently Asked Questions

Is GPS speed always more accurate than radar speed?

No. Both can be accurate under suitable conditions, and both can be affected by their installation or operating environment. Radar depends strongly on beam alignment and target selection. A GPS device depends on satellite geometry, signal visibility, receiver quality, update rate, and software filtering. The test method determines whether the comparison is meaningful.

Why does radar often read lower than GPS?

For a stationary radar, the most common geometric reason is cosine effect. The sensor measures speed along its beam axis, so an angle between the beam and vehicle path reduces the indicated value. GPS estimates speed over ground and is not affected by that radar mounting angle. Rounding and timing can add further differences.

Is a 1–2 km/h difference normal?

A small temporary difference can result from rounding, asynchronous updates, filtering, or minor geometry. It should not be declared acceptable or unacceptable without considering the specified sensor accuracy, reference uncertainty, installation angle, test speed, and project requirement. Use synchronized raw data and repeated steady-speed runs before reaching a conclusion.

Can I calibrate a traffic radar with a phone GPS app?

A phone app is useful for an initial functional check, but it is not automatically a calibrated reference. Phone placement, satellite visibility, chipset quality, app update rate, and smoothing all matter. Formal calibration or compliance testing should use an appropriate validated reference and follow the applicable procedure for the project and jurisdiction.

Why does the radar value drop as the vehicle gets close?

If the radar is beside or above the road, the angle between its beam and the vehicle path may grow as the vehicle approaches. The measured radial component then falls even if true road speed remains constant. Define a suitable comparison zone and align the radar along the approach rather than testing directly beside it.

Can angle compensation make radar and GPS match exactly?

Angle compensation can correct a known, stable geometric offset, but it cannot fix a changing angle, wrong target, GPS lag, poor satellite reception, or controller filtering. Measure the installation first, apply only supported settings, and validate at several speeds and distances. Do not tune compensation merely to match one observed GPS number.

Conclusion

Radar and GPS do not observe vehicle speed in the same way. A stationary Doppler radar measures radial speed along its beam; a GPS receiver estimates speed over ground and presents a filtered, device-dependent result. Angle, time alignment, signal environment, target selection, and display processing explain most apparent disagreements.

For a reliable comparison, use one vehicle, open sky, steady speed, measured radar geometry, synchronized raw records, and repeated runs. If the difference remains outside the project’s expected uncertainty, troubleshoot the radar, controller, and GPS reference as a complete measurement system.

Discuss Your Speed Measurement Application

Send ZLYRADAR your road drawing, number of lanes, required detection distance, radar mounting position, beam-to-road angle, target vehicles, speed range, interface, controller type, output and display logic, and operating environment. Zilai Technology (Shenzhen) Co., Ltd. can provide model recommendations, datasheets, communication protocols, samples, integration guidance, and project quotations.

Contact lanbing@zlyradar.com or visit https://www.zlyradar.com/.