How to Integrate RTK and GIS? 4 Steps for Field Utilization

Table of Contents

• The significance of integrating RTK with GIS

• Common Failures When Integrating RTK and GIS

• Step 1 Decide in advance what it will be used for on-site

• Step 2: Align coordinate systems and acquisition rules and collect position information with RTK

• Step 3 Organize attributes and import into GIS

• Step 4 Embed post-adoption usage and translate it into operational improvements

• Practical considerations for effectively integrating RTK and GIS

• Summary

The significance of integrating RTK with GIS

Linking RTK and GIS is not just about measuring positions with high precision. It is about creating a workflow that turns positional information collected on site into information that can be reviewed later, shared, and used for decision-making. When using only RTK, you can capture points with high precision in the field, but the measured results tend to remain confined to an individual's device or reports. Conversely, when using only GIS, if the accuracy of the underlying positional information or the acquisition procedures are unclear, the data may look tidy on the map yet be difficult to use for practical decision-making.

By linking the two, you can instantly verify coordinates obtained on-site on a map and associate them with equipment, boundaries, inspection points, as-built conditions, abnormal locations, photos, historical records, and so on. As a result, anyone who looks at it will understand the same location in the same way. Measuring, organizing, and utilizing become a single continuous workflow, speeding up on-site decision-making.

For example, on construction sites, if the positions of temporary structures and as-built verification points are captured with RTK and uploaded to a GIS, daily progress management and location management become integrated. In infrastructure management, recording manholes, signs, poles, pipeline-related equipment, and damaged areas with RTK, and managing them in the GIS together with histories and photos, makes it easier to prioritize inspections and repairs. For maintenance management, continuously observing the same locations makes it easier to compare changes. In disaster response, promptly recording the locations of affected areas and reflecting them on shared maps speeds up the initial response.

In other words, integration between RTK and GIS means turning coordinates obtained in the field into operational assets that the organization can use. What’s important is to design it not as a one-off data acquisition, but as an end-to-end workflow—collecting in the field, organizing, sharing, and applying the data for future use.

Common failures when integrating RTK and GIS

Integrating RTK and GIS is convenient, but in practice it's not uncommon for their use to fall short of expectations. In many cases, the reason lies not in the equipment's performance itself but in how the prerequisites are aligned.

The most common issue is a mismatch of coordinate systems. Even when measurements are taken correctly in the field, problems occur such as positions shifting when imported into the GIS, not matching the basemap, or not overlapping with other departments' data. This is a typical example of what happens when the reference used during positioning and the GIS's coordinate settings are not aligned. If field staff focus solely on collecting numbers and are not aware of the map reference that will be used later, they can get tripped up here.

Another common problem is insufficient attribute design. Even when locations are captured, the meaning of those points can be unclear. For example, if only point numbers are listed and information such as equipment name, type, inspection date, anomaly classification, photos taken, and person in charge are not included, then even when loaded into a GIS they are nothing more than points on a map. Even if the meaning is clear on site, the data becomes unusable for another person in charge or for yourself when viewed later.

Furthermore, not having decided how the data will be used after import also leads to failure. If putting it into a GIS becomes an end in itself, data may accumulate without changing on-site decision-making. If it’s unclear whether the data will be used for search, inspection planning, progress management, photo organization, or reporting, the value of integration becomes hard to see.

Another aspect that is often overlooked is the lack of focus on operational improvement. Even if you work hard to organize things at the initial rollout, after a few months input rules can break down, attribute names become inconsistent, different notations for the same equipment get mixed in, and update dates may stop being recorded. In that situation, merely having a map does not amount to an information platform you can reliably use in everyday operations.

Therefore, it is important that RTK and GIS integration does not treat positioning tasks and mapping tasks as separate. When the workflow—from field acquisition to operational improvement—is organized as a single, continuous system, the integration will become firmly established.

Step 1 Decide in advance how it will be used on-site

The first step to successfully integrating RTK and GIS is to clarify what will be used and in which situations. If you start measuring while this remains unclear, you may collect coordinates that are of little practical use.

