What is RTK real-time display? 5 practical uses on site

RTK "real-time display" refers to an operation in which, while moving on site, you can immediately confirm on the screen where you (or a machine/vehicle) are and at what height, aiming for centimeter-level accuracy (half-inch accuracy). The value is not merely that coordinates update, but that by watching the correction reception status and the solution state you can judge "Is this position trustworthy?" and "Can I record this now?".

What practitioners searching for "real-time display RTK" want is less a definition of the term and more the mindset and procedures to use it confidently on site, plus how to avoid common mistakes. This article therefore first explains the mechanism that makes RTK real-time display possible, then organizes five practical on-site uses, and summarizes configuration, operation, troubleshooting, and recurrence prevention as a single workflow.

Contents

• Background: why RTK real-time display is needed

• What does RTK real-time display "look at"?

• Quality indicators for on-site judgment

• Five practical on-site uses

• Procedures for fail-safe configuration and operation

• Troubleshooting and how to read logs when things go wrong

• Thinking about recurrence prevention and the LRTK option

Background: why RTK real-time display is needed

RTK is organized as a method to efficiently perform centimeter-level accuracy (half-inch accuracy) positioning in real time by combining satellite observations collected on site with correction information generated from reference-station observations. It is precisely because of this premise of "accuracy available in real time" that you can use what you see on the display to immediately guide the next work decision.

Real-time display is most valuable on site in processes where you "act immediately on measured results" rather than in the act of measuring itself. For example, stakeout, quick checks of as-built conformity, guiding heavy equipment, and immediate sharing of inspection results tend to create rework and slow the site tempo if coordinates are finalized only in post-processing. If you regard RTK real-time display as a tool to move decision-making forward and improve quality without stopping work, it becomes easier to design operations.

Also, with network RTK, users do not need to set up a base station on site. The less preparation required—base station installation, fixing known points, power supply, and securing communications—the easier it is to use real-time display as an everyday tool. This is why high-precision positioning, which used to be the preserve of specialized tasks, has spread into construction management and inspections.

What does RTK real-time display "look at"?

Coordinates shown by real-time display on the screen are not the results of standalone positioning but the result of canceling and correcting error factors using differences between the reference station and rover (or a network model). Explanations of network RTK describe using observation data from multiple continuous operating reference stations and the like to estimate errors around the rover (ionosphere/troposphere delays, satellite orbit errors, etc.) and generate correction information. In other words, the displayed coordinates depend not only on satellite reception but also on the correction model assumptions and communication status.

Typical network RTK methods are organized as virtual reference station (VRS) and surface correction parameter approaches. The former transmits the rover’s approximate position, calculates the data that would be observed at virtual points around it, and returns corrections accordingly. The latter generates a state-space model from a group of reference stations and computes corrections for the rover’s vicinity from that model. To stabilize real-time display it is more practical to understand that "the network side has certain assumptions to estimate errors around the rover" than to memorize the differences between methods.

As for delivery of correction information, protocols for streaming GNSS data over the Internet are well established, and because they use TCP/IP, streaming is possible over mobile IP networks. The streaming premise means that when you feel the display "freezes" or accuracy "suddenly drops" on site, the cause can be the communication path rather than the satellite environment.

Furthermore, standards for differential GNSS and RTK correction formats have been internationally developed; keeping this in mind prevents your thinking from diverging when devices or software change. The standards group of entity["organization","RTCM","dgnss standards body"] and the history of messages added for RTK corrections are closely related to differential data interoperability. Even if real-time display looks like an app on the surface, standardized data and protocols support it behind the scenes.

Quality indicators for on-site judgment

The key to making real-time display a "useful tool" is to translate indicators that judge coordinate trustworthiness into on-site language, rather than focusing on the coordinates themselves. In RTK, the ability to fix carrier-phase integer ambiguities to integers is the key to high precision. The general explanation shows that the process is to first estimate a float solution, then search integer candidates, and finally fix integer values to correct the carrier phase and compute relative position. On-site displays such as "FIX" and "FLOAT" concisely represent these solution stages; understanding this reduces misreading of the display.

Next is satellite geometry. GNSS positioning errors are strongly influenced not only by observation precision but also by the geometric arrangement of satellites as seen from the receiver; DOP is the concept used to express this. Poor DOP magnifies the same observation noise into larger position errors and thus makes it harder to get into FIX or to maintain FIX. In real-time display, looking at DOP lets you decide to "wait rather than measure now" or "move half a step" to improve geometry.

