How to Read Elevations in RTK Surveying: 6 Basic Points on Ellipsoidal Height and Geoid Height

RTK surveying newcomers in practical roles often first stumble over how to read elevations. While planimetric positions are easy to understand, heights introduce similar-sounding terms such as ellipsoidal height, geoid height, and elevation corrections, and it’s common to be unsure whether the value on-screen can be trusted as-is. Especially on construction, civil engineering, and surveying sites, operating with an unclear understanding of height can lead to unexpected rework when checking as-built conditions, setting out, or comparing with design. This article organizes the concept of height in RTK surveying from a practical perspective and clearly explains, in six basic points, the difference between ellipsoidal height and geoid height and the fundamentals for handling elevations correctly.

Contents

• Why understanding elevation matters in RTK surveying

• First thing to grasp: ellipsoidal height and elevation are not the same

• What is geoid height: the key to understanding RTK height displays

• Six basic points on reading elevations in RTK surveying that commonly cause confusion

• Common elevation troubles on site and their causes

• Checklist for using RTK elevations in practice

• Points to note when handling elevations in public surveys and construction management

• Summary

Why understanding elevation matters in RTK surveying

RTK surveying is a convenient method that allows immediate acquisition of high-precision position information on site. It is used for many purposes such as planimetric checks, stakeout, as-built management, setting out, and checking existing conditions. At the same time, many people report that heights are harder to understand than planimetric positions.

The reason is that height is not defined by a single reference. The height commonly called “elevation” in the field and the height that GNSS treats as its computational reference are fundamentally different concepts. RTK receivers and positioning apps display a height on their screens, but if you don’t correctly understand whether that number is an ellipsoidal height, an elevation, or a geoid-corrected value, it can differ from design drawings or known points by tens of centimeters.

This discrepancy is not caused only by equipment failure. It is more often due to misunderstanding the meaning of the displayed value. For example, it is not uncommon at sites for teams to repeatedly remeasure while suspecting reception or communication problems, when in fact they had mistaken an ellipsoidal height for an elevation. If you mix up the height references, it’s natural that repeated measurements will not agree.

On construction sites, differences of a few centimeters can affect construction quality and inspection results. Processes that involve height—such as slopes, earthworks, drainage gradients, finished floor or foundation top levels, paving, and buried utilities management—require particular attention. Understanding RTK heights correctly is crucial not only for surveying companies but also for construction managers, site supervisors, and infrastructure maintenance staff, because it affects daily work accuracy and efficiency.

In short, when working with heights in RTK surveying, merely reading the number is insufficient. It is important to know which reference that number is based on and how it relates to the height needed on site. Grasping this point alone changes how you read screens and greatly reduces indecision in field judgments.

First thing to grasp: ellipsoidal height and elevation are not the same

The first thing to understand about heights in RTK surveying is that ellipsoidal height and elevation are not the same. Confusing these will make all subsequent corrections and checks ambiguous.

Ellipsoidal height is the height from a reference surface that approximates the Earth as a smooth rotational ellipsoid. GNSS calculates position using signals from satellites, and the ellipsoid is the basis for those calculations. In other words, GNSS directly derives ellipsoidal height most readily, and that is the height the receiver initially handles internally.

On the other hand, the elevation commonly used on site is closer to the concept of height referenced to mean sea level. The heights we see in road ledgers, design drawings, control point results, and as-built management are in many cases based on this notion. When practitioners ask “what is the height at this point,” most are assuming elevation rather than ellipsoidal height.

The problem is that both look like “height,” so it’s easy to treat them interchangeably. When height is shown on an RTK screen, you may take it as elevation without checking. But the meaning of that displayed value changes depending on display settings, the reference being used, and whether any correction information is applied.

The difference between ellipsoidal height and elevation varies by location; it is not a constant value. Therefore, a correction amount that worked well on one site cannot necessarily be used unchanged on another. This variability makes height handling more difficult.

Also, even when RTK gives good planimetric accuracy, height can be more sensitive to conditions. Satellite geometry, obstructions, multipath, fixed-solution stability, and the state of correction information all affect height values. So after understanding the ellipsoidal-versus-elevation difference, you also need to check positioning quality.

A practical way to think about it is that GNSS initially provides ellipsoidal height, and an additional concept is needed to translate that into the elevation used on site. The important concept for that translation is geoid height, which is explained next.

What is geoid height: the key to understanding RTK height displays

Geoid height is an indispensable concept for understanding heights in RTK surveying. Since it bridges ellipsoidal height and elevation, understanding it quickly clarifies how to read heights.

The geoid is a reference surface that, considering gravity, has properties close to mean sea level. The Earth is neither a perfect sphere nor a perfect rotational ellipsoid, and gravity varies slightly by location due to uneven mass distribution and topography. As a result, a surface extended from mean sea level does not match the simple ellipsoid. The separation between the ellipsoid and the geoid is called geoid height.