The first thing to consider is the final use case. For example, whether you want to view the equipment register on a map, speed up searches for inspection points, visualize construction progress, or make revisits to abnormal locations easier will change what information you need to collect. If the purpose is equipment management, equipment numbers, types, managers, installation years, and inspection histories are important. For construction management, you will need work dates, work types, progress status, construction crews, photo records, and so on. For disaster response, information such as damage type, level of danger, whether emergency response is required, and whether passage is possible is important.

Next, organize the target objects. You need to decide in advance whether to manage them as points, lines, or polygons. Point data are suitable for objects whose position can be represented by a single point, such as signs or equipment poles. Line data are suitable for objects that have length, such as gutters, lane markings, or conduits. Polygon (area) data are suitable for objects that have extent, such as paved areas, restricted-access zones, or damage regions. If this is left ambiguous, you may collect something as a point in the field but later want to use it as an area, increasing the effort required to reorganize.

Also, clarifying the division of roles—who collects data in the field, who verifies it, who updates the GIS, and who utilizes it—is important. If the same person handles everything in a small-scale operation, it’s simple, but when multiple departments are involved, the perspectives of data entry personnel and users differ. Prioritizing ease of entry alone can cause problems during use. Conversely, adding too many management items increases the data-entry burden in the field and leads to more missed records. Therefore, it becomes easier to operate if you separate the items that must be collected on site from those that can be supplemented in the office.

At this stage, it is also important to have a clear image of the final deliverable. If you first imagine how you want it to appear on the map screen, what conditions you want to use for searches, which information you want to display in a list, and which photos you want to link to, the necessary items will become apparent. In practice, the fewer items you collect on site, the easier it is, but if the minimum information needed for later use is missing, a re-survey will be required. That is why it is important to design by working backwards from the intended use.

Furthermore, the required level of accuracy should be confirmed at this stage. It is not necessary to measure everything to the same accuracy. If the purpose is simply to determine the approximate location of equipment, you may not require strict control-point level accuracy. On the other hand, when deviations directly affect work—such as during recovery operations or when verifying construction positions—more rigorous procedures are needed. Clearly specifying the required accuracy makes it easier to decide on observation time, whether re-surveys are necessary, and how to perform on-site verification.

In short, the important thing in the initial step is not to start by measuring. First, clarify what will be measured, who will do it, to what level of accuracy, and what decisions it will be used for. With this preparation in place, the design of subsequent coordinate systems and acquisition rules will be less likely to waver.

Step 2 Make coordinate systems and acquisition rules consistent and collect position information with RTK

The second step is to acquire positions with RTK after standardizing the coordinate system and acquisition rules. This is the area where the most practical differences tend to arise in the integration of RTK and GIS. No matter how high-precision the equipment, if the handling of coordinates is ambiguous, the data will not be usable in GIS.

The first thing to establish is which coordinate system will be used for management. In GIS, background maps, existing registers, design data, and drawings from other departments are overlaid and used together. Therefore, from the stage of acquiring data with RTK, you must decide in advance which reference will be used for the final overlay. Even if on-site staff consider the numbers sufficient, the GIS side cannot use them unless it is known which reference those numbers are based on. The same applies not only to horizontal positions but also to how elevation is handled. You need to clarify in advance whether you require elevation, whether relative heights will suffice, or whether you will manage them against a different reference surface.

What is important here is to use the same terminology in the field and the office. For example, if terms such as coordinate values, latitude and longitude, plane rectangular coordinates, and elevation are mixed, misunderstandings are likely to arise during data handover. In practice, specifying the format used when recording data at acquisition, the format used for storage, and the format used when importing into a GIS will reduce confusion. On site, it is important not to leave device settings at their defaults but to check the settings for each project.

Next, decide the acquisition rules. Here, standardize not only what to measure but also how to measure it. For example, whether you take the center of the equipment, the edge, the center of the lid, or the base of the support pillar will change the position even for the same object. If different people use different criteria for selecting points, when comparing later you won't know whether it's a change or just a difference in observation position. For lines and surfaces as well, it is necessary to decide the rules for start and end points, how to handle corner points, and how to determine representative points.

Furthermore, the methods for quality checks at the time of acquisition should also be standardized. Deciding on checks for fixed solutions, verification of observation stability, conditions for re-observation, recording of the surrounding environment, the presence or absence of signal obstruction, and the orientation of photographs will make it easier to judge the reliability of the data later. In particular, under trees, beneath elevated structures, and near buildings, positional jumps and instability tend to occur, so it is important to record the conditions during observation. Even if a position looks slightly off when viewed in a GIS, on-site records allow you to trace the cause.