What is often overlooked on site is multipath and signal blockage. Research has shown that when satellite signals are blocked by buildings in urban street environments or contaminated by reflected/diffracted undesired signals, GNSS positioning degrades; multipath is a representative cause. When the real-time display shows "points wandering" or "sudden jumps in height," suspect degradation in the received signal quality before assuming corrections are at fault.

Since correction information is delivered via network, latency and freshness of corrections are also important. Differential augmentation is more effective when the reference station and user are close and the corrections have little time lag, as discussed in research and standards. For on-site operation, assume that in areas with unstable communications you can see a state where "the display is updating but the corrections are old."

Height requires additional caution. GNSS directly provides ellipsoidal height, and converting to practical orthometric height requires subtracting a geoid model and a datum correction, as explained in materials from entity["organization","国土地理院","geospatial info authority japan"]. Also note that changing the geoid model can produce differences in orthometric heights of up to several tens of centimeters (several tens of inches). If heights shown in real time do not match, suspect coordinate system and height system settings first rather than only the receiver state.

Public operational standards can also aid judgment. In the context of public surveying using network RTK, standards specify conditions for known-point accuracy, performing height transformations for height consistency, and acquiring a certain number of epochs continuously after obtaining a fixed solution. Real-time display on site is attractive for its speed, but to make measurements valid as records or checks you should have a rule to "verify the display state before recording."

Five practical on-site uses

From here, five practical ways to turn real-time display into something useful on site are summarized. All share the important point of narrowing the information shown on the screen and predefining decision criteria so that seeing the display immediately changes actions.

The first use is stakeout and guidance. Not only point stakeout but seeing in real time "which side and by how much you are off" near alignments or boundaries shortens the time the surveyor spends making decisions. Especially when walking toward a target point and adjusting the last tens of centimeters (tens of inches), real-time display fits the workflow better than methods that assume post-processing. It is important here to confirm that the display is in FIX, DOP is not degrading, and corrections are not interrupted before declaring the position "final."

The second use is quick as-built checks. In as-built management, the value is being able to judge on the spot whether the current positioning status meets required tolerances. With real-time display you can check coordinates and height and re-measure the same location multiple times in a short period to see whether results are stable and the environment is acceptable. Public surveying operations recommend obtaining a fixed solution and then acquiring a certain number of consecutive epochs; the idea is to connect real-time display to a quality control mechanism rather than just "looking" at it.

The third use is monitoring progress for filling or excavation. Real-time display connects current heights directly to site decisions of whether a location is higher or lower than the plan, more effectively than collecting points for later coordinate computation. Network RTK is shown as a method to "efficiently perform centimeter-level (half-inch) surveying in real time," and this brings meaningful process shortening. On site, because shaky results slow decisions, in places with poor satellite conditions it is effective to move the measuring position slightly or wait briefly for FIX to stabilize.

The fourth use is machine and vehicle operational support. Government materials show examples of GNSS receivers mounted on construction machinery using network RTK for information-driven construction. The real-time display value extends beyond knowing "where the machine is now" to managing work zones, detecting encroachment into danger areas, and sharing positions among personnel—benefitting safety and quality. When mounting on machinery, antenna placement, blockage, and proximity to reflecting surfaces directly affect positioning quality, so adjusting the installation environment while watching quality indicators is a prerequisite.

The fifth use is on-site decision-making for inspection and maintenance. For equipment and structure inspections, knowing "what was inspected," "where photos were taken," and "where an anomaly was confirmed" matters later. If real-time display lets you adjust the granularity of records on site by viewing position and height, post-work organization becomes easier. GNSS and RTK are used across surveying, geodesy, and infrastructure management because location information becomes a common language; stable on-site display increases the trustworthiness of records.

Procedures for fail-safe configuration and operation

To establish real-time display on site, it is more effective to design a "verification order" organized by common failure modes than to list settings from the equipment manual. Below is a generalized procedure not dependent on specific equipment names.

First decide coordinate references. Agree within the project on which horizontal datum to use, whether height is ellipsoidal or orthometric, and if orthometric, which geoid model and datum correction to use. Government materials explain converting ellipsoidal height to orthometric height by subtracting geoid height and datum correction. Because changing the geoid model can shift orthometric heights by up to several tens of centimeters (several tens of inches), do not proceed with ambiguous height settings when using real-time display heights for work.

Next stabilize the correction reception path. NTRIP specifications state that TCP/IP allows streaming over mobile IP networks, but conversely poor communication quality causes corrections to drop or be delayed. On site, identify locations prone to unstable communications and operate under the premise that "the display moving" and "corrections being fresh" are separate states.

