What Is the Difference Between Ellipsoidal Height and Geoid Height? Seven Steps to Check RTK Elevation

When you start using RTK surveying on site, many practitioners will at least once be puzzled about how to read elevation. Even if horizontal positions can be confirmed to centimeter-level, it is not uncommon for elevation alone to not match the expected value, to differ from existing drawings, or to show discrepancies compared to control points. In many cases the cause is not a failure of the positioning itself but a lack of clear distinction between ellipsoidal height and geoid height and an unclear concept of “elevation.”

RTK in particular derives high-accuracy coordinates from three-dimensional positions obtained from satellites, so if the “elevation” used on site and the height concept that the device or app uses internally do not match, it is easy to misread values. If this remains ambiguous in practice, unnecessary re-measurements and rework can occur in as-built verification, construction management, control point checks, and comparisons with design values.

On the other hand, once you properly understand the relationship between ellipsoidal height and geoid height, RTK elevation displays are not that difficult. What matters is to check in sequence what the number you are looking at actually means, which reference it is based on, and which type of height is needed on site. Memorizing the concept alone often leads to confusion in practice, so it is important to organize it into on-site verification steps that can be reproduced.

This article explains the difference between ellipsoidal height and geoid height in practical terms, then describes how to think about RTK elevation checks on site and provides seven verification steps to prevent oversights. It will be useful not only for those who are just starting to use RTK but also for those who already use it but are not confident about elevation alone. The goal is to eliminate misreading of heights so you can make decisions on site without hesitation.

Table of contents

• Why mixing up ellipsoidal height and geoid height makes RTK elevation look off

• Understanding ellipsoidal height in practical, on-site terms

• Understanding geoid height by translating it into practical work

• Why the elevation used on site and the height inside RTK do not match

• RTK elevation check step 1: Confirm the type of height currently displayed

• RTK elevation check step 2: Confirm the coordinate system and height datum in use

• RTK elevation check step 3: Confirm whether geoid correction is applied

• RTK elevation check step 4: Perform field comparisons at known or control points

• RTK elevation check step 5: Recheck antenna height and installation conditions

• RTK elevation check step 6: Confirm communication state and Fix status

• RTK elevation check step 7: Unify on-site operational recording rules

• Understanding ellipsoidal height and geoid height stabilizes RTK operations

• Summary

Why mixing up ellipsoidal height and geoid height makes RTK elevation look off

The main reason confusion arises with RTK elevation is that the height field staff usually think about is not the same as the height directly obtained by satellite positioning. What many people commonly call “elevation” tends to be closer to a value based on sea level. However, the height first obtained from GNSS positioning is the height relative to a smooth, rotating ellipsoid used to approximate the Earth. This is the ellipsoidal height.

In contrast, elevations used in land surveying and civil engineering practice—those in design documents, existing deliverables, longitudinal plans, and as-built management—are often considered in a practical height system that reflects the direction of gravity. This is where the concept of the geoid-based height comes in. In other words, there is a difference in reference surfaces between the raw height the RTK device internally obtains and the elevation desired on site.

If you compare numbers without understanding this difference, the value shown by the device may appear to be incorrect or inconsistent with known point results. Even when positioning is stable, different types of heights will not match. For example, if you are looking at the ellipsoidal height at a point while your field records are organized on an elevation basis, the difference will be equal to the correction amount. And because this difference is not constant by location, trying to reconcile it by simple heuristics is risky.

In practice, elevations are often checked more strictly than horizontal positions. Slight interpretation differences can affect work quality in slope gradients, equipment installation, pavement and earthwork elevation control, and interfaces with existing facilities. That is why it is crucial not to assume that the values obtained by RTK are “elevation” without checking whether they are ellipsoidal height or geoid-corrected height.

Confusion about height stems not so much from lack of knowledge as from the invisibility of switching reference surfaces. In other words, if you can organize the system, you can prevent the problem. First clarify what ellipsoidal height and geoid height each represent, and then translate that into an on-site elevation check procedure—this is the shortest route to stable RTK operations.

Understanding ellipsoidal height in practical, on-site terms

Ellipsoidal height is the height from an ellipsoidal surface used to represent the Earth smoothly and conveniently for mathematical calculations to the observation point. GNSS positioning, including RTK, calculates three-dimensional position with reference to this ellipsoid, so the first height information you obtain is fundamentally the ellipsoidal height.