Also, file naming and data organization methods should not be overlooked. Positioning data, photos, and field notes are often stored separately, and it frequently becomes unclear later how they correspond. Simply aligning point numbers, object numbers, photo numbers, and work dates according to a consistent rule can greatly reduce the effort required when importing into a GIS. Standardizing acquisition procedures is particularly important when multiple people are responsible for the same site, because individual habits tend to cause operational inconsistencies.

When collecting data on site, it's important not to add more fields than necessary. In high-precision positioning work, increasing the amount of input work makes operational mistakes and missed records more likely. Therefore, it's easier to operate if you have a system where only the minimum information required is entered on site during position acquisition, and supplementary information is added later. However, information that cannot be supplemented afterwards must be captured on site. Typical examples are identification information indicating what the position refers to and photos showing the site conditions. Having just these two makes downstream verification work considerably easier.

Put simply, at this step it’s not enough to rely solely on RTK accuracy. To make the data usable in a GIS, it is important to standardize the coordinate system, the targets to be captured, observation procedures, quality checks, and naming rules. When these are in place, the subsequent attribute design and GIS import will proceed much more smoothly.

Step 3 Organize attributes and import into GIS

The third step is to prepare the attributes that give meaning to the acquired location information and import them into a GIS. Coordinates obtained by RTK are merely the skeleton of a position. Only when information about the target objects and the site is linked to them do they become geographic information usable in operations.

In attribute design, the first thing to consider is separating required fields from optional ones. If you try to pack all information in from the start, the input burden becomes large and field operations will not continue. Conversely, if there are too few fields, you will not be able to filter or compare data in GIS. Therefore, it is important to first decide the common fields that are always necessary for any data. For example, management number, object type, acquisition date, collector, location certainty, presence of photos, and a memo field are commonly useful across many use cases. On top of that, adding purpose-specific fields—such as for asset management, construction management, or inspections—makes organization easier.

Attribute design also requires measures to prevent input inconsistencies. If the same meaning is written in different ways, filtering in the GIS becomes ineffective. For example, if labels like "abnormal," "needs confirmation," "confirmation required," and "needs action" are mixed, aggregation becomes difficult. For equipment types, mixing abbreviations, official names, and former names breaks consistency. To prevent this, make fields that can be turned into choices as selectable as possible, and limit free-text fields to only those that are truly necessary. Because a GIS is not only a tool for viewing maps but also for conditional searches and aggregation, the consistency of attributes determines usability.

The next important thing is how to link location information with photos, documents, inspection records, and so on. In field work, being able to view site photos and previous records together is far more useful than looking at coordinates alone. For example, even for the same equipment location, if appearance photos, inspection results, repair history, and details of abnormalities are linked, it becomes much easier to prepare before the next site visit. Therefore, when importing into a GIS, you need to ensure that the correspondence with photo file names and record numbers does not get lost.

Data formatting is essential before importing. If you put coordinate files or tabular records from the field directly into a GIS, inconsistencies in column names, garbled characters, blank cells, duplicates, and format mismatches can easily lead to rework. For example, if date formats are mixed or numeric fields contain symbols, later sorting or conditional searches will be hindered. That is why you should establish simple formatting rules before importing and standardize column names, date formats, numeric formats, and the handling of blank cells.

When importing into a GIS, how you separate layers is also important. If you put everything in a single layer, it may look tidy but will become difficult to manage operationally. It is appropriate to manage different types of information separately—such as equipment, abnormal locations, inspection records, and construction progress—and configure them so they can be overlaid as needed. On the other hand, if you divide layers too finely, users can become confused, so it is important to consolidate them into units that are easy to understand from the perspective of field users.

Also, you should always check overlap with the background map. Verify whether the coordinates obtained with RTK appear correctly in the GIS by comparing them with road edges, building locations, existing registers, aerial photographs, and so on. If there is a slight displacement, you need to determine whether it is an error on the background map side, a coordinate transformation issue, or an environmental factor during observation. Simply correcting a position based only on appearance can actually degrade the original accuracy. In practice, it is important to decide which data to treat as the reference and to have a consistent basis for judging apparent discrepancies.

