What is elevation correction? Learn the basics, calculation methods, and 6 checkpoints

When you feel on site that “the elevation doesn’t match,” “the height differs on measurements taken on different days at the same location,” or “RTK heights don’t match the design drawings or known points,” the first thing to suspect is not the positioning accuracy itself but the elevation reference and the correction procedure. In Japan, elevations are defined under the Survey Act with mean sea level as the reference, and the system is managed with the average sea level of Tokyo Bay defined as elevation 0 m (0 ft). However, heights obtained by satellite positioning (GNSS) are “ellipsoidal heights,” which do not match elevations referenced to mean sea level (the geoid) as-is.

Elevation correction fills this gap. Treat elevation correction not merely as memorizing a formula but as a practical procedure to convert satellite-derived heights into heights usable for field work (design, construction, as-built, inspection, disaster response), ensuring reproducibility and accountability. This reduces errors. In particular, from April 1, 2025, Japan’s control point elevation results were revised to “values based on satellite positioning,” and the new result framework (Geodetic Results 2024) along with the supporting geoid model (Geoid 2024) and related data began to be provided. If you continue operating with old habits, you may encounter cases where “your work is correct but the results don’t match.”

This article organizes the basics of “what elevation correction is,” the rationale for calculation methods, and six checkpoints to avoid confusion on site, presented as a practical workflow. The explanation is device- and software-agnostic, so it’s useful both for pre-adoption planning and for reviewing current operations.

Table of Contents

• Background on why elevation correction is necessary

• Basics of elevation, ellipsoidal height, and the geoid

• Calculation methods for elevation correction

• Points to check on site

• Common failures and troubleshooting

• Tips to stabilize elevation correction in RTK operations

• Making elevation correction routine with LRTK

Background on why elevation correction is necessary

Elevation is used as the “elevation of ◯ m (◯ ft)” shown on maps for decisions directly related to gravity and the behavior of water—drainage planning, irrigation, road longitudinal profiles, flood/tidal disaster planning, etc. The Geospatial Information Authority of Japan explains that the elevation reference is mean sea level and that, because gravity distribution is not uniform, water can flow even across visually flat terrain; therefore the elevation reference is determined with these factors in mind. In other words, elevation is based not only on terrain relief but on a reference surface consistent with gravity (the geoid).

On the other hand, heights obtained by GNSS are ellipsoidal heights. The ellipsoidal height is the geometric height from a reference ellipsoid to a ground point, and its reference surface differs from the mean sea level used for elevation. The Geospatial Information Authority of Japan’s materials organize this relationship and explain that elevation can be obtained by subtracting geoid height from ellipsoidal height.

In practice, note that Japan’s elevation origin is not simply “Tokyo Bay mean sea level = 0 m (0 ft).” The Survey Act prescribes Japan’s latitude–longitude origin and the Japan Vertical Datum (Japan’s height datum) as survey origins, and it allows the Director-General of the Geospatial Information Authority of Japan to approve different origins in special cases such as surveying remote islands. GSI’s explanations indicate that for remote islands, operations may use the island’s own mean sea level as the elevation reference.

To handle the difference between an island’s own mean sea level and Tokyo Bay mean sea level, a reference-surface correction value was introduced. GSI defines the reference-surface correction value as “the difference between Tokyo Bay mean sea level and the island-specific mean sea level” and provides reference-surface correction parameters as data representing the value at arbitrary positions. GSI also clarifies that in some remote islands, both geoid height and the reference-surface correction value are required when obtaining elevations by satellite positioning.

Thus, elevation correction sometimes only requires “subtracting geoid height from ellipsoidal height,” while in some areas (remote islands, etc.) you must also include the reference-surface correction value. If you enter the field without this knowledge, your calculations may be correct but the results will not match due to differing references—one of the most troublesome problems.

Basics of elevation, ellipsoidal height, and the geoid