What is important here is that ellipsoidal height is suitable for satellite positioning calculations but does not necessarily match the on-site sense of height. On site people ask “what is the elevation above sea level at this point?” or “what is the difference from the design elevation?” Ellipsoidal height is not always convenient for such judgments because the ellipsoid is a mathematical reference surface and does not directly represent gravity or the average sea surface.

That said, ellipsoidal height is not unnecessary. In fact it is a very important value for understanding how RTK works. Ellipsoidal height is the basis of positioning, and from it you apply appropriate corrections and transformations to get closer to the elevation needed on site. In short, ellipsoidal height is the starting point. If you look only at the outcome without knowing the starting point, you will not be able to trace where differences originated.

A common practical case is that when device settings are changed, the displayed height suddenly changes. This does not necessarily mean positioning accuracy has suddenly degraded—it can often mean that the display target switched from ellipsoidal height to a corrected height or vice versa. If the meaning of the number changes, the displayed height changes significantly. Therefore, when checking height on site, develop the habit of first confirming whether the current display is showing ellipsoidal height.

Ellipsoidal height can also be useful when technically confirming whether position is coming out correctly. For post-processing, comparing with other data, and confirming coordinate systems, understanding ellipsoidal-height-based values makes it easier to identify where transformations have been applied. Rather than seeing elevation only as the final deliverable, you should grasp ellipsoidal height as a basic term to understand how RTK handles different heights.

Understanding geoid height by translating it into practical work

To understand geoid height, first get an image of the geoid itself. The geoid is a reference surface determined by the Earth's gravity field and is often described as a surface that extends the average sea surface under land. Because on-site elevation is often used with a sense close to this geoid-based height system, the geoid is essential for linking RTK heights to practical work.

Technically, geoid height is used to denote the separation between the ellipsoid and the geoid. At a given point the ellipsoid and the geoid do not coincide; there is a difference between them. This difference is used to convert ellipsoidal height to the height in the practical elevation system you want to use. In other words, geoid height by itself is not the on-site elevation but rather the bridge to reinterpret ellipsoidal height as a practical elevation.

For practitioners, it can be easy to think of geoid height as “the key correction to bring GNSS heights closer to the usual sense of elevation.” If ellipsoidal height is the satellite-computation world, geoid height is the information that connects that world to the on-site elevation sense. Without this bridge, no matter how precisely GNSS determines height, comparisons with design values and existing deliverables will be confusing.

Be aware that how geoid height is treated varies by location. A difference established at one site cannot necessarily be used unchanged at another region. Because the Earth's gravity field and the relationship with the reference surfaces are not uniform, the discrepancy between ellipsoidal height and an elevation datum varies geographically. Applying a fixed value from a previous site to a different site can break elevation consistency.

Also, depending on the device or app settings, geoid correction might be applied automatically and shown, or the display might remain ellipsoidal height. Even if the screen simply shows “height” or “elevation,” the underlying content may differ. That is why you should not dismiss the term geoid height as mere jargon; understand it in relation to ellipsoidal height. In practice, this understanding alone raises the accuracy of checking settings and reduces unexplained elevation discrepancies.

Why the elevation used on site and the height inside RTK do not match

When RTK elevation does not match expectations, many first suspect reception environment or communication conditions. Those factors are important, but there are plenty of cases where heights do not match even when Fix is achieved. What should be reviewed in such cases is whether the elevation used on site and the height basis inside RTK are consistent.

On-site elevations must be consistent with design drawings, known-point deliverables, management criteria, and existing ledgers. However RTK first computes positions with reference to an ellipsoid. If you display that directly, it may not match the on-site elevation you need. In other words, it is not an issue of numerical accuracy but of using a different measuring stick.

For example, if two people measure the same point but one is looking at a device showing corrected height while the other is looking at ellipsoidal height, they may each think the other is wrong. In reality both are displaying correctly according to their respective standards. Continuing a discussion in that state will not reveal the cause. What needs to be aligned first is not measurement technique but the premise of which height is being viewed.

