4 Points to Know About Using Geospatial Information Authority of Japan Data with RTK

Table of Contents

• Why using Geospatial Information Authority of Japan data in RTK is important

• Point 1 Correctly understand the relationship between RTK and Geospatial Information Authority of Japan data

• Point 2: Use representative data appropriate to each purpose

• Point 3: Do not leave the handling of elevation and coordinate systems ambiguous

• Point 4 Decide in advance the operational decisions and items to be confirmed on site

• Summary

Why Using Geospatial Information Authority of Japan Data with RTK Is Important

RTK is a highly effective method when you need to quickly obtain high-precision positions on site. It is used across a wide range of tasks, including surveying, construction, as-built control, maintenance management, preparation of equipment registers, and on-site data collection for drafting. However, RTK is not a technology that functions in isolation. The preconditions you need to prepare in advance vary depending on whether you use the positioning results obtained on site as public coordinates or as site-specific local coordinates, whether you will overlay them with design drawings or existing plans, and whether you will deliver results that include elevations.

What becomes important here is the various datasets maintained by the Geospatial Information Authority of Japan. The concepts of reference systems—starting with GNSS reference stations—base map information, elevation-related data, and the rules of coordinate systems form the foundation for turning coordinates obtained by RTK into practically meaningful results. In other words, RTK is a means of determining position in the field, while GSI data is the common language that correctly places that position within Japan’s reference framework.

At worksites, even if RTK readings are stable at the centimeter level, if it remains unclear which reference those coordinates are defined against, problems arise such as not matching design data, being impossible to compare with observations from other days, and being difficult to reuse even if included on drawings or records. Conversely, if you understand the relationship with data from the Geospatial Information Authority of Japan, it becomes easier to decide which reference to use for the observations, how much can be handled with RTK alone, and where to combine other methods.

This article organizes the relationship between RTK and the Geospatial Information Authority of Japan (GSI) data from a practical standpoint and explains four focused topics: electronic reference stations, fundamental map information, handling of elevations and coordinate systems, and operational checks. We cover each of these points—addressing the areas that commonly cause confusion in the field—one by one.

Point 1 Correctly understand the relationship between RTK and the Geospatial Information Authority of Japan's data

The first point to grasp is that RTK and Geospatial Information Authority of Japan (GSI) data have different roles. RTK is a system for determining the current position with high accuracy by using the satellite signals received by a mobile station (rover) in the field together with correction information. On the other hand, GSI data is the foundation that supports how those high‑precision positions are interpreted in terms of reference frames and how they are aligned with maps and deliverables. Although the two may appear similar, their roles differ, and if you operate while leaving this difference ambiguous, you are likely to end up in a situation where measurements are obtained but cannot be used.

What is particularly important in practical work is the existence of electronic reference points. Electronic reference points are permanent reference points installed throughout Japan, and they form the core of the observation network that serves as the reference for satellite positioning. In network RTK used in the field, even if users are not aware of it, corrections and positional alignment are supported by wide-area reference information. In other words, even if you only look at the rover on site, there is a wide-area reference network behind it, and it is important to understand that concept.

A common misconception here is the idea that if the RTK displayed values are stable, they are correct official coordinates as-is. In reality, the stability of positioning and the suitability of the results are separate issues. Unless the coordinate system used during observation, the on-site standards required for deliverables, the coordinate definitions in the design data, and consistency with existing control point results are aligned, the numeric values themselves may be stable but discrepancies will occur when they are overlaid on design plans or existing survey results. Being a high-precision positioning result does not mean it meets the operational standards you need to use.

For example, when performing as-built verification using public coordinates at road or land development sites, what is required is not simply measuring the current position, but placing that position within the correct plane rectangular coordinate system and, where necessary, treating elevation in a unified manner. Furthermore, if comparisons with existing structures or past results are required, it is a prerequisite that they be tied to the same coordinate system and the same treatment of elevation. This is where the Geospatial Information Authority of Japan’s data plays a role.

Also, when considering the relationship between RTK and data from the Geospatial Information Authority of Japan, it is easier to organize if you divide it into four stages: observation, reference, background information, and finalization. Observation is carried out by RTK; the reference is covered by electronic reference points and control-point results; background information is supported by base map information and terrain- and elevation-related data; and in the finalization stage it is necessary to ensure consistency of the coordinate system and the vertical datum. Understanding this flow makes clear why simply looking at a map on site is insufficient, why verification of control points is necessary, and why the handling of elevations should be decided first.