Third is antenna height and mounting conditions. Before distance or area calculations, if there is a discrepancy between the input antenna height and the actual measured height, results will be consistently biased. Public surveying observation logs specify that antenna height should be recorded as the vertical height. On-site, standardize how to take the antenna center position, how to measure from the pole tip, and how to handle leaning; eliminate "about this much" within the team.

Fourth is daily checks using known points. Public surveying operation criteria specify accuracy conditions and consistency assurance for known points. For field operations, a practical flow is to check real-time display on a known point in the morning and confirm that horizontal and vertical positions are within tolerances, FIX is stable, and satellite count and DOP are not extremely poor before starting main work. This alone detects many "unexplained offsets" early.

Fifth is to standardize observation procedures. Public surveying operations recommend acquiring a certain number of consecutive epochs after obtaining a fixed solution. This is not merely about strictness but about suppressing real-time display fluctuations operationally and ensuring reproducibility. In practice, tailor rules to the task: for recordings, only acquire when FIX has been continuous; re-measure the same point after some time and check that differences are within tolerance.

Troubleshooting and how to read logs when things go wrong

Chasing real-time display issues by feel wastes recovery time. The basic isolation approach is to divide the problem into five systems—communication, satellite environment, correction model, coordinate settings, and observation procedure—and use logs to determine where the breakdown occurs.

Typical communication issues are interruption, delay, or repeated reconnection of the correction stream. NTRIP allows TCP/IP streaming over mobile networks, but on site signal strength, congestion, and blockages in cut areas can vary quality. Because coordinates may continue updating on the display, always check items that indicate correction reception state and correction data freshness to detect "real-time display without corrections."

Typical satellite environment problems are inability to get FIX, quick reversion to FLOAT after entering FIX, or periodic jumps in coordinates. DOP changes with satellite geometry and affects positioning errors; this background helps understand these phenomena. On site, the most efficient countermeasures are to move to a location with a clear sky view, increase distance from reflective surfaces (glass, metal, water), or raise the antenna.

When multipath or blockage is suspected, do not stop at "the location is bad"—identify which directions are blocked to see room for improvement. Research suggests methods such as elevation masks derived from obstruction distribution in urban environments, 3D map-based masks, and observation data quality checks. You do not need to implement the same algorithms on site, but deciding antenna placement with blockage directions in mind and measuring a bit away from nearby metal structures are practical measures.

Problems with the correction model are troublesome because they resemble satellite-environment issues visually. Network RTK estimates errors from multiple reference stations and behavior can vary with provider method or settings. Practical on-site responses include checking whether the issue reproduces at a different time, whether known-point consistency holds, and whether the same conditions can be replicated where communications are stable.

Coordinate setting issues often manifest as height mismatches despite horizontal agreement, or a uniform offset in a particular direction. Heights in particular require converting ellipsoidal height to orthometric height by subtracting geoid height and datum correction, and different geoid models can cause differences on the order of several tens of centimeters (several tens of inches). If the solution is stable in logs but height is wrong, first check geoid model and datum correction settings, then known-point height epochs and revision statuses.

Finally, how to read logs. At minimum, save the work date/time, solution state, satellite count, DOP, correction reception state, observation interval (epochs), antenna height, and coordinate/height system settings in a form that can be reviewed later on site. Public surveying operation criteria reference the concept of epochs and acquiring continuous epochs after obtaining FIX, so aligning log design with these ideas makes field-office communication clearer. With consistent logs, you can reproducibly separate whether a problem is due to "site environment," "settings," or "operation."

Thinking about recurrence prevention and the LRTK option

The most effective recurrence prevention is to make real-time display produce the same judgment for anyone who looks at it. Concretely, fix which quality indicators should be shown on site, verbalize acceptable conditions for acquisition, set known-point check procedures and tolerances, and standardize log fields. Public surveying operation criteria include known-point conditions, height transformation concepts, FIX confirmation and continuous epoch acquisition—elements that increase reproducibility. Simplify these to fit your company’s purposes and incorporate them into daily procedures.

Also, revisions to geodetic products and geoid models directly affect real-time display heights and must be incorporated into operations. National guidance explains subtracting geoid height and datum correction from ellipsoidal height and using provided integrated files or calculation services. Field teams should check whether their software can handle new models and plan how to compute heights if not; reviewing this at annual updates is prudent.

Even with the above operations in place, many sites will still feel that they want something easier while retaining necessary decision indicators. One option is LRTK, a high-precision positioning device designed to attach to a smartphone. With real-time display on the phone screen, workers can confirm solution state and reception while recording, reducing the need to swap dedicated devices or transcribe, and keeping logs more self-contained on site. If you want to make real-time display a standard field task, consider LRTK as a way to reduce equipment footprint and operation variance so you can more easily evaluate implementation benefits.