To reduce confusion in practice, first organize “which height is measured from which surface” in one relationship. GSI’s explanation shows that elevation is referenced to mean sea level, the extension of mean sea level onto land is the geoid, and the height from the ellipsoid to the geoid is the geoid height.

What matters here is that there are three main types of height used on site.

First, ellipsoidal height. This is the height directly obtained from GNSS positioning: the height from the reference ellipsoid to the ground point.

Second, geoid height. This is the height difference from the reference ellipsoid to the geoid, and it is easiest to think of it as the “offset of the reference surfaces” used to convert ellipsoidal height to elevation.

Third, elevation. This is the height referenced to mean sea level (the geoid), and Japan’s elevations defined under the Survey Act are explained as using Tokyo Bay mean sea level as elevation 0 m (0 ft).

When these three are mixed up, the field situation becomes not “the heights don’t match” but “it’s unclear what is being compared to what.” Especially with RTK and other systems that display heights in real time, work tends to proceed with ambiguity over whether the displayed height is ellipsoidal height or elevation. The first step in elevation correction is to define which height is used for display, recording, and deliverables.

Another point made more important by the 2025 revision is the “generation of the result framework.” GSI revised control point elevation results nationwide on April 1, 2025, moving the elevation system to one based on satellite positioning and providing the revised control point results as Geodetic Results 2024. Related data and documentation have also been published.

On-site elevation correction depends not only on the geoid model and reference-surface correction value but also on “which generation of control point results you reference.” That is why it is necessary in practice to align assumptions before calculations.

Calculation methods for elevation correction

The basic formula for elevation correction is surprisingly simple. GSI explains that elevation can be obtained by subtracting geoid height from the height determined by satellite positioning (ellipsoidal height).

For the basic region (the area where Tokyo Bay mean sea level is used as the elevation reference), the concept is as follows.

Elevation (H) = Ellipsoidal height (h) − Geoid height (N)

This is also summarized in explanations of the Quasi-Zenith Satellite System: elevation is the ellipsoidal height minus the geoid height (the difference between the ellipsoid and the geoid).

In some remote islands where a reference-surface correction value is required, the relationship between ellipsoidal height and elevation includes the reference-surface correction value (C). GSI defines the reference-surface correction value as the difference between Tokyo Bay mean sea level and the island-specific mean sea level, and states that in the applicable areas, both geoid height and the reference-surface correction value are used. GSI also presents the relationship: ellipsoidal height in remote islands = elevation + geoid height + reference-surface correction value.

Therefore, in such island areas the formula becomes:

Elevation (H) = Ellipsoidal height (h) − Geoid height (N) − Reference-surface correction value (C)

What is confusing in the field is “where to obtain N and C, and in what form to use them.” GSI organizes three methods for this.

The first is to calculate values from Geoid 2024 data and reference-surface correction parameters and subtract them from the ellipsoidal height.

The second is to subtract values computed from an integrated file that combines both. The integrated file can be used nationwide, not only in areas requiring the reference-surface correction value, and GSI states it will provide the integrated file for a transitional period to smooth the shift in the elevation system, with plans to discontinue it in the future. For field operations that want a single nationwide process without branching settings, using the integrated file is a reasonable approach. However, since the integrated file may be discontinued in the future, it is safer to also establish procedures for data updates and operational migration.

The third is to use calculation services such as geoid height calculation services to obtain the geoid height and reference-surface correction value for the point in question and subtract them from the ellipsoidal height.

Although the formula fits on one line, field problems arise when the input height is not an ellipsoidal height, when N or C are not applied, or when result frameworks are mixed. The next chapter narrows the on-site checkpoints to six.

Points to check on site

To avoid failing at elevation correction on site, what matters more than the calculation itself is a quick method to confirm that the calculation is being applied correctly. Here are six checkpoints that practitioners searching for “how to perform elevation correction” on site can directly turn into operational rules. None of them depend on specific devices.

