top of page

A common request when people want to operate RTK in "real-time display" is not so much about equipment selection as about the need to "make decisions on-site while looking at numerical values." They want to check as-built conformity on the spot, continue staking out piles or boundaries without stopping, or record while walking an inspection route. For these purposes, the ability to judge from the positioning status currently shown on the screen directly improves productivity more than fixing coordinates by post-processing.


However, real-time display of RTK is not established simply by creating a screen where coordinates are updated. In materials from entity["organization","Geospatial Information Authority of Japan","geospatial info authority japan"], network RTK is organized as a method that combines satellite data acquired on-site with correction information generated from observation data of nearby continuously operating reference stations to efficiently perform centimeter-level surveying in real time. In other words, display quality depends not only on satellite reception but also strongly on the reception path of correction information, settings (coordinate system and height system), observation procedures, and the field environment (遮へい・反射: obstructions and reflections).


This article assumes practitioners searching for "real-time display RTK" and organizes seven points to grasp before introduction. It does not depend on any specific manufacturer or service name but summarizes decision criteria usable on any site and an approach to introduction that avoids failures.


Table of Contents

• What real-time display RTK is

• Seven things to know before introduction

• Basic settings and on-site flow for real-time display

• Common failures and how to distinguish troubles

• Inspections and log operations to ensure quality

• Bringing real-time display into everyday sites with LRTK


What real-time display RTK is

RTK is explained as performing relative positioning using observations from a base station and a rover, and when the integer ambiguity of carrier-phase can be resolved, centimeter-level accuracy can be achieved. The ambiguity is first estimated as a float solution, an optimal integer set is searched and fixed, and observations are corrected with that integer to determine the relative position. The status indicators often seen on site screens, "FIX" and "FLOAT," can be understood as quality flags that succinctly indicate whether this integerization has been achieved; doing so greatly reduces misinterpretation of real-time displays.


The value of real-time display lies not in the numerical coordinates themselves but in enabling earlier operational decision-making. Network RTK is introduced as a form that can be used without installing a base station on site, and the lighter the preparation, the easier it is to incorporate real-time display into everyday tasks. On the other hand, network RTK operation manuals note that short observation times can lead to degradation in accuracy due to satellite switching and multipath, and recommend inspecting with multiple observation sets at different times. In practice, it is important to recognize that "the display is moving" and "the recorded quality is acceptable" are not the same.


Also, as a mechanism to receive correction information on site, NTRIP is described as the HTTP-based protocol standard for streaming GNSS data and differential correction data over the internet. While convenient, this means communication quality and latency can affect the continuity of real-time display. To stably operate RTK in real-time display, you must include communication as a quality management target in addition to satellites.


Seven things to know before introduction

Here we organize seven items to check before introduction that will help you avoid getting stuck on site, presented in the order directly relevant to practical decisions. The key is that none of these stand alone; they interact to determine how the real-time display appears.


The first is to decide upfront the purpose of the real-time display and the allowable error range on site. The required rigor differs depending on whether the goal is staking/guidance or recording as-built measurements and inspections. With RTK, quality changes between FIX and FLOAT, and the general approach is to aim for high precision assuming a fixed solution. Therefore, before introduction decide operational criteria such as whether records will be made only when a fixed solution persists for a certain time, and for guidance use, how to handle the moment a fixed solution is lost. Network RTK manuals also present the idea of inspecting with the premise that short observations may degrade accuracy, so creating criteria tailored to the purpose is essential.


The second is to consider how correction information will be obtained and alternative routes when communication is unstable on site. Network RTK is introduced as a method that uses correction information created from observations of nearby continuously operating reference stations and can be used without placing a base station at the site. NTRIP, often used for delivering such corrections, is defined as an HTTP-based standard for GNSS streaming. For on-site introduction, decide within construction or inspection plans whether the area has coverage, where weak-signal sections exist, and where to return if reconnection is needed; doing so reduces failures. Operation manuals also state the need to pre-survey whether the area is within mobile phone service coverage.


