How to Make RTK Real-Time Displays Easier to Read: Six Tips to Avoid Failure

Whether work with RTK becomes "faster" is determined less by the positioning accuracy itself than by whether the operator can make the correct judgment the moment they look at the screen on site. A real-time display is not just a screen where coordinates are updated. It is a decision panel for reading at a glance whether correction data are being received, whether the solution is stable, and whether accuracy is deteriorating due to obstructions, and for deciding whether to record this point now, wait a little, or move to another location. Networked RTK combines correction data generated from nearby reference stations with the site’s satellite data and is organized as a method to efficiently perform cm-level (half-inch-level) surveying in real time.

On the other hand, real-time displays at the site tend to become hard to read. The reason is simple: there is a lot of information needed for judgment. If positioning status, satellite geometry, correction reception status, height reference, recording units and rounding are not aligned, you can end up with a situation where “the display is shown but it can’t be used.” Furthermore, when corrections are streamed over the Internet, communication quality and latency can affect display stability. NTRIP is described as an application-layer protocol for streaming GNSS data and differential corrections over the Internet; it is HTTP-based and uses TCP/IP so it can be delivered over mobile networks.

This article is aimed at practitioners who will search for “real-time display RTK” and summarizes a way of thinking and six fail-safe tips to make your screen easier to read and reduce mistakes, without depending on specific devices or software names. In short, readability is determined not only by fonts and color schemes, but by what you display, what you don’t display, and how the display is linked to actions.

Table of contents

• Typical patterns that make real-time displays hard to read

• Information design and priority of display items that determine readability

• Six tips to make displays easy to use for fail-safe operation

• How to read quality indicators that directly affect on-site decisions

• Troubleshooting and immediate countermeasures when the display breaks

• Inspections and logkeeping to prevent recurrence

• Making real-time displays even more field-oriented with LRTK

Typical patterns that make real-time displays hard to read

The first cause of a hard-to-read real-time display is that the screen is an "everything shown" display. If you cram latitude/longitude, plane rectangular coordinates, height, speed, heading, number of satellites, signal quality, correction reception status, and so on onto one screen, it becomes hard to notice important changes. In RTK, the ability to fix the integer ambiguity of carrier-phase cycles as integers is the key to cm-level accuracy, and when ambiguity cannot be fixed the accuracy tends to degrade. In other words, what the field needs to know first is not “the current numbers” but “whether the current solution can be trusted.”

The second cause is that updates are too fast to read. Real-time RTK displays tend to update at high frequency such as 1-second updates, but if numbers flicker so fast they are hard to read, people pay attention to the fact that things are “moving” rather than to important changes. Moreover, in environments with obstructions and reflections the positioning solution can jump, which in the field is often misunderstood as "broken." There are reports that in urban canyon environments multipath can cause positioning errors, and that creating masks from sky-visibility information can improve results.

The third cause is that map or guidance displays are not suited to the task. What the site needs are relative informations such as “how many meters to the target and which way to move” or “how far off the planned line we are”; if the screen is just a list of absolute coordinates, decision-making will be delayed. If the map scale is too wide or too narrow for the task, or the orientation is rotated so the target is lost, you end up with an unusable display despite it being present.

The fourth cause is mixing height systems and references. Heights obtained by satellite positioning are ellipsoidal heights, and to treat them as orthometric heights you need to convert using a geoid height or similar, as explained by entity["organization","国土地理院","japan mapping agency"]. Because revisions to orthometric height products and updates to geoid models can change conversion results for the same point, a lack of unified height reference on the display can cause situations where “the screen is normal but the values don’t match.”

Finally, an often-overlooked issue is mixing display and recording purposes. Real-time displays can be used for both guidance and surveying, but while guidance can proceed despite some jitter, surveying and as-built records require certain conditions to be met. Operational standards for public surveys, for example, show that acquiring a continuous number of epochs (e.g., at least 10 epochs) after achieving a FIX solution is standard practice, so recording requires its own rules.