Furthermore, at sites where RTK has been introduced, increased work efficiency can lead to postponing the verification of reference points. When points can be obtained faster than before, attention tends to focus on the observation itself, but what is truly important is whether the data are left in a state that can be reused in subsequent processes. The significance of utilizing Geospatial Information Authority of Japan data lies in connecting observation points to Japan’s official positional information framework so that the same interpretation can be made the next day, by a different person, or with different software.

In other words, the takeaway from point 1 is that RTK is a technique for determining positions, and Geospatial Information Authority of Japan data is the foundation for using those positions with the correct reference. Understanding this relationship and then clarifying which data to use next is the first step to reducing mistakes in practical work.

Point 2: Use representative, usable data according to purpose

There are several Geospatial Information Authority of Japan (GSI) datasets that are easy to use in combination with RTK, but the important thing is not to apply everything uniformly—use them according to your purpose. Representative datasets commonly relevant on site include electronic reference stations, control point results, Fundamental Geospatial Data, elevation-related data, and GSI Maps. Understanding the role of each can greatly increase the value of the RTK data you obtain.

First and foremost, prioritize electronic reference points and control point results. These serve as the starting point for confirming which reference frame the points acquired in the field are tied to. On sites where management under public surveying and public coordinates is the assumption, confirming the relationship with known points and existing control points is indispensable. Rather than accepting points newly obtained by RTK as final deliverables, you can increase the reliability of your observations by comparing them with existing control point results and by identifying the positions and usability of nearby control points before starting work.

Whether there are reference points available near the site in particular has a major impact on the operational policy. If there are reference points nearby that are easy to check, initial RTK checks and daily verifications become easier. Conversely, if there are no suitable known points in the surroundings and site conditions are severe, it is safer to supplement RTK with the establishment of reference points and check surveys using other methods rather than relying on RTK alone. Electronic reference points and reference-point results should be used not merely as references but as material for deciding the observation plan itself.

Next, one of the datasets frequently used in practical work is fundamental map data. Fundamental map data includes feature data that form the basis for handling location information, such as roads, shorelines, building perimeters, and administrative boundaries. By overlaying this with field points acquired by RTK, it becomes easier to organize equipment locations, visualize inspection routes, check relationships with existing features, and carry out simple register maintenance. For example, in the management of road appurtenances, drainage facilities, signs, manholes, and boundary-related matters, it is important not only to collect points with RTK but also to use the background data to determine which road a point lies along and which features it is related to.

However, base map information is not万能. It should not be treated as measured data that precisely represents current conditions; rather, it should be used primarily as data for background organization and for providing locational context. Newly installed structures on site, modified slopes, or temporary works during construction may not be reflected. Therefore, when using base map information, you should understand that, although it is useful for identifying existing features, assigning attributes, and organizing positions, it is risky to use it as-is as the control line for construction layout (setting-out) or for strict as-built verification.

Elevation-related data are also extremely important when using RTK. With RTK, attention tends to focus on horizontal position, but on-site vertical consistency often becomes an issue. For earthworks, drainage, longitudinal road profiles, slope management, and equipment installation, even if the horizontal position is correct, the results cannot be used if the elevation is off. What is needed here is the concept of elevation datums and conversions. By understanding how heights obtained with RTK are handled and converting them into the required vertical reference system, it becomes easier to coordinate with drawings and existing deliverables.

Also, a viewing environment such as the Geospatial Information Authority of Japan’s maps is useful for preliminary site reconnaissance. By roughly confirming the terrain around the site, road configurations, locations of existing features, and elevation trends, it becomes easier to plan observation schedules, travel routes, and the order of control point checks. Of course, it is important to position the map viewer as an aid for preliminary surveys and on-site explanations, rather than using the screen view itself as the final deliverable.

In practical terms, the basic approach is: use electronic reference points and control point results when you want to verify benchmarks; use Fundamental Geospatial Data when you want to overlay background features; use elevation-related data when considering consistency of heights and terrain; and use viewing-type maps for preparation and checking the overall picture. With this organization, coordinates obtained by RTK become easier to handle not as mere point clouds but as information usable for operational purposes.

In short, Geospatial Information Authority of Japan data is not a one-size-fits-all dataset. It is divided into types that provide reference, that provide background, that assist with handling elevation, and that aid preliminary assessment. To leverage RTK accuracy, it is essential to clarify the purpose for which points are being acquired and to select representative data that matches that purpose.

Point 3: Do not be vague about the handling of elevation and coordinate systems