The third is to unify coordinate and height systems and avoid mixing them on site. Height causes the most confusion on site; the basic relation that ellipsoidal height obtained from satellite positioning minus geoid height yields orthometric height (elevation) is presented in national guidance. Additionally, when elevation products are revised, the procedure of subtracting geoid height and reference surface correction amount from ellipsoidal height is described, with a caution to verify that software can read the updated data before use. If handling heights in real-time display, fix in the project what height is being shown and which model is used for conversion, and operate assuming revisions/updates may occur. Without this alignment, positioning may be stable yet heights disagree, prolonging trouble.


The fourth is to understand the site’s satellite environment in advance and incorporate difficult locations and times. GNSS errors can be amplified by satellite geometry, explained by DOP. This means that even with identical receiver performance, results vary if the "view of the sky" differs. In places prone to obstructions and reflections—inside forests, near buildings, close to slopes, or in shadows of temporary structures—fixed solutions may not be maintained, or outliers may occur even when fixed. National committee materials also record discussions that large discrepancies can occur near urban areas even with fixed solutions and that multipath effects can appear in partial forms, so consideration is needed. Before introduction, grasp at representative points on site which directions are blocked and which times are unfavorable so you can appropriately use real-time display.


The fifth is to finalize equipment configuration and mounting conditions from the perspective of real-time display. Real-time display tends to encourage operations that look only at "coordinates on the screen," but in practice physical conditions such as antenna height, pole verticality, mounting position obstructions, and power stability manifest as display jitter. Operation manuals note that short observations can degrade accuracy due to satellite switching and multipath; thus, weak observations are susceptible to environmental influence. Before introduction decide on a balance between portability and setup reproducibility, and standardize how to measure and input antenna height within the team. If this is left vague, a consistent offset may remain even with correct settings, and real-time display will lose credibility.


The sixth is to standardize observation procedures to reduce display fluctuations by operation. Public surveying manuals using network RTK indicate as a single-point observation standard to obtain a FIX solution and then continuously acquire 10 or more epochs of data. Furthermore, anticipating accuracy degradation from short observation times, they recommend comparative inspection with two observation sets at different times or loop closure checks. In practice, for recording, adopt continuous acquisition and averaging as basic, and for critical points institute a rule to take data twice at different times and check differences. Guides in forestry and agriculture also recommend using averages of multiple continuously acquired data and checking satellite configuration displays.


The seventh is to decide in advance the display items required for real-time display and the log items necessary to trace causes. A clear screen is not one with less information but one where the information needed for judgment is visible in the shortest time. At minimum, it is important to know the solution state (whether fixed), correction reception status, satellite geometry quality (DOP, etc.), and which coordinate and height references are being used. DOP is explained as error amplification due to satellite geometry, and the integerization of ambiguities is organized as the key point of RTK. Then, rule what display states warrant recording, re-measurement, or suspending work, and log the meta-information needed for those decisions (number of acquisitions, timestamp, positioning state, correction reception state, height settings, antenna height). Given that short observations may leave multipath effects and other impacts, without logs causes cannot be traced and real-time display will be hard to institutionalize.


Basic settings and on-site flow for real-time display

From here, to make the introduction reproducible by anyone, we organize basic settings and on-site flow as a single sequence. Button names and screen names vary by device and app, so they are not addressed, but the order of checks can be standardized.


First, solidify the reference settings. Align horizontal positions with the adopted geodetic system and match the deliverable format. If dealing with heights, decide whether to use ellipsoidal height as-is or to use orthometric height (elevation). If using elevation, the basic relation of subtracting geoid height from ellipsoidal height is shown, and after elevation product revisions the procedure including subtracting the reference surface correction amount is described. At introduction, have the team check once at the same point how elevation and ellipsoidal height are displayed to greatly reduce later confusion.