Information design and priority of display items that determine readability

When creating a readable real-time display, the first thing to do is not to decorate the screen but to divide on-site decisions into three types. In many field situations guidance, recording, and inspection are mixed. For guidance you want to instantly judge “which way to move now.” For recording you want to judge “is it acceptable to finalize this point.” For inspection you want to judge “are today’s conditions normal.” Because putting all of these into a single screen always fails, it is important to change display priorities by purpose.

Next, divide the minimum information required in a real-time display into main and supporting elements. The main elements are position display and relative guidance. Position can be shown as the current location on a map or as coordinate values, but what directly affects field actions is the “difference from the target.” The supporting elements are the reliability indicators. Since RTK accuracy depends strongly on ambiguity fixing and degrades when ambiguities cannot be fixed, the solution status should not be a marginal digit but a premise for judgment and placed in a constantly visible location.

Among the elements that determine reliability, satellite geometry and the impact of obstructions are especially useful on site. In GNSS, satellite geometry affects positioning error and this effect is described by the DOP concept. In other words, even with the same receiver, poor sky view can amplify errors.

Also include the correction reception status in the display design. As the mechanism of networked correction distribution is described — NTRIP streams GNSS data over HTTP and uses TCP/IP so it can be delivered over mobile networks — it depends on the communication status. Therefore the display must prevent the misinterpretation “coordinates are updating so it’s fine” when communications fail.

Height display is more about preventing accidents than readability. If you handle orthometric height, the conversion procedure shows subtracting geoid height (and if necessary a reference-surface correction) from ellipsoidal height. When heights don’t match on site, suspecting only the receiving status delays recovery. Making it obvious on the display whether you are showing ellipsoidal height or orthometric height contributes to readability.

Six tips to make displays easy to use for fail-safe operation

From here we summarize six tips to make real-time displays easier to read. While they may sound like font and color advice, they actually change both display and operation together. They are organized as concepts applicable to any site, independent of specific devices or apps.

Tip 1: Treat the screen as three modes — “guidance,” “recording,” and “inspection.” For guidance, maps and the difference to the target are top priority. Fine digits of coordinates are not important; what matters is that direction and distance to move are instantly clear. For recording the reverse is true: coordinate values, heights, solution state, and correction reception state are the main elements. For inspection, arrange satellite count, DOP, correction reception stability, and how easily FIX is obtained so they can be checked quickly. Given operational standards such as obtaining continuous epochs after FIX, recording screens should focus on whether conditions are appropriate for recording rather than whether a value was merely captured.

Tip 2: Intentionally standardize number units and digits. Many hard-to-read displays have numbers with too many digits or mixed units. A common confusion on site is whether millimeter-level (0.04 in-level) accuracy is required or whether centimeter-level (half-inch-level) accuracy is sufficient. For example, in guidance you cannot instantly convert between "0.03 m (0.10 ft)" and "3 cm (1.2 in)." Set units and rounding to match the decision being made. In particular, height is prone to accidents when ellipsoidal heights and orthometric heights are mixed, so clearly state which is displayed and, if conversions are performed, standardize the geoid model used on site.

Tip 3: Turn quality indicators from “numbers to read” into “status displays to judge at a glance.” RTK accuracy depends strongly on ambiguity fixing, and when fixing fails accuracy tends to degrade. Therefore the solution status is not a small adjacent numeral but a signal to decide whether to stop or proceed. The same goes for DOP: because satellite geometry can amplify errors, the moment DOP deteriorates you should be able to decide “do not record here” — use thresholds that change text or background color to provide highly visible cues.

Tip 4: Separate “smoothing for display” and “raw data for recording” to reduce display jitter. Large jitter makes people distrust the display; too much smoothing risks missing anomalies. The important point is separating on-screen decision-making from verifiable recorded logs. The concept of construction quality control by entity["organization","国土交通省","ministry of land japan"] explains that continuous acquisition of construction-management data and traceability are important. If you smooth the display for readability, design logging so data remain available for verification. Also, in some observation conditions smoothing FLOAT solutions for input is noted as important; smoothing can be effective if used appropriately.

