Creating Clean Alignments: RTK Field Code Organization Techniques

• Introduction

• Main Discussion - The Need to Organize Field Codes - How to Establish Concrete Rules - Standardizing the Code System - Measures to Reduce Input Errors - Relationship with Cloud Integration

• Applications - Organization Techniques Useful in the Field - Implementation Examples - Troubleshooting

• Conclusion

• LRTK Product Introduction

• FAQ

Introduction

RTK surveying (Real-Time Kinematic surveying) is a method that corrects satellite positioning errors to obtain centimeter-level high-precision positions in real time. Because of that high accuracy, it has been widely used on surveying sites in recent years. However, no matter how precisely data are measured, they cannot be fully utilized if the methods for recording and organizing them on site are not appropriate. In particular, the handling of "field codes" assigned to survey points and features is a key point for effective data use.

Field codes are short identification codes assigned to each point obtained during surveying. For example, boundary points might be labeled "BP" (Boundary Point), and road centerlines "CL" (Center Line); using letters or numbers makes it immediately clear what a measured point represents. By organizing and operating these codes uniformly, subsequent data processing and drawing creation can be dramatically streamlined. Conversely, if each site uses different, inconsistent codes, even RTK survey data will become time-consuming to organize, reducing the expected productivity gains.

This article explains in detail tips for organizing field codes for beginner to intermediate survey technicians engaged in RTK surveying. Starting with the necessity of organizing field codes, it covers how to create concrete rules, standardize the code system, reduce input errors, and even integrate with cloud services, providing practical knowledge and know-how for the field. Mastering field code organization techniques will help you make the most of high-precision RTK survey data.

Main Discussion

Now we will look in detail at the points you should keep in mind when organizing field codes.

The Need to Organize Field Codes

Even if RTK surveying provides high-precision position information, it is meaningless unless it is clear what that information represents. The primary purpose of organizing field codes is to clearly define the role and attributes of each survey point and to classify and manage data in an easy-to-understand way. For example, even if two items are both “points,” how they are treated later differs depending on whether a point is a building corner or the location of a road sign. If unified codes are assigned on site, when you review coordinate data back at the office you can immediately determine what each point represents.

Organizing field codes also directly improves data processing efficiency. Surveying software and CAD often have "field-to-finish" functions that automatically place symbols on drawings based on specified codes or connect consecutive points with lines. If codes are well organized and standardized on site, you can fully use these automatic drafting functions and greatly reduce manual drawing corrections. If codes are inconsistent, the software may not recognize them correctly and manual editing will increase.

Furthermore, code organization is important when multiple people work as a team. If each surveyor uses their own abbreviations, duplication or misunderstandings can occur when data are merged. By establishing field codes as a common “language,” information sharing within the team becomes smoother and miscommunication can be prevented. In this way, organizing field codes improves the quality of surveying results in a dimension separate from accuracy and is a key to improving work efficiency.

How to Establish Concrete Rules

Let’s consider how to actually create rules for organizing field codes. The first step is to design a code system that is easy for everyone to understand. Below are some points to consider when setting rules.

• Code names should be intuitive: Field codes should, as much as possible, be easy to associate with the on-site object. For example, use “CURB” for curbstones or “UTLP” (Utility Pole) for utility poles; basing codes on English words or common abbreviations makes them easier to remember. Codes using the Romanized initials of Japanese words (e.g., “SK = sokkō” for side ditch) can also be effective.

• Uniform length and format: Standardize the number of characters in codes according to the project. If codes are too long, input becomes tedious; if too short, the risk of duplication increases. Generally, 2–4 characters is manageable. Also define rules for uppercase/lowercase usage (for example, standardize on all uppercase).

• Categorization and use of prefixes: Group the code system by type of object. For instance, codes related to roads could begin with “RD,” and boundary-related ones with “B.” Deciding on prefixes makes it possible to identify the general category just by looking at the code.

• Use of numbers: When many objects of the same type appear, append numbers to codes to distinguish them (e.g., “TP1,” “TP2” for tree positions 1 and 2). To represent consecutive points, you can append suffixes like “-1” and “-2” for start and end points. However, ensure that the numbering method is standardized among all members.

• Handling special characters: Hyphens, underscores, and other symbols may be restricted by the devices or post-processing software you use. Confirm whether these characters are allowed when setting rules, and avoid them or substitute other notation if necessary.