In practice, ellipsoidal height minus geoid height is often used to obtain a height close to elevation. Exact handling depends on the geodetic system and operational conditions, but as a basic concept to grasp on site, this relationship is very useful.

This concept matters because the height obtained by RTK equipment from GNSS and the heights used in design or control points will differ if compared as-is. If you compare numbers without considering geoid height, you will see an unexpected offset. But this is not an anomaly—it may simply be a difference in reference surfaces.

Note that geoid height itself also varies by location. In other words, the correction amount is not uniform nationwide. It can change even within a single prefecture, and on large or elongated sites treating it as a simple constant may be inappropriate. Locally, adjustments can be absorbed by matching to known points, but if you force numbers to match without understanding the true meaning, errors may become evident at other points.

Also, depending on receiver or app settings, some devices already display elevations that consider the geoid, while others show ellipsoidal height as-is. If site personnel do not know what the numbers on their display represent, results can appear inconsistent when different devices are used on the same site.

Although geoid height may seem theoretically difficult, the practical point is simply to understand that there is a correction between the height GNSS directly indicates and the elevation desired on site. You do not need to memorize complex formulas. What matters is always being aware of which reference the height you are looking at is based on.

Six basic points on reading elevations in RTK surveying that commonly cause confusion

To handle heights correctly in RTK surveying, the quickest route is to organize and understand the key points one by one. Here are six items that commonly cause confusion in the field.

• Confirm what the on-screen height actually represents. A label of “height” alone is insufficient. You need to check whether it is ellipsoidal height, geoid-corrected elevation, or a value transformed into a local coordinate system. Overlooking this will destabilize subsequent calculations and comparisons.

• Always compare with known points. Even if settings are theoretically correct, operational omissions or differences in correction conditions can occur. Comparing numbers at a known point lets you detect reference differences immediately. Sites that habitually perform a known-point check at the start of work tend to experience fewer height-related problems.

• Do not trust height with the same confidence as planimetric accuracy. RTK can have stricter requirements for vertical accuracy and stability. Satellite visibility and local environment affect height more readily, so a fixed solution does not guarantee complete vertical reliability. Basic actions—waiting until values settle, taking multiple observations, and inspecting surrounding obstructions—are important.

• Distinguish whether you need absolute height or relative height on site. For example, when comparing the top level of a structure with a design value, absolute height agreement is important. On the other hand, if the main task is checking height differences within the same site, relative stability may be the practical priority. If you do not recognize this difference, you may be unduly troubled by mismatches.

• Do not treat elevation corrections as ad hoc fixes. It is common to apply a correction based on the difference observed at a known point, but using such a correction without understanding what it represents is risky. The correction may be compensating for the ellipsoidal-versus-elevation gap, aligning to a local reference, or simply correcting a configuration error; the implications differ. If you merely note a correction value and reuse it, reproducibility can be lost on other sites or different days.

• Confirm in advance the height reference required for deliverables. Internal sharing, construction management, client submissions, as-built records, and control surveys may each require different handling of heights. Even if the surveying team manages data based on ellipsoidal height, the recipient may expect elevations. If terminology is not unified on site, the same word “height” can refer to different numbers.

Keeping these six points in mind greatly reduces confusion about heights in RTK surveying. In short, height is not a single number but the result of overlapping references, corrections, and operational purposes. Before reading a display value, it is important to check what rules produced that number.

Common elevation troubles on site and their causes

On RTK surveying sites, elevation-related troubles often occur in subtle ways. Because planimetric positions may appear correct, when problems are limited to height it can take time to identify the cause. Here we summarize common troubles and their background.

A representative issue is numbers not matching known points. One of the most common causes is confusing ellipsoidal height and elevation. If the receiver displays ellipsoidal height while you compare it directly against a known point’s elevation result, a discrepancy will certainly occur. If you then focus only on communication or satellite counts, you may miss the true cause.

Another frequent case is different heights displayed on different devices. Even when observing the same location, different equipment or settings can yield inconsistent heights. While differences in positioning quality can be a factor, often the cause is display reference differences or how the geoid model is handled. If multiple people work on the same site, unified settings are essential.

There are also cases where heights match at some parts of the site but discrepancies appear at distant points. This often happens when a correction determined from a single point is applied unchanged across a wide area. While localized agreement is possible, ignoring spatial variation can cause larger differences elsewhere. This is especially risky on long, linear sites or sites with significant elevation changes.

Some teams experience unstable heights despite having a fixed solution. Obtaining a fixed solution is important in RTK, but it does not fully guarantee vertical quality. Reflections or obstructions from nearby buildings, trees, slopes, vehicles, or overhead lines can cause slight fluctuations. In cases that require strict vertical control, observing the value over several seconds to more than ten seconds and confirming stability is effective.

On construction sites the issue may surface as differences from design levels that seem larger than expected. In such cases, the design data reference, the site’s local reference, or the device’s display reference may not match. When multiple parties prepare data at different times, checking the height reference is often overlooked.

