Precautions and Best Practices to Avoid Failure When Implementing RTK Overseas

Introduction

RTK (Real Time Kinematic) surveying technology achieves centimeter-level accuracy (half-inch accuracy) by correcting satellite positioning (GNSS) errors in real time. It is used across many fields, from construction and civil engineering to mapping, but implementing RTK overseas presents many challenges different from those at home. Differences in local communication infrastructure, discrepancies in geodetic datums, insufficient checks on regulations, equipment failures, and the technical proficiency of local personnel can all lead to unexpected failures if not handled carefully.

This article explains, in detail, the common failure patterns when introducing RTK overseas and the preventive measures (best practices) for those starting RTK operations abroad or for practitioners and technical managers who have struggled with overseas surveying in the past. We cover typical failure cases such as base-station coordinate input errors, forgetting to convert to the local geodetic system, FIX instability due to communication problems, overlooking local radio and surveying laws, insufficient training for local staff, inadequate cloud integration, and data inconsistencies in multinational projects. For each item, we describe the background that makes the failure likely and the countermeasures or avoidance strategies to take in advance.

Implementing RTK overseas is by no means easy, but risk can be greatly reduced with proper preparation and measures. Let’s go through the specific precautions and best practices.

1. Base Station Coordinate Setting Errors – Insufficient Verification of Local Control Points

Failure example: The foundation of RTK surveying is placing the base station at an accurately known coordinate, but this basic mistake often occurs on unfamiliar foreign soil. For example, entering one digit incorrectly when inputting base station coordinates, mixing up latitude/longitude with planar coordinates, or configuring the system with Japan’s datum without considering the local geodetic system can result in all measured points being shifted by tens of meters (tens of ft). Because observations may appear normal on site, such errors are hard to notice and can later result in panic when the survey does not match maps or design coordinates. Especially abroad, unfamiliarity with local official coordinate systems and control points means extreme care is needed when configuring the base station.

Best practices:

• Before installing the base station, obtain the coordinates of local known points (government control points or existing triangulation points) and use them as the reference whenever possible. Even if you must use an unknown point as the reference, secure sufficient check points so you can transform to the local coordinate system later.

• When entering the base station’s known coordinates, perform thorough double checks. Verify the number of digits, signs, geodetic datum, and coordinate system, and if possible have another operator cross-check. Be careful not to overlook mistakes such as wrong zone numbers.

• After configuration, perform a test survey. Measure known reference points separately to verify there are no mistakes in the base station settings. If discrepancies are found at the test stage, they can be corrected immediately.

• Don’t leave these steps to local workers alone; prepare standardized procedures and a setup checklist. Template the input procedure and cautions for control point coordinates so consistent quality is maintained regardless of who performs the setup.

2. Forgetting to Convert to the Local Geodetic System – Data Shifts and Discrepancies

Failure example: Many countries use geodetic datums different from Japan, and forgetting to convert can cause survey results to not match local maps or drawings. For instance, delivering GNSS coordinates obtained in WGS84 (World Geodetic System) without converting them to the local national coordinate system has produced position errors of tens of meters or more (tens of ft or more). Some countries handle east/west longitudes differently or use different projection zone divisions (e.g., UTM zones), so simple conversion mistakes can occur. In overseas projects, this kind of omission of coordinate transformation often leads to widespread data discrepancies.

Best practices:

• At project start, always investigate the official geodetic systems (horizontal and vertical) used locally. Identify the datum adopted by each country (e.g., NAD83, ETRS89) and coordinate systems (e.g., UTM zones or national planar grids), and establish a unified standard for the project.

• Configure GNSS receivers and surveying software, if possible, to output directly in the local geodetic system. If using local correction services (network RTK, etc.), confirm that the provided coordinate system matches the project requirements.

• If data observed in WGS84 or another system must be converted later, use official transformation parameters or software provided by the national geodetic authority to perform accuracy-guaranteed coordinate transformations. Avoid manual calculations or guesswork; use automated tools to prevent human error.

• After conversion, cross-check the coordinates against local known points or official maps to ensure they align correctly with the local system. Performing this verification prevents fatal mistakes where results later fail to match drawings.

3. Fix Instability Due to Communication Problems – Loss of Correction Signals

Failure example: RTK’s high-precision positioning depends on receiving correction information from the base station in real time. However, in overseas fields, differences and instability in communication environments can cause frequent interruptions in correction data. For example, using mobile data for NTRIP where local signal coverage is weak can lead to frequent communication losses, preventing the rover from maintaining FIX and causing it to fall back to float or single positioning, degrading accuracy. Other reports cite cases where radio modems could not transmit adequate power due to country-specific frequency regulations, reducing communication range to the base station. Communication interruptions or latency directly destabilize RTK accuracy and cannot be ignored.