Tip 5: Fix map display rules to reduce eye movement. Field real-time displays are hard to read because the eye wanders. Decide per task whether to fix a center cross and move yourself, or move the current-location icon, whether to keep the map orientation fixed, etc. For example, when walking along a boundary or alignment for inspection, a fixed orientation is less confusing; in a confined yard a display with travel direction at the top may be more intuitive. The important thing is to standardize display rules within the field team so everyone interprets the screen the same way.

Tip 6: Design alerts and recovery procedures as part of the display. Readability is judged not only in normal conditions but by how clear things are in abnormal conditions. When correction is lost, DOP worsens, satellite count drops, or FIX is lost, small notices on the screen are not enough for field crews to notice. Since NTRIP delivers corrections via streaming, assume communication failures and latency can occur, and make abnormal-status messages instantly noticeable. Also define "what to do to recover" as standard field procedures and include them as checklist items on the inspection screen. Operational practices such as acquiring continuous epochs after FIX are useful examples of standardizing abnormal-condition judgments.

How to read quality indicators that directly affect on-site decisions

Even if the real-time display is made easy to read, judgments will vary unless the meanings of quality indicators are internalized. Here we summarize key points to make on-site indicators not just “readable” but “actionable.”

First is solution status. In RTK the integer ambiguity of carrier-phase cycles is the issue; if fixed, cm-level (half-inch-level) accuracy is attainable, and if not fixed accuracy tends to degrade. On site, treat this difference like a “permit.” For example, for recording do not finalize unless a fixed solution is stable; for guidance, defer decisions in places where a fixed solution cannot be maintained.

Next is DOP. GNSS positioning error is affected by satellite geometry and is described by DOP. In times or places with poor DOP, errors can be amplified even with the same receiver conditions. In practice, tie DOP thresholds to actions: if DOP worsens beyond a set value, choose one of “do not record,” “wait a bit,” or “move half a step.” Don’t just watch DOP — convert it into an operational rule; this is as important as readability.

Obstructions and multipath are also directly linked to display interpretation. In urban obstruction environments, there are reports that multipath mitigation can improve Fix rates, and that poor sky visibility leads to unstable positioning. When the real-time display shows “position jumping” or “height changing suddenly,” first suspect sky visibility and reflections rather than communications or settings. A readable display is one that quickly causes you to suspect environmental degradation.

Correction reception is a major pitfall of real-time displays. NTRIP is described as streaming GNSS data over HTTP and thus can be delivered over mobile networks; this means corrections are not guaranteed. On site you should monitor not just whether coordinate updates continue but whether corrections are being received freshly. If corrections stop, the display may continue but expected accuracy may not be maintained, so place correction status prominently on the screen.

For height, understanding the structure of ellipsoidal height and orthometric height quickly resolves display issues. Orthometric height relates to the geoid, and orthometric height is obtained by subtracting geoid height from ellipsoidal height. Revisions of orthometric height products specify subtracting geoid height and any reference-surface correction from ellipsoidal height. When on-site heights do not match, the quickest check is not the receiver environment but “which height is being displayed” and “are conversion settings consistent.”

Troubleshooting and immediate countermeasures when the display breaks

When the real-time display suddenly becomes hard to read on site, the causes fall into three major categories: communication path, satellite environment, and settings or reference mismatches. Here we organize a practical approach to isolate causes from screen symptoms.

Check communications first. Since corrections are delivered over a network, communication outages or latency can directly cause display instability. Because NTRIP is described as HTTP-based streaming, prioritize checking whether the correction stream is alive. If on-screen correction reception status is unclear, the display itself is the problem. If communications are suspect, try relocating, switching networks, or reconnecting first; you may resolve the issue before getting into satellite-environment discussions.