The essence of attribute design is to create a state in which things can be found later, compared, and explained. Putting data into a GIS is not the goal in itself. It is important that anyone can tell where something is, what it is, what condition it is in, when it was acquired, and how it should be handled. To that end, location and attributes must be designed together, and organized to prioritize usability over ease of import.

Step 4 Establish post-adoption usage to drive operational improvements

The fourth step is to solidify how the data will be used after being imported into the GIS and to connect that to ongoing operational improvement. Only once you reach this point does the integration of RTK and GIS become a tangible result in the field. Conversely, if this is weak, the carefully prepared data will end up as a map that goes unviewed.

One of the primary uses after importing is improving location verification and search efficiency. If points and lines captured in the field are organized on a GIS, you can quickly grasp the location of the target and more easily find past collected information. Tasks that relied on paper drawings and individual memory become activities where a shared understanding can be achieved on a map. This is also effective for handing over to new personnel. By visualizing location information that only experienced staff understood, dependence on specific individuals can be reduced.

Another major benefit is speeding up on-site decision-making. If you can filter on a GIS by equipment type, anomaly category, last updated date, presence of photos, and other criteria, you can immediately extract high-priority targets. For example, because you can organize on the map equipment that hasn’t been inspected for a certain period, locations with high anomaly categories, or sites that require revisits, the quality of patrol planning and work instructions improves. When location information is incorporated into the workflow, it becomes a decision-support tool rather than mere recordkeeping.

Furthermore, monitoring changes through comparison is also an important use. If the same location can be viewed over time, it becomes easier to grasp terrain changes, damage expansion, movement of temporary structures, and the progress of as-built conditions. In particular, combining RTK-acquired positions with photos and inspection records allows you to track site changes with positional information. This is highly effective for maintenance management and construction management. Rather than merely retaining previous records, presenting them in a way that shows where and how things have changed makes it easier to decide on next actions.

It also becomes easier to incorporate into reporting materials. GIS is also useful when creating maps for on-site explanations, maps for sharing progress, and overview maps of anomaly locations. When putting these into paper documents or presentation materials, if the coordinates are accurate and the attributes are well organized, the persuasiveness of the explanation increases. Materials with vague locations create discrepancies in understanding among stakeholders, whereas information organized in a GIS tends to serve as a common foundation.

However, to establish sustained use, it is necessary to create a mechanism for updates. Even a map that has been properly organized will quickly become outdated if it is not updated. Therefore, you need to decide when to add new entries, which fields to update when changes occur, and how to handle photo replacements and decommissioning information. In practice, new registrations may be made while decommissions or relocations are not reflected, causing discrepancies between actual conditions and the map. To prevent this, it is important to clarify who is responsible for updates and to keep the update procedures concise.

From an operational improvement perspective, regular reviews are essential. Check whether the attribute fields decided at introduction are too many and becoming a burden on field staff, or conversely whether any necessary fields are missing; whether there are inconsistencies in notation that make searching difficult; and which processes have frequent missed updates. The linkage between RTK and GIS is not something you complete once by creating a perfect setup. It is important to refine it into a form that fits the field through actual use.

For example, at first all items were entered on site, but because the burden was large, it’s common to change to entering only required items on site and having the office complete the rest. Conversely, changing abnormality categories that were initially free-text into selectable options to make aggregation easier is also effective. If photo naming had been inconsistent, simply switching to a naming convention that combines the management number and the shooting order will make downstream processes easier. The accumulation of these small improvements cultivates a system that supports integration.

At this step, the important thing is not to create maps but to change workflows by using them. Only when the acquired location information proves useful for on-site verification, planning, inspections, reporting, handovers, and improvements will the integration of RTK and GIS deliver results.

Practical considerations for effectively integrating RTK and GIS

We have reviewed four steps up to this point, but there are several points to note when operating in practice. First, it is important to strike a balance between high accuracy and ease of use. RTK’s strength is high accuracy, but if you always pursue the highest accuracy at every site, operations can become burdensome due to observation conditions and work time constraints. What is required on site is accuracy that is sufficient for the purpose and procedures that can be maintained. Ensure accuracy firmly in the situations where it is necessary