Next, stabilize reception of correction information. Since NTRIP is defined as an HTTP-based standard for GNSS streaming, settings typically center on connection information to the provider, authentication, and selecting the correction stream to receive. What matters on site is not whether you can connect but whether the connection can be maintained. If there are sections prone to unstable communication, build operations such as "initialize in a section where communication is stable before entering" and "perform important recordings at points where communication is stable" into the workflow. Operation manuals also require pre-surveying whether the area is within mobile phone service coverage.


On top of that, always include checks at the start of on-site work. Public surveying manuals for network RTK show examples of accuracy conditions for known points and a standard of acquiring 10 or more continuous epochs after obtaining a FIX. In practice you may simplify this, but at least make a rule to check first thing at a known point whether a FIX is obtained, whether values fall within tolerances, and whether height conversion behaves as expected—and do not start main work if these fail. If problems arise here, they are more likely due to settings or references than the field environment, enabling faster recovery.


During work, switch real-time display between "guidance" and "recording." For guidance, it suffices if the center of the screen shows the current location and the difference to the target; obsessing over fine digits can slow decisions. For recording, the opposite applies: verify FIX maintenance, quality indicators such as DOP, and correction reception status, and use continuous acquisition and averaging to obtain a stable value. Satellite configuration effects are described via DOP, and manuals note that short observations may be affected by satellite switching and multipath. In other words, recording requires a rhythm of "state confirmation → continuous acquisition → confirmation."


Finally, organize and share results. While real-time display speeds decision-making on site, its value diminishes if you cannot explain it later. Therefore, at the end of the work prepare minimal logs so that "that day’s inspection results," "points with anomalies," and "reasons for re-measurement" can be traced. As guidance in forestry and agriculture suggests, materials that touch on satellite reception conditions, satellite configuration displays, and acquisition count settings support reproducibility in practice.


Common failures and how to distinguish troubles

When operating RTK in real-time display, troubles fall into three main systems: communication, satellite environment, and references/settings. Here we organize how to distinguish by symptom in ways that don’t waste time on site.


First, if you suddenly cannot enter a FIX or cannot maintain a FIX. If the cause is communication, the correction stream may be interrupted. Since NTRIP is defined as HTTP-based streaming, communication outages or delays can occur. Design screens to show correction reception status, and if reception is unstable, realistic countermeasures are to return to a location where communication is stable, reconnect, or change the work sequence.


If the FIX loss is due to the satellite environment, DOP degradation, a decrease in satellite count, and simultaneous jumps in position and height are likely. Error amplification by satellite geometry is explained by DOP; given the same observation noise, worse geometry amplifies errors more. In such cases, changing the view of the sky is often faster than changing settings: move a bit away from a building, keep distance from reflective surfaces, avoid slopes and temporary structures, etc. Multipath effects can cause accuracy degradation in short observations, and in urban areas large outliers can occur even with FIX.


Next, if horizontal coordinates agree but only height does not, or height is unstable. This can occur from the satellite environment, but a common cause right after introduction is mixed references. National guidance states that elevation is obtained by subtracting geoid height from ellipsoidal height. After elevation product revisions, the procedure to subtract geoid height and reference surface correction amount is given, and there is a caution to confirm that the software can read new data. When handling heights in real-time display, clearly state the type of height being shown and unify it within the team; otherwise height mismatches will persist.


Also, there are cases where values seem stable under FIX yet later do not match known points. Network RTK manuals assume that short observations may be affected by satellite switching and multipath and recommend comparative inspection with two observation sets at different times. Because real-time display has a brisk tempo, taking a single acquisition and stopping risks capturing an outlier. For critical points institute a rule to take measurements again after some time or under different conditions and compare.


