How should elevation correction be carried out? An 8-point guide for beginners on methods and cautions
By LRTK Team (Lefixea Inc.)
When you feel on site that "the height doesn't match," the cause is not necessarily only insufficient positioning accuracy. More often, the issue is that the “height reference” referred to by the word elevation has become mixed up somewhere in the workflow. Heights obtained by satellite positioning are ellipsoidal heights, and they do not directly match the elevations (heights referenced to mean sea level) assumed in maps or design drawings. Elevation correction is the practical work of organizing this difference, correctly applying the necessary data, and converting it into heights usable in operations.
Furthermore, in entity["country","日本","country in east asia"], on April 1, 2025 (Reiwa 7), the elevation results of control points were revised, and the elevation framework shifted to a system based on satellite positioning. Along with this revision, the geoid model “Geoid 2024 Japan and Surroundings,” the reference-surface correction parameters needed for remote islands, and related documents and result tables have been made available. Beginners are likely to become confused during this transition period when the “new elevation system” and “traditional practices” run in parallel and site assumptions are not aligned before work begins.
This article explains how to proceed with elevation correction for practitioners searching for “標高 補正 方法,” especially those encountering elevation correction for the first time, so they can proceed without hesitation. Rather than memorizing formulas, it summarizes what to decide, what to check, and where you are likely to stumble, in eight items of methods and cautions. The goal is that, after reading, elevation correction on site becomes “a reproducible task with the same quality each time.”
Table of contents
• Reasons why elevation correction is necessary
• Preconditions and terminology to align first
• Overview of the elevation correction calculation method
• Eight methods and cautions so beginners don't get lost
• On-site verification procedure and thinking about tolerances
• Common failure patterns and how to handle them
• Embedding elevation correction on site with LRTK
Reasons why elevation correction is necessary
The reason elevation correction is necessary is that elevation is a height referenced to mean sea level. Japan’s elevation standard is defined by the Survey Act as mean sea level, and the state’s explanation clarifies that the surface obtained by extending mean sea level over land is called the geoid. The “X m above sea level” values used in practice use this geoid as the reference surface.
On the other hand, heights obtained directly from satellite positioning are ellipsoidal heights. An ellipsoidal height is a geometric height measured from a reference ellipsoid that mathematically approximates the Earth, and its reference surface differs from the geoid used as the elevation reference. Therefore, if you treat ellipsoidal height as elevation as-is, you will encounter inconsistencies with design drawings, known points, and past results.
The concept of elevation correction is simple: elevation is obtained by subtracting geoid height from ellipsoidal height. What matters on site is less knowing this formula than deciding which geoid model to use, which elevation result set (generation) to align with, and whether additional reference-surface corrections are needed for remote islands—these must be aligned before work begins.
Preconditions and terminology to align first
The biggest source of confusion in elevation correction is terminology mixing. Here, for beginners, we narrow down to the minimal terms needed on site. The goal is to be able to immediately answer in conversation “which height are we talking about right now.”
First, elevation. Elevation is the height referenced to mean sea level (the geoid) and is generally used in maps, construction, and infrastructure planning. The national explanation states that elevation is related not only to the visible terrain but also to gravity distribution, and that a reference surface called the geoid is necessary for accurate elevation.
Next, ellipsoidal height. Ellipsoidal height is the height obtained by satellite positioning, measured from the reference ellipsoid to the ground point. This is where the common misunderstanding “satellite-measured height = elevation” occurs, but because the reference surfaces differ, it is normal that they do not match as-is.
Then geoid height. Geoid height is the height difference from the ellipsoidal surface to the geoid surface, and it is the “offset” that connects ellipsoidal height and elevation. entity["organization","国土地理院","japan geospatial agency"] explains that it determines geoid heights from the ellipsoidal surface using gravity data and other inputs.
Finally, a reference-surface correction amount that beginners tend to overlook. For some remote islands, operations may define elevation based on the island’s own mean sea level; in such cases, the difference from the entity["place","東京湾","bay in japan"] mean sea level is treated as a reference-surface correction amount. The Geospatial Information Authority of Japan defines the reference-surface correction amount as the difference between Tokyo Bay mean sea level and the island’s own mean sea level, and indicates that when obtaining elevation by satellite positioning, this amount must be subtracted along with the geoid height in certain areas.
Overview of the elevation correction calculation method
The basic form of the elevation correction formula is very simple. Elevation H is obtained by subtracting geoid height N from ellipsoidal height h. The Geospatial Information Authority’s explanation explicitly states that elevation can be obtained by subtracting geoid height from the height determined by satellite positioning (ellipsoidal height).
Expressed as a formula: Elevation = Ellipsoidal height − Geoid height. This is the core of “elevation correction.” When heights on site don’t match, questioning whether the premises of this formula are aligned first can reduce unnecessary reobservations or configuration tinkering.
However, in areas such as remote islands, the reference-surface correction amount must also be subtracted. The national explanation of the revision of elevation results describes a method of subtracting both the geoid height calculated from Geoid 2024 and the reference-surface correction amount calculated from the correction parameters from ellipsoidal height. It also organizes methods that subtract values obtained from an integrated file or values obtained from a calculation service.
What confuses beginners here is “which data to use in which procedure.” The Geospatial Information Authority requests confirmation of data formats (for example ISG format or GML format) and that the data can be properly read by the software before use. In other words, the success of elevation correction is decided less by the “formula” and more by “confirming correct data application.”
Furthermore, where there is a need to convert old elevations to the new elevations on site, another concept called elevation correction parameters appears. These are grid data to approximately convert old results to new results; they can be used but produce certain errors, so the project’s tolerance should be considered, as explained in Q&A and notes for public surveying. Depending on the purpose, elevation correction should use either conversion using the geoid model or recalculation using the correction parameters.
Eight methods and cautions so beginners don't get lost
From here, the way to proceed with elevation correction is organized into eight items in the order beginners won’t get lost. For each item, always understand the “method” and the corresponding “caution.” Elevation correction is a “chain structure” where if any prerequisite is missing, the whole thing can collapse.
First, decide in advance which height will be used in deliverables. Clarify whether the site needs elevation, ellipsoidal height, or both depending on design, as-built, inspection, and delivery units. Elevation is referenced to mean sea level (the geoid), ellipsoidal height is obtained by satellite positioning, and they do not match by definition. The caution is that saying simply “height” in site conversations will start confusion. Make it an operational rule to always indicate whether values on records or screens are elevation or ellipsoidal height.
Second, confirm which elevation results (generation) the known points and design drawings are based on. Control point results obtained after April 1, Reiwa 7 are called “Geodetic Results 2024,” and a rule to distinguish them from the pre-revision “Geodetic Results 2011” has been indicated. The caution is that mixing generations can lead to a situation where “the calculations are correct but they don't match.” First check the generation in the known-point lists and provided result tables, and unify it within the project.
Third, fix the geoid model to be used. In the new elevation framework, Geoid 2024 is central, and the introduction of GNSS leveling using this model is explained even for public surveying. The caution is that mixing it with geoid models used in the past can cause differences of several centimeters to several tens of centimeters depending on location, which is not surprising. On site, decide the model name and data version and ensure everyone computes under the same conditions.
Fourth, check whether a reference-surface correction amount is required in the area. The reference-surface correction amount is the difference between Tokyo Bay mean sea level and the island’s own mean sea level, and in applicable areas it must be subtracted from ellipsoidal height together with geoid height. Areas where the correction amount is needed include south of the Tokara Islands and south of Hachijō Island, and handling for Okinawa Island and some other remote islands is organized. The caution is that omitting this correction in applicable areas will cause discrepancies no matter how carefully you observe. First determine whether the area applies, and if necessary, incorporate the correction amount into the calculation procedure.
Fifth, decide where the calculations will be performed. Methods include obtaining geoid heights and reference-surface correction amounts for each point via a geoid height calculation service and subtracting them, or using an integrated file to subtract them. The caution is incidents where something was “supposedly set” but in reality not applied. Because data must be confirmed to be readable by the software before use, always verify application on test points.
Sixth, when converting old elevations to new elevations, understand the nature of the correction parameters when using them. Elevation correction parameters are grid data that can compute correction amounts to convert old elevations to new elevations; they are convenient but produce certain errors, so you must consider the tolerance. The caution is expecting the correction parameters to produce “complete agreement.” If the required precision is high, decide from project requirements whether conversion by correction parameters is sufficient or additional surveying/inspection is needed.
Seventh, before starting site work, check calculations at known points and decide tolerances before proceeding. Guidance for public surveying shows a procedure where ellipsoidal heights from network RTK, etc., are converted to elevation by subtracting geoid heights obtained by geoid height calculation and reference-surface correction amounts, and states that if known points are in old elevation, they should be converted to new elevation first. The caution is that proceeding on site without verification risks discovering discrepancies late and having to redo all results. Verification is the cheapest insurance.
Eighth, record the correction conditions and results to create reproducibility. With the revision of elevation results, provision of result tables, data, and documents has begun. The caution is that if you measure the same point months later and cannot trace the conditions, the reason for “mismatch” may remain forever unknown. Minimally recording the geoid model name, whether the reference-surface correction amount was applied, the result generation, calculation method, and verification results will stabilize on-site quality.
On-site verification procedure and thinking about tolerances
The biggest moment beginners stumble with in elevation correction is when they have “performed the calculation but cannot judge whether it is correct.” Therefore, it is important to standardize verification procedures and decide tolerances in advance. Official materials from the Geospatial Information Authority warn that conversion using correction parameters produces certain errors, so use them considering the error tolerance for the project. In other words, tolerances should be decided according to the work purpose, not left for the site to decide arbitrarily.
As a verification procedure, first check at known points whether the values displayed as elevation are consistent with known-point results. If they do not match here, before suspecting the observation environment, inspect the premises in the following order: (1) the type of height (elevation or ellipsoidal height), (2) the sign (whether subtraction is reversed), (3) application of the geoid model, (4) necessity of the reference-surface correction amount, and (5) mixing of result generations. This order is also the order of least cost to fix.
Next, re-measure the same point after a short time and confirm whether the difference falls within the tolerance. Elevation correction can look like a mix of “data application issues” and “observation variability,” so whether the result is reproducible by re-measurement helps separate these. If the difference is large, observation conditions (satellite visibility, reflections, equipment setup) may be poor even before the correction calculations. Conversely, if the difference is small and stable, you can judge that the correction premises are largely satisfied.
Finally, always record the judgment results. With the revision of elevation results, provision of result tables and management under the name Geodetic Results 2024 have been indicated, and rules for distinguishing result generations are provided. On site, a short note about which generation, which geoid model, and which correction conditions were used for today’s work will dramatically speed up next-time judgments.
Common failure patterns and how to handle them
Here we present common failure patterns beginners encounter and the corresponding remedial thinking, derived from the symptoms. The key is to eliminate premise and correction issues before concluding “the observations are bad.” Many elevation correction problems can be explained as configuration and operational issues.
If the symptom is “a constant offset everywhere,” first suspect height type confusion and sign errors. Because elevation is defined as ellipsoidal height minus geoid height, reversing the add/subtract direction produces a large offset. Next suspect mixing of result generations. Since rules exist to distinguish Geodetic Results 2024 and Geodetic Results 2011 in result tables, if known points remain mixed with old results, calculations can be correct yet inconsistent.
If the symptom is “only certain regions don’t match,” the most likely cause is omission of the reference-surface correction amount. Areas requiring the correction amount are specified, and in applicable areas ellipsoidal height must be subtracted by geoid height and the reference-surface correction amount. For sites mixing remote island projects, always determine applicability before work and fix the calculation route if correction is necessary.
If the symptom is “values ceased to match across fiscal years,” suspect the revision of elevation results and switching of result generations. Since the implementation date of the revision and the provision of result tables under Geodetic Results 2024 are indicated, if the reference of control point results changes mid-project, the same site can appear to have changed values. The remedy is to set the generation to be used for the project and, if switching mid-project, harmonize known points, designs, and results all at once.
If the symptom is “you applied correction parameters but small residuals remain,” check whether those residuals are within the specification tolerances. Correction parameters are convenient but produce certain errors, so use them with the project’s tolerance in mind. The remedy is to confirm the required precision for the work and, if necessary, not rely solely on correction parameters but consider additional inspection or alternative methods.
Embedding elevation correction on site with LRTK
Correct knowledge alone does not ensure elevation correction becomes standard practice. What determines embedding is an operation that does not omit verification and a system that records results. The Geospatial Information Authority requests confirmation that Geoid 2024 and the reference-surface correction parameters can be read properly by software before use, and clarifies the error and tolerance considerations when converting with correction parameters. In other words, elevation correction is a task premised on “verification each time.”
Beginners often stumble on site because, in the rush, checks of known points are skipped, correction condition notes are not kept, and results become “numbers valid only for that moment.” To close this gap, create an environment where operators can always follow the same verification steps and record results on the spot. Elevation correction is less a single calculation than a habit of verification and recording.
One option is LRTK, a smartphone-mounted GNSS high-precision positioning device. The repetitive tasks required for elevation correction are: (1) assume ellipsoidal height as the starting point, (2) subtract geoid height and reference-surface correction amount if necessary, (3) verify at known points, and (4) record the correction conditions. If you can carry a compact setup on site that integrates positioning, verification, and recording, this repetition becomes a practicable routine. If you want to proceed with elevation correction without hesitation, consider introducing LRTK as an operational measure to stabilize on-site height consistency.
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.