Best practices:

• Conduct research into the communication environment at the survey site beforehand. Check local cellular network coverage and Wi‑Fi availability, and prepare local carrier SIM cards or pocket Wi‑Fi devices as needed. Using dual-SIM-capable devices that can switch between carriers is also effective.

• In remote areas where cellular infrastructure is unreliable, consider alternatives such as local radio transmission for corrections. Extend communication range with relay stations or high-gain antennas and ensure line-of-sight to the base station. If necessary, carry a satellite communication terminal to exchange minimal data with headquarters for peace of mind.

• During surveying, continuously monitor RTK solution status. Frequently check the FIX/FLOAT indicators on controllers and receivers, and do not push observations when FIX is not obtained. Pause temporarily and prioritize restoring a stable FIX by changing antenna location, rebooting communication equipment, or moving closer to the base station.

• Also consider operations that don’t insist on real time. If communications cannot be guaranteed, switch from RTK to PPP (Precise Point Positioning) or PPK (Post-Processed Kinematic) as needed. Record raw rover data on site and combine it later with base-station data in post-processing to refine measurements while keeping field work to provisional surveying.

4. Risk of Violating Regulations – Ignorance Is No Excuse

Failure example: One often-overlooked issue is national regulations. Surveying equipment and communication methods that are fine in Japan may be illegal overseas. For example, bringing a high-power UHF radio for base-rover communication into a certain country was found to use a frequency band banned by local law, exposing the team to the risk of equipment confiscation or fines. Some countries require authorization for surveying activities; map production or infrastructure surveys may be treated as state secrets, and foreign companies conducting surveys without permission may face penalties. Ignorance of the law is not an acceptable excuse, so pre-project investigation is essential.

Best practices:

• Before exporting surveying equipment, check local radio laws and communication regulations. Verify whether the planned radio devices are approved for use locally (e.g., whether they have FCC or CE markings) and whether their frequency and transmission power are within allowed ranges. If necessary, consider renting equipment certified for the local market or models that support permitted frequencies.

• Investigate the legal requirements for conducting surveys locally. Determine whether surveyor certification or prior notification to authorities is required, and whether there are restrictions on foreign companies or foreign technicians carrying out surveys. Confirm these points through the project owner or local partners. In some cases, it may be necessary to formally partner with a local surveying firm and operate under their name.

• Be careful with the handling of survey data and geospatial information. Some countries restrict the export or public release of high-accuracy positioning data. When transferring coordinate data to the home country via the cloud, comply with data confidentiality policies. If data are regulated, apply appropriate measures such as encryption or anonymization.

• To implement the above measures, collaborate with local experts or legal advisors. Use local partners or consultants familiar with regional rules to obtain up-to-date legal information and reflect it in the project plan.

5. Insufficient Training for Local Personnel – Skill Gaps among Local Staff

Failure example: Many overseas projects assign surveying tasks to locally hired staff or subcontractors. However, handing advanced RTK equipment to personnel without adequate training can lead to repeated mistakes. Examples include always observing with the pole tilted because they didn’t know to hold it vertical, entering wrong antenna heights causing vertical offsets, neglecting to monitor satellite tracking or FIX status and recording unreliable data. Even if local staff have no malicious intent, operator errors due to inadequate training can degrade project quality and require rework.

Best practices:

• At project start, provide an intensive training period for local staff. Teach RTK fundamentals, equipment operation, and key cautions comprehensively, and reinforce understanding with hands-on exercises using real equipment. If language barriers exist, use interpreters or distribute manuals translated into the local language.

• Prepare practical checklists that document the items to verify for each observation. For example: “Have you confirmed the base station coordinates?”, “Have you checked pole verticality with the bubble level?”, “Have you correctly set antenna height/prism height?”, “Is the FIX solution being maintained?” Making it standard practice to consult the checklist for every task helps prevent human error.

• In the initial phase, ensure an experienced engineer directly supports the local team. Attend the first several surveys to instruct on-site, and continue to review data regularly to provide feedback. For remote locations, set up a system to answer questions via online meetings or phone so field concerns are resolved promptly.

• Training should not be a one-off; provide continuous follow-up. Share new issues with the staff as they arise and teach solutions to improve team skills over time. Cultivate excellent local staff as leaders who can train others, thereby reducing future training burdens.

6. Cloud Integration Failures – Pitfalls in Data Sharing and Backup