The order of these checkpoints matters. First question the reference, then the data application, and finally the positioning or observation conditions—this order speeds recovery.

Checkpoint 1: Clearly identify which type of height you are comparing. First determine whether the value you are looking at is ellipsoidal height or elevation, and whether the known points and design drawings use one or the other. GSI organizes that ellipsoidal height is obtained by satellite positioning and that elevation is obtained by subtracting geoid height from ellipsoidal height. If this premise is ambiguous, you may appear to have a mismatch even when corrections are applied correctly.

Checkpoint 2: Confirm whether the elevation reference is Tokyo Bay mean sea level or an island-specific mean sea level. While Japan’s elevations are generally defined with Tokyo Bay mean sea level, the Survey Act allows different origins in special cases such as remote island surveys. GSI also explains that in remote islands the island’s own mean sea level may be used as the elevation reference. If your site is in an applicable region but you are not applying the reference-surface correction value, a constant offset will persist.

Checkpoint 3: Verify that the geoid model (Geoid 2024, etc.) is correctly applied. GSI provides Geoid 2024 and indicates it should be used in operations after the elevation result revision; it also warns to confirm that software can successfully read the files before use. In the field, accidents occur where a file thought to be set is not actually loaded, the format is different from expected, or an old model is still being referenced. Always perform test calculations on known points and numerically confirm whether the geoid application is taking effect.

Checkpoint 4: Confirm whether the reference-surface correction value needs to be applied and, if so, that the data used are correct. GSI specifies the areas requiring the reference-surface correction value, indicating “south of the Tokara Islands and south of Hachijō Island,” and provides guidance on how to obtain the reference-surface correction parameters in its Q&A. In applicable areas, you must subtract both geoid height and the reference-surface correction value when obtaining elevation from ellipsoidal height. If this step is omitted, no amount of field effort will remove the offset.

Checkpoint 5: Align the generation of the result framework. GSI provides revised control point results as Geodetic Results 2024 from April 1, 2025, and its Q&A shows rules for distinguishing them from the pre-revision Geodetic Results 2011 (such as notation in result tables). If known points remain based on the old results while the field operates under the new assumptions (Geoid 2024, Geodetic Results 2024), inconsistencies arise. If something that was matching yesterday suddenly doesn’t match, first suspect mixing of result generations.

Checkpoint 6: Fix the on-site verification rules. Single matches can occur by coincidence. What’s important is reproducibility: repeated checks on the same known point should yield the same result, and checks at different times or on different days should be consistent. Although the revision to elevation results promises faster availability of elevation data based on satellite positioning, field quality requires incorporating inspections and confirmations into operations. GSI advises checking documentation and confirming successful software loading before using data. In practice, make morning checks of known points mandatory, and if abnormalities appear, resolve them in order from the correction assumptions (height type, geoid, reference-surface correction, result generation). Doing so stabilizes elevation correction.

Common failures and troubleshooting

Elevation correction problems often show similar symptoms. Here, causes are organized with “what is happening” and “how to isolate the cause.” The key is to eliminate mixed references and settings before discussing whether positioning is poor.

The most common case is treating ellipsoidal height as elevation. If GNSS devices or apps only display “height,” users tend to assume it is elevation. But GSI clarifies that satellite positioning provides ellipsoidal height and that elevation is obtained by subtracting geoid height from ellipsoidal height. The remedy is simple: always label display fields as “ellipsoidal height” or “elevation,” and fix the type of height recorded.

Next is confusing or failing to apply the geoid model. Even when you intend to calculate elevation correction, accidents occur where the geoid file isn’t loaded, an old geoid model is referenced, or file format differences cause calculation errors. GSI warns to confirm that Geoid 2024, reference-surface correction parameters, and integrated files can be successfully read by software before use. Mitigation is to always perform test calculations on known points and numerically confirm that geoid subtraction is applied.