Confusion is also caused by the coexistence of multiple height-related pieces of information on site. Design elevation, ground elevation, as-built elevation, known-point elevation, and device display elevation are all called “height” but differ in content. Adding ellipsoidal height and geoid-corrected height to the mix without organizing terminology leads to misunderstandings. In RTK elevation checks, before looking at the value itself you must clarify what type of height it represents.

To avoid height mismatches you must not only configure devices correctly but also unify recognition within the site. Share height standards among design, construction management, and surveying staff, and record which standard a value follows in reports and photo records to reduce later confusion. It is not abnormal for RTK internal height and on-site elevation to differ. The problem is using them without noticing the difference.

RTK elevation check step 1: Confirm the type of height currently displayed

The first step in checking RTK elevation is to clarify what type of height is currently being displayed by the device or app. If this is left vague and you proceed to the next checks, all subsequent decisions will be unstable. The most common oversight on site is this seemingly basic lack of confirmation.

Even if the display label reads “height,” “elevation,” “above sea level,” or “altitude,” the underlying meaning is not necessarily the same. The device may be showing ellipsoidal height or a geoid-corrected value. Moreover, even if the screen shows a single term, the reference can change based on internal settings. Therefore, do not judge by label alone; check the settings screen and the specification details.

When performing this check, do not only look at the current display name but also trace which reference surface the height is relative to, whether corrections are applied, and whether an external height model is referenced. If there is a history of setting changes, confirm when the display method was changed. It is not uncommon for changes in displayed values at the same point to be caused by display-standard changes rather than positioning error.

Also, multiple devices are often used on site. If one shows ellipsoidal height and another shows corrected height, simultaneous observations will produce numeric differences. Treating that difference as an error can lead to unnecessary re-observation or suspicion of device malfunction. When comparing devices, especially, ensure the same type of height is being displayed.

Confirming the type of height is both a technical measurement check and a communication check for site management. If the team can verbalize “what height are we looking at now,” decision-making becomes much faster. Performing this first step carefully prevents more than half of common confusion in RTK elevation checks.

RTK elevation check step 2: Confirm the coordinate system and height datum in use

After identifying the height type, the next thing to check is which coordinate system and height datum the value is based on. In RTK, height is handled as part of the coordinate system as well as position, so even if planar coordinates match, differing height datums will make agreement difficult. On site, because planar checks are visually easier, verifying height datum tends to be postponed, but if you handle elevation you must do this.

Comparing RTK display values with known-point deliverables or design drawings without knowing which datum those documents use is meaningless. The important thing is that both sides of the comparison are organized on the same standard. For example, even if the positioning side uses a certain standard, if the reference deliverables operate on a different standard the heights will not align. Rather than judging only by magnitude of difference, suspect mismatched datums first.

As part of this check, review the routes by which coordinate information is exchanged on site. If surveying files held by surveyors, design values referenced by construction staff, and location information recorded in photo management are managed under different premises, the meaning of height can change somewhere along the chain. If someone on site cannot immediately answer “what datum is this height based on,” consider it likely to cause trouble later.

Also note that devices or data import may perform automatic coordinate transformations or height conversions. Even if users have not explicitly set them, they may be processed using default values. Therefore, check not only the display screen but also project settings, coordinate settings, and correction settings across related items.

Confirming height datum is a modest task but one of the most efficient ways to reduce re-measurements on site. If coordinate system and height datum are aligned, any minor differences can be attributed to reception conditions or installation conditions. If datums are not aligned, no matter how carefully you observe, you cannot settle the result. In RTK elevation checks, aligning the measuring sticks of comparison is fundamental.

RTK elevation check step 3: Confirm whether geoid correction is applied

A particularly important item in elevation checks is whether geoid correction has been applied. Because RTK fundamentally works with ellipsoidal height, there are many situations where using a geoid-based correction is necessary to get to a more practical and user-friendly elevation. Missing this check can leave you unable to explain numeric differences.

A common on-site mistake is assuming “it shows elevation, so it must be corrected.” In reality, display labels and correction status do not always match. One device may be corrected while another is not; this is especially likely if you are operating with initial settings. You must understand what your device or app automatically does and what the user must configure.

When checking whether correction is applied, do not just check the on/off state; also confirm which geoid model is referenced, whether it is suitable for the area, and whether updates or switching have been correctly reflected. If any of this is unclear, validate the practical appropriateness by comparison with known points. Even if theoretically corrected, the value is meaningless if it does not match practical on-site numbers.