Failure example: Increasingly, survey data are centrally managed in the cloud for real-time sharing between field and headquarters. However, overseas network issues or service unavailability in certain regions can cause delays in cloud data synchronization. For example, uploading a day’s observation data to the cloud on site might be so slow that it takes all night, forcing physical delivery by USB stick. There are also cases where teams used different data formats, causing chaos when attempting to integrate data in the cloud. When cloud-dependent workflows fail, data loss or mismatches of current information can impede project progress.

Best practices:

• Standardize the data management workflow: before the project begins, define what data are uploaded to the cloud, when, and by whom, and who will view and use them. Unify file formats and naming conventions so field and headquarters teams do not get out of sync. For example, set rules such as uploading daily point CSVs and performing weekly integration checks.

• Prepare offline contingencies: be flexible about immediate cloud synchronization depending on site connectivity. In regions with poor networks, first store data on a laptop or local server and sync in bulk when a good connection is available. Secure physical delivery methods to headquarters as a last resort and ensure multiple backup paths for reliable data retrieval.

• Choose a cloud platform after confirming it supports access from abroad. Some countries block or throttle specific cloud services, so consider using a CDN or a server in a local region where appropriate. For security, implement VPN access and multi-factor authentication to enable safe and reliable data sharing.

• Regularly perform data integrity checks on cloud-collected data. Verify that datasets from different teams do not mix coordinate systems or contain duplicates, and check for file corruption or missing data. Ideally appoint a dedicated data coordinator, but if that’s not possible, run automated scripts for basic checks to detect problems early.

7. Data Consistency Errors in Multinational Projects – Lack of Unified Coordinate Systems and Units

Failure example: In projects spanning multiple countries or international joint ventures, teams from different nations often bring their own survey data. A common issue is data inconsistency caused by unaligned coordinate systems and units. For example, a Japanese team surveying in JGD2011 and a European team using ETRS89 resulted in several tens of centimeters of discrepancy when their results were merged. For heights, Japan’s team used geoid heights while the European team used ellipsoidal heights, producing obvious vertical mismatches. Mixing imperial and metric systems is another典型的な failure source. When crossing borders, failing to decide on these basics can create major disruptions downstream.

Best practices:

• Establish unified standards for the project’s geodetic reference and unit system. For example: “Standardize horizontal coordinates to WGS84 latitude/longitude and require all countries to convert to WGS84 before delivery”; “Unify heights to a mean sea level reference using a specified geoid model”; “Use meters for all distance units.” Document these in the project charter and technical specifications and ensure all stakeholders are informed.

• If teams must work in local systems, share transformation parameters and procedures for converting to the common coordinate system. Use trusted seven-parameter transformations or other agreed formulas so teams do not perform inconsistent conversions. Discuss any uncertainties within the project and standardize the conversion method.

• Always include metadata that specifies coordinate systems and units when handing over survey data. For example, include labels in folder or file names like “JGD2011_XY_EGM96HT” to indicate horizontal is JGD2011 and vertical is EGM96 geoid height. Clear labeling lets recipients interpret data correctly and avoid miscommunication.

• When integrating final data, perform cross-validation using overlapping sections or common control points. Compare the same points measured by different national teams to confirm differences are within tolerances. If discrepancies exceed acceptable limits, trace back and investigate causes and review each team’s processing steps. Regular reviews like this enable early correction of data consistency problems.

New Options to Simplify Complex RTK Deployment

As described above, implementing and operating RTK overseas requires many precautions, advanced know-how, and careful preparation. On the other hand, addressing these points in advance can prevent accuracy problems and trouble, enabling successful RTK surveying even across countries.

Recently, however, technological advances have produced solutions that reduce this complexity. One example is LRTK, which combines a smartphone with a small high-precision GNSS device to allow anyone to perform centimeter-level accuracy (half-inch accuracy) positioning easily. LRTK is an all-in-one surveying system that attaches a dedicated ultra-compact RTK-GNSS receiver to a smartphone and enables high-precision positioning with one-touch operation via an app.

Using such devices, you can obtain accurate global coordinates on site without the hassle of base station setup or worrying about differences in geodetic systems. Acquired data are automatically saved to the cloud and shared with the office seamlessly. LRTK supports multi-GNSS and multiple frequencies, so stable positioning is expected even in mountainous areas beyond cellular coverage or in overseas regions lacking Internet infrastructure. Because it is intuitive to use, even if many people are not skilled with surveying equipment, the training burden on local staff is greatly reduced.

As a smart solution to the common challenges of overseas RTK deployment, LRTK—an easy surveying device combining a smartphone and a compact GNSS—is very attractive. If you feel that “RTK operations overseas are difficult…”, consider these latest solutions. By leveraging technology, you can make complex RTK surveying simpler and more reliable.