Once rules are set, formalize them as a document (a code book) and share it with the entire team. Distribute it and ensure thorough awareness before a new project begins so that codes can be chosen on site without hesitation. Allocate time for rule formulation and training to eliminate situations where staff wonder, “Which code should I use in this case?”

Standardizing the Code System

After establishing rules for field codes, it is important to standardize the code system within your organization. If different codes are used for each project, staff must relearn rules each time and it becomes inefficient; past data assets are also harder to reuse. Having a unified internal code system enables consistent recording and organization across sites, making personnel transfers and new employee training smoother.

When standardizing, existing industry standards and specifications can be referenced. For example, Japan’s public surveying has a “numerical map data acquisition classification code” system for feature classification. However, because these are number-centered and hard to memorize on site, it may be practical to use your company rules in the field and convert to the standard codes at delivery time. The important point is to establish a consistent code system within the company or department. Once a standard is decided, avoid changing it lightly so that accumulated data and know-how can continue to be utilized.

Standardization also helps when working jointly with subcontractors or other teams. If you agree upon and share the code system in advance, data reconciliation and integration across different companies will be smoother. A standardized code system functions as a common language and supports collaboration across organizations and projects.

Periodic review is indispensable when advancing standardization. You may need to extend the code system to accommodate new feature types or situations. When doing so, update the code list while considering compatibility with existing data. Implement version control and ensure the team always uses the latest code table.

Measures to Reduce Input Errors

No matter how good the code system is, it’s wasted if codes are entered incorrectly on site. Here are measures to minimize field code input errors.

• Use device support features: Modern GNSS receivers and surveying tablets/apps often allow selection from a pre-registered code list. Choosing from a menu prevents typos, and features that display recently used codes reduce input effort.

• Avoid ambiguous abbreviations: Similar-looking field codes make input errors hard to notice. For example, try to avoid confusing pairs like “ST” for station and “SL” for station line. If similar abbreviations are inevitable, differentiate them with numbers or alternate characters.

• Enforce input rules: Some devices distinguish full-width vs. half-width numerals or uppercase vs. lowercase letters. Instill the habit of entering codes exactly as specified. For example, if “BP” is the standard, treat “bp” as nonstandard and require consistent use of “BP.”

• On-site double checks: If possible, use a two-person system where the surveyor reads the code and a recorder confirms it in a call-and-response method to prevent human error. If working alone, make a habit of reconfirming the code on the screen for each point.

• Regular analysis of error patterns: Share patterns of past code errors within the company and consider countermeasures. If it’s found that similarly named codes were frequently misused, either revise the code system or issue warnings. Aiming to learn from errors and continuously refine the system is important.

By applying these measures consistently, field code input errors can be steadily reduced. Fewer input errors mean less data cleaning and the ability to obtain RTK surveying results without compromising immediacy or efficiency.

Relationship with Cloud Integration

Field code organization pairs well with cloud services. Recently, many surveying data sets are managed and shared in the cloud, and data consistency is the key there. If codes are unified and organized, it is easier to maintain data integrity in the cloud.

Specifically, when RTK survey data collected on site are uploaded to the cloud, office staff can check contents immediately. If field codes are clear, people working remotely can correctly understand what each point represents. When sharing progress in real time via the cloud, a prerequisite is that the code system is shared by the entire team.

You can also store and distribute the code system itself in the cloud. For example, place a project-specific code dictionary in the cloud and have each member’s device (GNSS receiver or smartphone app) automatically sync the latest dictionary at startup. This reduces the risk of someone referencing an old code list.

Cloud integration also facilitates data reuse. Survey data with organized codes can be handed directly to the design department or GIS systems via the cloud. Designers can interpret features based on codes and immediately reflect them in designs, and unified codes make feature classification easier when analyzing accumulated data with machine learning.

In short, consider field code organization and cloud usage as a set. To achieve smooth data circulation between the field, cloud, and office, it is important to organize codes and share them among everyone.

Applications

With the basic concepts covered, here are practical application techniques, case examples, and remedies for potential problems.

Organization Techniques Useful in the Field

Below are convenient techniques to know when putting field code organization into practice on site.

• Carry a code list: Even experienced surveyors may encounter unexpected codes on a new site. Save the latest code list as a PDF on your smartphone or tablet, or print it on a small card to carry for quick reference.