The third is failing to apply the reference-surface correction value. This often happens in projects involving remote islands or Okinawa when teams mistakenly use the same formula as the mainland. GSI specifies the areas requiring the correction value and defines it as the difference between Tokyo Bay mean sea level and the island-specific mean sea level. The countermeasure is to first determine whether the site is in the applicable area; if so, correct using H = h − N − C and record the data source and version.

Fourth is mixing result generations. From April 1, 2025, GSI revised control point elevation results and provides them as Geodetic Results 2024. GSI’s Q&A also shows rules for distinguishing Geodetic Results 2024 in result tables. If only some known points don’t match or some points show a constant offset, check whether the known points’ result generations are mixed (Geodetic Results 2011 vs. Geodetic Results 2024). The response is to standardize the known-point list at project start: either consistently use old results, or migrate all points together to the new results.

Fifth is when numeric values agree but they don’t match “field intuition.” This often stems from misunderstanding the nature of elevation (a surface consistent with gravity). GSI explains that because gravity distribution is not uniform and water flows accordingly, accurate elevation requires a reference surface reflecting gravity distribution. In the field, judging height by visual relief alone can produce a sense of mismatch. The remedy is to share within the team that elevation aligns with design and water flow, and to define evaluation criteria for elevation correction results as “map elevations.”

Tips to stabilize elevation correction in RTK operations

In RTK environments, elevation correction becomes an operational matter of “settings and checks” rather than a one-off calculation. This is because RTK fundamentally provides ellipsoidal heights, and elevation is obtained only after subtracting geoid height (and the reference-surface correction value where required). GSI’s materials for public surveying state clearly that elevation is obtained by subtracting geoid height and the reference-surface correction value (as obtained from geoid calculations, etc.) from the ellipsoidal height.

A practical tip is to apply the same rules for elevation correction to both on-site real-time displays and recorded data. Mixing real-time display as ellipsoidal height with records as elevation causes inevitable confusion in stakeout checks and communication. If both display and records are unified as elevation, on-site decisions align with water flow and design elevation standards. Therefore, as minimum practical rules adopt: (1) fix the geoid model, (2) include the reference-surface correction value when the area requires it, (3) align the result generation, and (4) perform morning known-point test calculations.

Also include data update handling in operations. GSI provides Geoid 2024, reference-surface correction parameters, and an integrated file in line with the elevation result revision, and states the integrated file will be provided only for a transitional period with future discontinuation planned. Therefore, field teams should record which data they use and have verification procedures for updates. A stable operation prevents confusion every time data are updated.

Finally, to avoid making elevation correction dependent on an individual’s intuition, standardize how results tables and work records are written. GSI’s Q&A shows notation rules for result tables; at the field level, it is effective to note the result generation for known points, the geoid model name used, and the types of corrections applied in project records.

Making elevation correction routine with LRTK

The biggest reason elevation correction breaks down on site is that when work is busy, “checks and confirmations are omitted.” Even with the correct formula, a single mix-up—ellipsoidal height versus elevation, missing geoid application, omission of the reference-surface correction value, or mixing result generations—can rapidly undermine confidence in field heights. GSI requires checking documentation and confirming successful software loading before using Geoid 2024, reference-surface correction parameters, and integrated files, but that also implies the need to incorporate confirmations into field operations.

A useful approach is to make elevation correction a daily routine rather than a special task. Implement morning known-point checks, judgment of whether the site falls within the applicable area, unify display and records as elevation, and record the correction conditions used as standard field operations.

One option to help operationalize this is LRTK (iPhone-mounted GNSS high-precision positioning devices). By combining a smartphone for field positioning, recording, and sharing, inspections and confirmations become “done on the spot” rather than “doing later.” Elevation correction is not completed by device performance alone; it becomes a trusted result only when references and confirmations are aligned. Using a portable configuration like LRTK and incorporating the six elevation-correction checkpoints into the daily field flow brings RTK real-time displays closer to an operation where heights can be handled without confusion.