The handling of elevation and coordinate systems is the aspect most likely to cause trouble in RTK operations. On site, people tend to feel reassured when the horizontal positions look plausible, but many of the problems that occur later when overlaying data on drawings or existing datasets actually originate in this area. Even when using Geospatial Information Authority of Japan data, you must avoid using elevation and coordinate systems ambiguously.

First, about coordinate systems. When handling public location information within Japan, it is necessary to understand the handling of coordinates based on the World Geodetic System and the divisions of the plane rectangular coordinate system. What often occurs on site is that the settings on the surveying instruments, the settings in the design data, and the settings for the background map differ subtly. For example, even at the same site, if the plane rectangular coordinate system's zone number differs, the coordinate values themselves change significantly. This is not merely an error of several centimeters (a few in); the data may not overlap at all.

This issue can be difficult to notice when data are first loaded into software. Even if things appear roughly aligned on the screen, when you zoom in it may appear as mismatched geometry, failure to sit on known points, or slight discrepancies in distances. Especially on sites where contract drawings, past deliverables, construction-management data, and GIS data are provided by different people, relying on verbal agreement to confirm the coordinate system is risky. For each dataset, explicitly verify which coordinate reference it was created to, and standardize the import and export settings.

Next is elevation. In RTK there is a difference between observed heights and the heights required as deliverables. On site, people often assume that any obtained height can be used, but if the definition of the required height in design documents, as-built control, existing survey results, and maintenance ledgers does not match, you cannot compare or verify them. Especially for tasks where height directly affects quality—such as drainage gradients, pavement elevations, curb heights, and equipment installation heights—if you do not decide in advance how to handle elevation, you can end up in the troublesome situation where the horizontal positions agree but only the elevations do not.

A common mistake on site is to treat the height displayed on the rover as the elevation without modification. You should first confirm what height is required for the deliverables and carry out any necessary conversions and unification of reference systems for that purpose. In particular, you must always verify whether the height shown on the design drawings, the height recorded in existing control point results, and the height obtained from RTK observations have the same meaning. If you neglect this verification, things may appear fine on site but will not align at the delivery stage or when coordinating with other trades.

Another thing to be careful about is the interpretation of elevation information included in foundational map data and existing topographic data. Elevation data vary in their usefulness depending on the time of acquisition, resolution, and processing methods. While they are helpful for general terrain understanding and for supporting construction planning, they cannot directly replace on-site construction heights. On sites where the current ground surface is changing, where excavation or embankment work is ongoing, or in urban areas where pavement renewal has been repeated, it is common for past elevation data and present conditions not to match. Therefore, although elevation data provide a useful baseline, they do not justify omitting confirmation of current heights.

The important thing when making use of Geospatial Information Authority of Japan data is to explicitly manage coordinate systems and elevations as separate items. You need to sort out, before observations, which public coordinate system is used for the horizontal plane, what reference is used for heights, what reference the design values are based on, which realization is being adopted for known points, and with what settings background data should be loaded. Rather than aligning things based only on on-site intuition, it is important to formalize them as data definitions.

Also, extra caution is required at sites that use local coordinates. If operations are run on site-specific reference systems and the transformation relationship to public coordinates is not clear, it will be difficult to integrate external data. What works within the site may not be reusable in a different work section or during future operation and maintenance phases. Even when there are reasons to adopt local coordinates, you should decide in advance to what extent you will preserve the relationship with public coordinates, whether you will retain transformation parameters, and how you will establish verification points.

In the end, the key to preventing failures when using Geospatial Information Authority of Japan (GSI) data with RTK is consistency of definitions rather than how the numbers look. If the coordinate system and elevation are aligned, subsequent steps—drafting, integration with point clouds, GIS management, re-observation on different days, and sharing with other trades—will proceed smoothly. Conversely, if this is ambiguous, no matter how much you shorten observation time, re-measurements and reprocessing will occur and the efficiency gains will be lost.

Point 4 Decide on operational judgments and confirmation items on-site in advance

The final point is to decide in advance what to check on site and where decisions will be made. Simply knowing the data is not enough to make effective use of RTK and the Geospatial Information Authority of Japan (GSI) data. In practice, field conditions, communication environment, deliverable requirements, surrounding features, working time, and the operator’s level of proficiency all interact, so you need to determine ahead of time when RTK should take the lead and when to combine it with supplementary methods.

First, what you should confirm is the standards required for the deliverables. The required accuracy and criteria change depending on what the points collected on site will be used for. For simple position records or updates to an asset register, an operation that emphasizes consistency with the background map may be sufficient. On the other hand, for as-built management, boundary-related matters, checks against construction standards, or referencing point clouds, it is necessary to strictly align even the handling of public coordinates and elevations. If you confirm the deliverable standards at the outset, you can avoid performing unnecessarily strict observations that waste effort and prevent later problems caused by insufficient accuracy.