Next check satellite environment. DOP explains error amplification due to satellite geometry, and in urban obstruction environments multipath can dominate positioning errors. If DOP is worsening, satellite count is decreasing, or jumps are increasing simultaneously, moving to a different location is faster than tweaking the display. Small actions—move to a position with slightly more sky, increase distance from reflecting surfaces, or rotate your body or pole to reduce obstructions—can be effective.

The third cause is settings or reference mismatches. Typical symptoms are “horizontal fits but height does not” or “everything is offset by a constant amount.” Height handling procedures specify subtracting geoid height (and reference-surface correction if needed) from ellipsoidal height, and different models affect appearance. If only height is off on site, first suspect height system and conversion settings rather than corrections or satellites. Also, antenna-height entry errors won’t be fixed by making the display prettier. Require antenna height and reference checks on the inspection screen before recording to reduce recurrence.

A tip to speed isolation is to view screen symptoms as combinations rather than single occurrences. For example, if correction reception and satellite count are normal but FIX is hard to obtain, the cause is more likely reflections or observation quality than obstruction. In multipath environments, sequential-solution elimination can be difficult, and thresholds or algorithm adjustments may be needed; this requires balancing convenience and reliability. Accepting that behavior changes with environment, design displays and rules so that when conditions are poor the operator can choose not to force a recording.

Inspections and logkeeping to prevent recurrence

Making real-time displays easy to read is not complete the moment the screen is improved. To institutionalize it at the site, inspections and logs must be put into a system so anyone makes the same decisions. Here we present ideas that work with minimal operation.

First, daily inspections. Public survey manuals specify known-point accuracy conditions, height consistency procedures, and operations such as acquiring at least 10 continuous epochs after a FIX. On site, either apply these directly or simplify them to suit your purpose; create a morning inspection flow to confirm the display is correct before starting work. The more readable the real-time display, the easier it is to reflect inspection results in field decisions.

Next, logs. Logs may sound like expert material, but in practice they are like notes to help recall causes later. At minimum record the work date, location, reference used, progression of solution status, correction reception state, trends in satellite count and DOP, height handling, and antenna-height settings. The concept of construction quality control expects traceability through acquisition of construction-management data, so keeping logs is directly tied to quality and accountability.

Preventing height-related recurrence includes tracking revisions. Revisions to orthometric height products specify subtracting geoid height and any reference-surface correction from ellipsoidal height, and setting epochs for orthometric-height products enables monitoring temporal changes. On site, fix the geoid model and reference-surface correction handling as a “project specification,” and run inspection procedures when annual updates or revisions occur. Ultimately whether the real-time display is easy to read depends on whether such reference management is in place.

Finally, education. A readable screen is a tool to externalize the judgment criteria in the veteran’s head. When new personnel join, verbalize and share where to look on the screen and which states mean “record” or “defer.” As noted, the balance between convenience and reliability can change with the positioning purpose; field rules are not set-and-forget. Collect performance from inspections and logs and maintain a process to update rules — that is how readability is maintained long term.

Making real-time displays even more field-oriented with LRTK

If you apply the six tips above, real-time displays will become much easier to read. Still, in the field you may face operational barriers such as “it’s a pain to bring out a dedicated terminal,” “recording and sharing are separate tasks,” or “the display is readable but carrying it is a burden.” Readability is determined not only by screen design but by how often you can pull the device out and use it.

Consider a GNSS high-precision positioning device that attaches to a smartphone — LRTK. With real-time displays on a smartphone screen that can directly link to on-site recording and sharing workflows, the display becomes not just something you “look at” but part of a standard operating procedure. LRTK is presented as a high-precision positioning device used in combination with a smartphone, intended for field use.

The goal of making real-time displays easier to read is not a prettier screen but faster decisions, more accurate records, and quicker recovery from problems. If you can make real-time displays a routine on a portable configuration like LRTK, inspections, guidance, recording, and sharing become seamless, and display design improvements translate directly into field productivity. If you want real-time displays to become a field standard rather than a specialized task, consider the display tips together with smartphone-attached options like LRTK.