Also remember that enabling geoid correction alone does not resolve all elevation differences. Antenna height input errors, unstable Fix, misidentification of control points, and differences in the datum used in forms can also overlap. Therefore geoid correction is not a magic setting but one element of height verification. Still, because overlooking it complicates the entire process, its priority is high.

As a practical measure on site, explicitly list “geoid correction status” in pre-observation checks. If the team uses a common checklist, anyone can start observations with the same premise. Many RTK elevation problems arise from omissions in such basic checks rather than difficult theory. Making geoid correction status explicit each time contributes to stable elevation management.

RTK elevation check step 4: Perform field comparisons at known or control points

Even after confirming settings, you should always perform field comparisons at known points or control points. Even when the settings are theoretically correct, operational conditions may change once equipment is brought to the site. To build confidence in elevation checks, you must measure at points with well-defined heights and compare them to expected values.

The purpose of comparing at known points is not only to see if the numbers match. It is meaningful to observe how large the differences are, whether the differences are constant, and whether they are reproducible with repeated observations. If the difference is constant, it points to datum settings or corrections; if the difference varies, suspect the reception environment or installation conditions.

A critical part of this step is ensuring that the reference point information itself is reliable. Using outdated records or mistaking points on site will leave you unable to determine whether RTK or the reference value is incorrect. When using known points, carefully check the point’s history, management status, and confirm its location on site.

Also, do not stop at a single comparison—repeat measurements at different times and with changed setup to improve certainty. RTK heights are sensitive to environmental influence, so a single match is not sufficient. Confirming stable results through repeated observations helps judge whether the method is robust for routine operations.

On site, time pressure can tempt you to skip this comparison. However, performing a short known-point check before observation is far more efficient than later doubting the whole dataset and re-measuring. In sites where heights are a concern, initial control-point verification dictates overall quality. RTK elevations become trustworthy only after on-site validation at known points in addition to configuration checks.

RTK elevation check step 5: Recheck antenna height and installation conditions

Even if you understand ellipsoidal and geoid heights, antenna height and installation conditions are surprisingly easy to overlook. If you look for only the complicated reference-surface story, you may miss basic mistakes at your feet. In RTK elevation checks, confirming installation conditions is as important as theory.

If the antenna height entry is wrong, the height value will be systematically offset by that amount. Because the resulting number will look plausible, this error is hard to spot. Pay special attention when observation style changes, when you change the type of pole or mount, or when you alter how you carry the device mid-job. If you treat the number without understanding where the antenna reference is taken, alignment of heights will fail.

Installation conditions matter too. Device tilt, loose fastening, wobble in holding position, and ground stability affect reproducibility of height. Heights are more sensitive than planar positions to such subtle differences. If heights vary when observers change, suspect installation conditions before reference-surface issues.

Moreover, in locations with poor visibility or many multipath reflections, the height component can become unstable. In these situations the device may appear to be measuring but is disadvantaged in producing a stable height. Therefore standardizing installation conditions is important. If you set simple rules for observation posture, holding methods, pre-observation wait times, and checks, you can reduce variability.

RTK elevation checks should proceed on two wheels: understanding numerical meanings and standardizing observation conditions. Even with correct understanding of ellipsoidal and geoid heights, misentered antenna height produces mismatches. Conversely, even with stabilized installation, choosing the wrong height datum yields mismatches. The ability to separate these two causes greatly affects on-site judgment.

RTK elevation check step 6: Confirm communication state and Fix status

One final item you must not overlook in RTK elevation checks is communication state and Fix status. Even with correct understanding of ellipsoidal and geoid heights, proper settings, and correct antenna height, if the positioning state itself is unstable, elevation reliability decreases. The height component in particular is more easily affected than horizontal position, so checking Fix status is mandatory.

On site people sometimes assume that because coordinates appear on the screen, everything is measured correctly. But in RTK, whether the solution is Fix and whether it is stably maintained greatly affects the confidence in values. Momentary Fix is not sufficient; you must check whether the state fluctuated during observation, whether there were communication interruptions, or whether correction information was unstable. When heights do not match, habitually review the observation state history to narrow down causes.

Communication degradation can also affect values subtly. A total cut is obvious, but intermittent instability or reduced communication quality may only show as slight numerical fluctuation. When comparing heights, judge not only the momentary value but also whether the value had been stable beforehand.