These troubles are often caused not just by mechanical measurement errors but by differences in definitions and insufficient setting checks. In resolving height troubles, before suspecting positioning quality, first confirm whether the numbers you are comparing are based on the same reference.

Checklist for using RTK elevations in practice

To use RTK elevations practically on site, standardizing a confirmation procedure is important as well as understanding the theory. Following the same flow each time reduces human error and makes troubleshooting easier.

First, confirm which type of height the equipment or app will display that day. Check settings and operational records to determine whether it shows ellipsoidal height or elevation. If this is ambiguous before going to the site, the meaning of the acquired data can become unclear later.

Next, check at a known point. At the same time, confirm which reference the known point’s height is managed under and compare it with the screen value. If necessary, organize how corrections or transformations will be handled operationally. It is reassuring to recheck after a short interval rather than relying on a single check; height assessments value stability more than instantaneous values.

Then, check the observation environment: sky openness, nearby reflective objects, communication status, satellite count, and the maintenance of a fixed solution. Environmental influences on vertical measurements are easily overlooked compared with planimetric checks, so develop a habit of observing conditions upon arrival.

During actual observation, do not read a point in an instant and finish; monitor how the values settle. If the value fluctuates in small increments, it may not be stable yet. For critical points, perform multiple observations or remeasurements and record the variation range to aid judgment. When in a hurry on site, this extra step helps prevent later rework.

Also, be conscious of what the acquired height will be used for. The judgement required differs whether you are checking against a design level, verifying temporary works, or performing as-built management. Depending on the purpose, decide whether a single observation is sufficient or whether reobservations or verification with other methods are necessary.

Finally, when sharing results, append a description of what the height means. Instead of just transmitting a numeric height, record whether it is treated as elevation, ellipsoidal height, or aligned to which reference. This prevents confusion when another person reviews the data later. Height troubles often arise not only from numbers but also from insufficient explanation.

By handling RTK heights in the flow of display confirmation, known-point comparison, environment check, stability confirmation, purpose judgement, and explicit reference when sharing, field failures are reduced. Sites that can use heights correctly will see overall reliability of their work improve.

Points to note when handling elevations in public surveys and construction management

When using RTK heights for public surveys or construction management, on-site convenience alone is not sufficient. It is important that the deliverable standards are met and that operations are explainable.

In public surveying, consistency and reproducibility of results are particularly required. If it is unclear which reference the observed heights on site use, or what corrections and transformations were applied, it becomes difficult to provide an explanation later. When comparing with control point results or existing drawings, confirm that the numbers being compared are on the same basis.

In construction management, comparison with design values is central, so height discrepancies directly affect quality judgments. For processes where height directly ties to as-built evaluation—such as tops of structures, bedding, backfill, pavement thickness, and drainage gradients—it is important that site personnel understand the height reference. If the design is managed in elevation but the site reads ellipsoidal height, apparent errors may be large and could lead to unnecessary corrections or rework.

Also, when multiple people work on the same site, consistent terminology is essential. If words like height, elevation, reference height, and correction value are used with different meanings by different people, perceptions will diverge even when viewing the same numbers. Simply sharing which reference will be used for heights during morning briefings or pre-task meetings helps prevent problems.

Furthermore, if you use a local site standard, document that rule clearly. Operating under an ad hoc site reference is possible, but if the relationship to public deliverables or external submissions is not organized, data integration may become impossible later. Advancing a local method for convenience can increase burden during handover or inspection.

In practice, height is not a number you can reconcile at the end. Initial settings and checks determine subsequent quality. Because vertical aspects are more easily overlooked than planimetric ones, it is important to organize them carefully from the start.

Summary: Understand RTK elevations correctly to stabilize on-site decisions

Confusion about heights in RTK surveying does not arise simply because the numbers are complex. The essential cause is that similar-sounding terms—ellipsoidal height, geoid height, elevation—refer to different bases but are easily treated as the same “height.” That is why it is important not to read displayed values blindly but to understand what those numbers mean.

As explained, GNSS fundamentally handles ellipsoidal height, which differs from the elevation typically required on site. Geoid height is the concept that bridges that difference. Understanding this relationship makes it easier to resolve many common issues such as mismatches with known points, device-to-device differences, and confusion when comparing with design levels.

In practice, the basics are to confirm the type of displayed value, compare with known points, check height stability, and judge the required accuracy according to the purpose. Vertical references require more careful confirmation than planimetric references, and small misunderstandings can lead to major rework. Conversely, mastering these points markedly improves the usability of RTK surveying.

Tasks involving heights on site—checking control points, comparing with existing structures, as-built verification, and setting out—are diverse. To carry out these routine tasks more efficiently and without hesitation, it is important to prepare a positioning environment that is easy to use for both planimetric and vertical dimensions. High-precision GNSS devices like LRTK that can be attached to an iPhone make it easier to perform on-site coordinate checks and quick surveys, and by applying them with a correct understanding of how to read elevations, daily positioning work becomes smoother. By organizing concepts of elevation and combining them with on-site verification procedures, RTK surveying becomes an even more practical and powerful tool.