• Make codes easy to remember: If memorizing codes is burdensome, use mnemonics or associations. For example, associate “EB” with “Elevated Bridge” so the meaning sticks. When training new staff, sharing such memorization tips along with the code table is effective.

• Customize input devices: When using smartphones or tablets for surveying, tweaking the software keyboard settings can improve input efficiency. For example, create a custom keyboard with frequently used letters or register codes in the user dictionary to reduce typos and speed up input.

• Link photos to codes: Take photos near survey points and record the point’s field code in the filename or notes. Later, when cross-referencing photos with survey data, the code serves as a clue and helps identify features. Combining visual information with code data increases record reliability.

• Regular review and update: After a site is completed, review the list of codes actually used. You’ll see “unused codes” and “newly needed codes.” Remove unused items and add necessary ones—evolving the code system to match field realities is important.

Using these techniques improves the practical application of field code operations. Small daily improvements accumulate to significantly enhance the reliability and usability of survey data.

Implementation Examples

Here is an example of a field where field code organization was implemented. In a mid-sized surveying company, each team used its own abbreviations, so data had to be translated each time they were consolidated. The company formed an internal project team to create a unified code system and share it via the cloud.

They first listed the main objects used in daily work and, with input from both veterans and younger staff, assigned codes. Experienced staff proposed necessary and sufficient classifications, while IT-savvy younger members built a cloud-based management system for the codes. The resulting code system was distributed to all employees and integrated into a new surveying system that linked smartphones with GNSS receivers. On site, staff could select codes from the surveying app, enabling even new employees to assign codes accurately without hesitation.

As a result, office-side data cleaning was greatly reduced. Previously, matching each team’s codes took hours; after unification, drawings could be produced with almost no checks. Cloud sharing also allowed real-time progress monitoring, reducing communication loss between field and office. This case demonstrates that introducing field code organization directly improved productivity and reduced human error.

Troubleshooting

Common problems in field code operations and their solutions are summarized below.

• Problem: Codes were forgotten during surveying, leaving several points “uncoded.” Solution: Immediately check data after returning to the office and determine correct codes for uncoded points through team discussion. Photos and notes often make identification possible. As a preventive measure, create a routine to check that all points have codes before finishing work on site.

• Problem: Similar codes were mistakenly used interchangeably, resulting in the same feature being recorded under different codes. Solution: If discovered during data integration, perform recovery processing to standardize to one code. For example, if “PL” and “POL” are mixed, choose one and correct the data. To prevent recurrence, remove confusing combinations from the code system and revise abbreviations.

• Problem: A new feature was encountered and a temporary code was created on site, which later turned out not to be an official code. Solution: In unknown cases, avoid deciding a permanent code on the spot; instead assign a provisional code (e.g., “TEMP”) and leave a note. After returning to the office, determine the official code with stakeholders, correct the data, and add the code to the system. It’s important as a rule not to increase codes arbitrarily by on-site judgment.

• Problem: The software in use did not correctly interpret some code notations, and part of the data did not appear on drawings. Solution: Spaces or non-ASCII characters (such as Japanese characters) in codes can be the cause. Check the software specifications and change problematic characters. Existing data can often be corrected with bulk-replace functions. Consider optimizing codes to suit the software if necessary.

• Problem: Due to cloud synchronization issues, some members’ devices retained an old code list and they entered data using outdated codes. Solution: Check cloud sharing settings and device sync status to ensure the latest code list is always distributed. For data recorded with old codes, prepare a mapping table to convert to the new codes and correct the records. Make it a rule to update all devices to the latest state at the initial stage to prevent recurrence.

Although troubles cannot be completely avoided, knowing these countermeasures and preventive steps minimizes damage. The important thing is to learn from problems that occur and share the insights organization-wide so the same mistakes are not repeated.

Conclusion

We covered RTK field code organization techniques from introduction to application. Although surveying is often perceived as accuracy-first, in practice how data are organized and utilized determines site efficiency and the quality of deliverables. By properly organizing field codes, survey data transform from mere collections of points into meaningful information that demonstrates value in downstream processes.

Creating and enforcing rules and awareness may take effort at first. However, once a system is established, its benefits persist long-term. It becomes a tool to pass veteran knowledge to younger staff and increases compatibility with new technologies (cloud and smartphone surveying). Truly, “cutting-edge technology × thorough basics” will together support future efficiency improvements in surveying work.

