What latency or age of corrections does PointPerfect Flex require?

The performance of the PointPerfect Flex service depends on the timely delivery of GNSS correction data to the receiver. Correction latency (also referred to as age of corrections) directly affects convergence behavior, positioning accuracy, and how long an RTK‑class solution can be maintained.

This guidance applies to common questions around correction latency, age of corrections, late SPARTN or RTCM corrections, and network‑related delays when using NTRIP.

When PointPerfect Flex corrections are delivered over IP‑based protocols (i.e. NTRIP), the ideal correction latency is typically between 1 to 5 seconds. Operating within this range helps achieve optimal convergence times and positioning accuracy under normal operating conditions.

The total correction latency observed at the receiver additionally depends on transmission time and data delivery rate. Typical correction age observed at the receiver is:

As correction data becomes older, positioning accuracy gradually degrades. If the correction latency exceeds the receiver’s acceptable limit, the receiver may automatically reduce the positioning mode (i.e., revert from RTK Fixed to 3D/DGNSS) in order to maintain reliable and stable position output. 

A noticeable position shift (typically up to a meter) can occur during this transition. This behavior is expected and is explained in Why does my rover jump by meters when it loses RTK fix

Notes:

• Actual correction latency depends on the data distribution method, network conditions, and receiver setup.
• Performance may vary in challenging environments (for example, poor sky visibility or high ionospheric activity).
• For best results, ensure continuous connectivity, correct antenna installation, and appropriate receiver configuration.