When checking Fix status, do not rely only on a display icon; consider observation duration and continuity. While in the field you may be rushed to check a single point, at critical moments for height control it is safer to allow a little extra time to confirm stability before reading values. Prioritizing short-term efficiency and adopting unstable values can lead to greater rework later.

When investigating causes of height mismatch, it's important to separate whether settings, datum, installation, or communication are the primary cause. Communication state and Fix status play the role of the final reliability judgment in that separation. RTK elevation is usable in practice only when correct conceptual understanding is layered on top of stable positioning.

RTK elevation check step 7: Unify on-site operational recording rules

The final step to handling RTK elevation stably is to formalize verification results as on-site operational recording rules rather than leaving them to individual experience. Even if a height problem is resolved on the spot, the same confusion tends to repeat with the next person or at the next site. That is why standardizing the verification procedure itself is necessary.

What you should record goes beyond simple observation values. Make it practical to record which height was displayed, whether geoid correction was used, antenna height, results of known-point comparisons, Fix status, the datum used, and any observation notes. With these items recorded, when you review values later you can accurately reproduce the meaning of the numbers.

Especially on multi-person sites, standardizing vocabulary is effective. Be precise in using terms such as ellipsoidal height, corrected height, design elevation, and known-point elevation, and use the same terms in forms and shared notes to reduce misunderstandings. Practitioners do not need to memorize complex theory, but they should at least be able to share what kind of height they are handling using the same words.

Also, it is useful to standardize a troubleshooting sequence. If you set a flow such as check displayed height, confirm coordinate system, check correction, compare known points, confirm antenna height, and verify Fix, anyone can follow the same order to trace causes. This is valuable not only for quality control but also for training and handover.

RTK is convenient, but because settings and standards are not always visible, operating it subjectively tends to cause shifting interpretations of height. Conversely, if you unify check procedures and recording rules, elevation management becomes much more stable. Beyond mastering the devices, the real advantage in practice is sharing the same assumptions within the site.

Understanding ellipsoidal height and geoid height stabilizes RTK operations

As we have seen, confusion about RTK elevation often arises less from positioning accuracy and more from misunderstanding the meaning of numbers. Ellipsoidal height is the height GNSS directly produces, and geoid height is the important element that connects that to the elevation sense used on site. Understanding this relationship prevents panic when heights do not match and enables you to prioritize checks.

What’s important for practitioners is not memorizing difficult theory but being able to explain what the currently displayed height is, what height is needed on site, and how to close the gap. Doing so improves the accuracy of known-point checks and design comparisons, reducing unnecessary re-measurement and misinterpretation. Elevation management quality depends not only on observation technique but substantially on organizing these basic concepts.

Also, the more you use RTK routinely on site, the more elevation checks become a series of small, repeated tasks. If you initially learn the concepts vaguely, you will repeatedly be uncertain in subsequent operations. Conversely, if you organize the difference between ellipsoidal height and geoid height up front, you can apply the same viewpoint at any site. This improves not only efficiency but reproducibility of on-site decisions.

Summary

When handling heights with RTK, it is essential not just to look at numbers but to understand which height datum those numbers represent. Ellipsoidal height is the height directly provided by satellite positioning, and geoid height is the concept used to convert that into the elevation used on site. Mixing these two makes it appear that devices are malfunctioning even when they are working correctly.

On-site verification is most effective if it proceeds from identifying the type of height displayed, to confirming coordinate system and height datum, checking geoid correction, comparing with known points, verifying antenna height, confirming Fix status, and finally unifying recording rules. Organizing checks along this flow makes it easier to trace causes of elevation problems and reduces re-measurements and rework. Stable handling of RTK elevation requires both conceptual understanding and operational procedures.

If you want to make on-site elevation checks more certain and efficient, in addition to this basic understanding it is also important to set up convenient routines that allow quick end-to-end checks from position to elevation on site. With LRTK, by attaching it to an iPhone you can leverage centimeter-level high-precision positioning while more flexibly performing control-point checks and capturing site coordinates. If you want to establish a system that lets you confirm heights on site without hesitation after correctly understanding the difference between ellipsoidal height and geoid height, consider also using LRTK to streamline simple surveying and control-point measurements.