Field code organization is an improvement anyone, even beginners, can start today. Small reviews add up to major efficiency gains. Please consider adopting these techniques on your site to maximize the benefits of RTK surveying.

LRTK Product Introduction

Finally, we introduce LRTK, a product attracting attention as an innovative tool that significantly lowers the barrier to RTK surveying. LRTK (El-Ar-Tee-Kay) is a compact device that enables centimeter-accuracy RTK surveying using just an iPhone. Designed as a smartphone-integrated simple surveying terminal, it allows people without specialized GNSS receivers to perform high-precision positioning easily.

The LRTK device is compact enough to fit in a pocket and is attached to an iPhone via a dedicated case or attachment. The weight is approximately 125 g, and the thickness is about 1.3 cm (0.5 in), so it does not add bulk to the phone. It connects wirelessly via Bluetooth, eliminating cumbersome cable routing. Although integrated, the device can be operated separated from the phone during surveying—for example, attaching the LRTK to a pole or tripod while operating it from an iPhone via Bluetooth—offering flexible usage.

Regarding positioning performance, LRTK supports multi-GNSS and multi-frequency reception, receiving signals not only from GPS but also from GLONASS, Galileo, and Michibiki (QZSS) simultaneously. This greatly improves error mitigation and positioning stability compared to traditional single-frequency GNSS. LRTK also supports Michibiki’s “centimeter-level augmentation service (CLAS)” in Japan, enabling high precision based on satellite correction information even in mountainous areas without network coverage. When network connectivity is available, you can use network RTK (Ntrip service) to obtain correction data from the nationwide reference station network.

In other words, with LRTK you can achieve centimeter-level positioning immediately even at sites without a base station. Users familiar with iPhone operation can handle it easily through a simple UI provided by a dedicated app, allowing surveying to begin without complex settings. Compared to traditional expensive, bulky surveying equipment, LRTK lowers barriers to introduction and transport, making it a solution well-suited to sites seeking labor reduction and efficiency. Combined with field code organization techniques, data obtained with LRTK can be shared to the cloud immediately and results can be confirmed and utilized in real time.

Although smartphone-integrated RTK is a new technology, its combination of reliable accuracy and usability is expected to make it one of the surveying standards in the future. From beginners to experts, LRTK—achieving high-precision surveying anywhere— is a product worth watching alongside field code organization techniques.

FAQ

Q: What is a field code? A: A field code is a short identification code attached to each point or feature obtained in surveying. For example, assigning the code “BM” (Building Corner) to a point set at the corner of a building makes it easy to understand what that point represents. Using codes lets you identify point types at a glance on drawings or data lists, streamlining post-processing and analysis.

Q: How should I start organizing field codes? A: First, list the current point names and abbreviations you use and organize duplicates and unclear entries. Next, create a common code system within the team. The key is to make rules that are easy for everyone to understand. Document the resulting code list, distribute it, and ensure everyone records on-site data according to it. Start with a small site as a trial and gradually expand company-wide while adjusting rules as needed.

Q: Should I use industry-standard code systems? A: It is not necessary to strictly conform to industry standards. Ideally, have a company-specific standard customized for on-site usability. However, if you need to comply with public delivery standards (such as those of the Geospatial Information Authority of Japan), design your system so it can be mapped to the required classification codes at delivery. In other words, use easy-to-remember codes on site while enabling conversion to official classification codes for submission.

Q: What happens if a code is entered incorrectly or forgotten on site? A: Minor input errors can generally be corrected in post-processing after returning to the office. For example, you can perform bulk replacement of incorrect codes or fill in missing codes. However, if you forget on site, it may be difficult to recall accurately later, so entering codes correctly on the spot is important. If you notice a mistake, leave a note or record it in a backup, then correct it later. Taking photos for later verification also helps.

Q: Do I need special equipment or services to use the LRTK device? A: LRTK basically works with an iPhone and the device itself. In Japan, receiving QZSS (Michibiki) CLAS signals allows single-unit high-precision positioning even without a base station. If internet access is available, using Ntrip services (to receive correction information from existing reference station networks) provides more stable positioning. In short, you can start RTK surveying with just an iPhone and LRTK without installing your own dedicated base station. Survey poles and mounting accessories make operations easier but are not strictly required.