Finally, common operational errors include antenna height input mistakes and mixed recording units. When on-site values are shifted by a constant amount, human setting errors are often the cause rather than corrections or satellites. At introduction always display "antenna height," "type of height," and "acquisition count" on the recording screen and instill the habit of checking them before recording; this prevents most problems. The concept of continuous acquisition and averaging is recommended in guides and is an area where operation can raise quality.


Inspections and log operations to ensure quality

Real-time display advances work rapidly but has the weakness that accountability for work can become vague. To successfully introduce it, create an operation that ensures quality before worrying about technology.


First decide inspection standards. Public surveying manuals for network RTK present concrete operational standards such as accuracy conditions for known points, acquiring 10 or more continuous epochs after obtaining FIX, and comparative inspection using two sets at different times. You do not need to take everything to the field exactly as written, but two items—morning known-point checks and double acquisition for important points—are strongly recommended if using real-time display for records. These allow early discrimination among field environment, communication, and setting issues.


Next design logs. Logs are not only for experts but serve as evidence to explain later “why this value was adopted” on site. At minimum log positioning state (whether FIX), correction reception state, number of acquisitions (averaging conditions), coordinate and height systems, antenna height, and work timestamps. Guides in forestry and agriculture also emphasize elements such as satellite reception status, satellite configuration display confirmation, and acquisition count settings as important for reproducibility.


Further, always incorporate the impact of revisions and updates on heights into operations. National guidance on elevation product revisions describes subtracting geoid height and reference surface correction amount from ellipsoidal height, using integrated files or calculation services, and confirming reading in the software to be used. This means that the site is not necessarily wrong but the reference assumptions may change. Those responsible for introduction should run inspection procedures when annual updates or revisions occur, and if consistency with past data is required set rules for conversion or annotation to preserve long-term trustworthiness of real-time display.


Finally, human operation. Real-time display is often assumed to be "understandable by looking at the screen," but in practice its effectiveness appears only when the judgment criteria of "which states are acceptable for recording" are shared. Take into account that integerization of ambiguities is the RTK core, satellite geometry effects are described by DOP, and short observations may leave multipath effects. Verbalize the judgments and codify rules so that anyone will act the same way.


Bringing real-time display into everyday sites with LRTK

Covering the seven points above establishes the technical and operational foundation to use RTK with real-time display. Even so, adoption may fail on site because switching dedicated devices is cumbersome, work is fragmented between recording and sharing, or inspections and logs are too bothersome to maintain. The value of real-time display depends more on "frequency of use" and "habit formation" than on raw performance.


One option is LRTK, a smartphone-mounted GNSS high-precision positioning device. If you make the real-time display visible on the smartphone screen and link it easily to on-site recording and sharing workflows, the display becomes part of routine procedures rather than a special task. The decision materials needed in real-time display are whether the solution is FIX, whether corrections are being received, whether satellite geometry is deteriorating, and whether height references are consistent. Creating an environment where these decision materials can be checked anytime on site greatly increases introduction success.


Introducing RTK for real-time display does not end with choosing equipment. The essence is to decide in advance the seven items—purpose, corrections and communication, references and heights, satellite environment, equipment and mounting, observation procedures, and screen design and logs—and shape them into operable practices. If you want real-time display to become a form that can always be checked on site or feel the need to reduce the burden of carrying inspections and logs, consider reorganizing real-time display operations including smartphone-mounted devices like LRTK. Doing so helps RTK function not as a tool for specialized tasks but as a tool that supports everyday on-site decision-making.


Next Steps:
Explore LRTK Products & Workflows

LRTK helps professionals capture absolute coordinates, create georeferenced point clouds, and streamline surveying and construction workflows. Explore the products below, or contact us for a demo, pricing, or implementation support.

LRTK supercharges field accuracy and efficiency

​

The LRTK series delivers high-precision GNSS positioning for construction, civil engineering, and surveying, enabling significant reductions in work time and major gains in productivity. It makes it easy to handle everything from design surveys and point-cloud scanning to AR, 3D construction, as-built management, and infrastructure inspection.

bottom of page