Second, check whether there are any known points or check points near the site. No matter how convenient RTK is, without any verification points it becomes difficult to detect day-to-day stability issues or identify anomalies. If possible, before starting work you should review the nearby reference point results and determine whether there are any usable points. Once on site, verify a known point under the same equipment settings you will use that day and check whether the observations are reasonable. Taking this simple step alone makes it much easier to detect communication failures, configuration errors, or coordinate system mix-ups early.

Third, determine whether the site conditions are suitable for RTK. Check whether the sky is open, whether there are not many overhead obstructions, whether there are not many locations beneath elevated structures or trees, whether reflections from nearby structures are not strong, and whether communications are not prone to instability. Data from the Geospatial Information Authority of Japan are very useful as a reference or background, but they do not improve the reception environment at the site itself. In other words, even if the reference is correct, if positioning conditions are poor the results will be unstable. The important thing is not to force a solution using RTK alone. Depending on the location, you may need to choose to combine it with other methods such as total station surveying, leveling, or approaches that include post-processing.

Fourth, decide how far to rely on base map information and existing data for on-site judgments. Background data are extremely useful, but they should be used on the premise that there may be differences from actual conditions. For example, displaying road edges and the exterior outlines of structures as background can help you efficiently organize points, but those alignments do not necessarily match the latest on-site conditions. Therefore, it is important to clearly define the division of roles: background data provide positional context, and verification of current conditions is supplemented by on-site observations. This allows you to take advantage of the convenience while avoiding overconfidence.

Fifth, decide how to verify elevations. On sites where height is critical, simply increasing the number of observation points is not enough. Before starting work, you need to decide which points will be used for daily height checks, whether to compare them with known points, at what stage to reconcile them with design values, and which height definition to use when exporting deliverables. Handling elevations is more likely to become a problem later than horizontal measurements, so formalizing the rules early is a practical tip.

Sixth, it is also important to keep operational records. When using RTK in the field, you can easily record the point data itself, but operational details such as which correction settings were used, which coordinate system the data were acquired in, which known points were used for verification, and how elevations were handled tend to be omitted. However, it is precisely that operational information that is needed for future reuse and for verification in case of problems. By concisely recording not only the list of observed points but also the setup conditions and verification results, re-surveys and handovers become much easier.

Seventh, it is important not to let the criteria for on-site decisions vary from person to person. If one person uses background data like a baseline while another views it only as a reference display, results will not be consistent even when using the same equipment. By standardizing within the company and on-site teams the methods for confirming control points, the methods for checking coordinate systems, how background data is used, the handling of elevations, and the conditions for re-observation, the effectiveness of using RTK and Geospatial Information Authority of Japan data will be stabilized.

Although the list of on-site checks may look long, in practice they can be organized by deciding the order. First confirm the deliverable criteria, then identify nearby known points, next assess the on-site reception conditions, decide how to use background data, and finally finalize elevation and recording methods. If this workflow is in place, it becomes easier to integrate Geospatial Information Authority of Japan data into practical work without compromising RTK speed.

Summary

Things to know about using Geospatial Information Authority of Japan data with RTK can be organized into four main points. First, understand the relationship that RTK is a technique for determining positions, and Geospatial Information Authority of Japan data is the foundation for correctly placing those positions on official reference frames. Second, use electronic reference points, reference point results, fundamental map information, elevation-related data, and so on according to your purpose. Third, do not be vague about handling elevation and coordinate systems; align the definitions of the plane and the height. Fourth, on site, decide your judgment criteria in advance, including standards for results, check points, reception conditions, the role of background data, elevation verification, and operational records.

RTK is a powerful means to speed up field work and make high-precision positional information easy to handle. However, what truly benefits operations is not that something was measured, but that the measurement results can be connected to design, drawings, ledgers, GIS, maintenance, and future work. Data from the Geospatial Information Authority of Japan plays the bridging role. By anchoring control with electronic reference points, providing positional context with Fundamental Geospatial Data, correctly handling elevations and coordinate systems, and embedding on-site verification items into operations, RTK data becomes not just observation points but reusable operational data.

If you want to leverage RTK on-site from now on, it's important to design not only the operation of the equipment but also which data from the Geospatial Information Authority of Japan to use and for what purpose. Simply adopting that perspective reduces rework after observations and greatly increases the reliability of the results.