Prevent Rework: How to Spot Bad RTK Points in Advance

Table of Contents

• What is RTK positioning? Basic mechanism and use cases

• Typical NG examples that cause rework in RTK surveying

• On-site checkpoints to spot “bad RTK points” in advance

• Techniques to identify and correct bad RTK points in the cloud

• Recommended flow for accuracy checks and inspection routines

• Best practices to leverage RTK in the field, design, and maintenance

• Recommendation for simple surveying with LRTK

• FAQ

What is RTK positioning? Basic mechanism and use cases

RTK positioning refers to the GNSS surveying technique called Real Time Kinematic. While standalone GPS positioning can have errors of several meters, RTK uses two receivers—a reference station (base) and a rover (mobile)—and the rover receives error-correction information from the base in real time, canceling out errors to achieve centimeter-level accuracy. A major characteristic is that real-time differential corrections from satellites enable on-the-spot high-precision coordinates.

This high-precision RTK positioning is increasingly used in various civil engineering and surveying situations. For example, in stakeout work, where stakes must be placed exactly at design coordinates, RTK can guide workers to the design coordinate on site and complement conventional total station angle/distance methods. In as-built verification (measuring the geometry and quantity of completed structures), RTK can quickly measure many points to check whether construction matches drawings. RTK positioning is also effective for position guidance during infrastructure inspections: when searching for points identified on drawings for road or bridge inspections, RTK-capable devices can guide inspectors to those points with errors of only a few centimeters. In short, RTK surveying is becoming indispensable in situations that demand instant positioning with centimeter-level accuracy (half-inch accuracy).

Typical NG examples that cause rework in RTK surveying

Although RTK surveying is high-precision, misuse can lead to undetected measurement errors and later rework (re-measurement or redo). Below are typical NG examples that commonly occur on site. By understanding and avoiding these mistakes in advance, you can prevent unnecessary rework.

Saving points before sufficient accuracy is achieved

This happens when survey points are recorded before the RTK receiver has obtained a fixed solution (Fix). RTK achieves centimeter accuracy only once a Fix is obtained, but poor satellite reception or interrupted correction streams can leave the solution in a float state. In Float state, positional errors can be tens of centimeters or more, so saving points in this state locks in large measurement errors. For example, if surveying proceeds in a hurry and points are recorded without checking whether the device shows Fix, some points later may clearly be offset when reviewing data, forcing a return to the field for re-measurement. Registering points without realizing the required accuracy hasn’t been achieved is a typical mistake.

Mistakes in positioning offset settings

In RTK surveying, you must correctly set the instrument’s mounting height and offsets. For example, when using a pole or monopod and placing its tip on the ground point to be measured, with a GNSS antenna or smartphone mounted above it, failing to correct for the height to the antenna will not yield the correct ground coordinates. The image shows a smartphone-mounted RTK receiver “LRTK Phone” attached to a monopod with a height offset entered. On site, you measure the instrument and adapter lengths and set them in the app, but mistakes happen when the offset value is entered incorrectly or the changed value is forgotten. For example, if the antenna is actually 1.8 m (5.9 ft) above the point but the setting is left at 0 m (0 ft), a 1.8 m (5.9 ft) vertical error will occur. Horizontal position can also be offset if a prism pole is tilted during measurement; equipment without tilt compensation requires the pole to be kept strictly vertical. Errors from incorrect offset settings are sometimes hard to notice and may only become apparent later when plotted and the height does not match, so caution is required.

Mis-measurement from not confirming FIX

This is the error of continuing work without confirming whether a fixed solution has been obtained. Recording points while the solution is Float is itself a problem, but a particularly troublesome situation is when the operator believes the device was Fix at the time of measurement but it actually wasn’t. In environments where Fix is difficult—near buildings or under elevated structures—forcing measurements can produce a fleeting Fix mark that is actually unstable, a pseudo-Fix state with large errors. If you don’t notice this and assume “Fix so it’s OK,” that point may later be grossly out of place and require rework. Always check the receiver or app display before and after each point; if Fix is not achieved, remeasure or change the environment and try again. Avoid rushing and relying on assumed Fix.

Shifts from coordinate system or reference point setting errors

Handling the reference coordinate system is also critical in RTK surveying. Mistakes here can make all measured points wrong and lead to major rework. For example, in Japan the plane rectangular coordinate system of the Japan Geodetic Datum 2011 (JGD2011) is used, but choosing the wrong zone number can cause east–west shifts of tens of kilometers. Using a site-specific local coordinate system but accidentally measuring in global coordinates can also cause problems. Additionally, mistakenly entering the known coordinates of a self-established base station is dangerous: a single-digit error can shift all points by tens of meters. Such coordinate-system errors are not easily noticed on site, since Fix may be achieved and work proceeds as if normal. When data is checked in the office later, all points may fail to match drawings, possibly forcing mass re-measurement. Countermeasures include double-checking base station and coordinate system settings before work, and, where possible, performing a test measurement on a known local point to confirm the correct coordinates before starting full surveying.

On-site checkpoints to spot “bad RTK points” in advance

To avoid creating “bad RTK points” from the mistakes above, on-site pre-checks and careful measurement are essential. Below are key checkpoints to detect suspicious points on site and prevent rework.

• Confirm FIX state: Before recording each point, verify that the GNSS receiver or app solution is definitely FIX. If Fix is not achieved, do not save the point; wait, or change the environment and reacquire satellites. If the Fix mark appears but is intermittent or unstable, remeasure or average measurements to improve accuracy. Assuming “it must be Fix” is the most dangerous mindset—do not take the display at face value. Some models display GNSS status and accuracy indicators (PDOP or satellite count), which can be referenced.

• Multiple measurements and averaging: Take multiple observations rather than a single one to eliminate outliers. For important points, perform duplicate measurements or take readings at different times and compare. If the same point yields clearly different coordinates, a problem is likely. Use any averaging functions in the RTK receiver or app—for example, continuous measurement for 10 seconds to 1 minute to take an average will reduce transient errors and make it easier to judge accuracy. Even a short wait after Fix is obtained can stabilize positioning before saving.

• Instrument setup and offset checks: Handle instruments carefully. When using a pole or monopod, keep it vertical using the bubble level and confirm the tip (spike) is at the intended point. Before measuring, check in the app that the antenna height and offset settings are correct. In busy field work, people often change pole length but forget to update settings. For lateral offsets using L-shaped adapters to place the smartphone or GNSS receiver offset from the pole, follow the manufacturer’s recommended correction method. A small routine check of posture and settings before measurement can prevent critical errors.

• Coordinate system and localization pre-setup: Align the reference coordinate system before starting. For network RTK, confirm which coordinate system (which JGD2011 zone) will be used, and apply coordinate transformations or localization corrections if necessary. If the design drawings use a local coordinate system, apply parallel translation/rotation corrections to GNSS coordinates using known local points. Neglecting this will result in high-precision coordinates that do not match the design. Conversely, don’t apply local corrections twice if you are already using public coordinates. Decide the reference system in the survey plan and ensure all team members know the device settings.

• Double-check with known points: At the start of surveying and after breaks, measure a known reference point on site. Since the coordinates of that point are known, you can immediately determine whether the RTK measurement is drifting. If large discrepancies appear, immediately check for setting errors and correct them. If no known point exists, establish a temporary mark at the start, measure it, and re-measure it at the end to verify no change. This method is also effective.

Techniques to identify and correct bad RTK points in the cloud

Uploading RTK-collected positioning data to the cloud greatly simplifies quality control and error detection. The image above shows an example of the “LRTK Cloud” interface, where survey points recorded on site are plotted on a map and you can view coordinates, notes, and details for selected points. Comparing cloud data with maps or design drawings makes finding and correcting “bad RTK points” smooth.

If field-collected data is uploaded to the cloud, office staff or other team members can check data in real time. For example, they can check whether measured point groups align with design positions or spot any obviously outlying points. If a single point is plotted far from the others on the cloud map, someone can immediately instruct the field team to re-measure point No. XX. This lets you identify and re-measure erroneous points the same day, reducing the risk of later rework.

Cloud use enables centralized data management and visualization for early error detection. Practical techniques include overlaying design data and known point coordinates on the cloud map to visually check offsets. Using distance-measurement tools to compare distances between known points can reveal scale errors. Also, photos and notes attached to each point can show on the cloud if the wrong structure was measured, for example. When a problematic point is found, tag it for attention or edit/delete it in the cloud as needed. If a base coordinate error causes a uniform offset across the dataset, you can apply a bulk offset correction to all survey points in the cloud (if that feature exists); otherwise export the data, apply a parallel translation in CAD or GIS, and re-upload. Thus cloud workflows can in some cases “rescue” bad points by post-correction. However, it is best to avoid mistakes from the start; cloud correction should be a last resort, with primary reliance on on-site verification and re-measurement.

Recommended flow for accuracy checks and inspection routines

To prevent rework in RTK surveying, it helps to establish habits of checking accuracy and inspecting equipment/data at key stages. Below is a suggested flow to incorporate into fieldwork.

• Start-of-work check – Upon arriving on site, first verify equipment operation using a known reference point. After powering on GNSS, perform RTK measurement on the known point and confirm the obtained coordinates match the known coordinates. If there are large discrepancies, do not proceed until you identify and resolve coordinate system settings or equipment malfunctions.

• Periodic checks during measurement – For long work sessions, perform periodic accuracy checks. As a guideline, every few hours or every few hundred meters measured, pause and re-measure a reference or starting point to check for drift. Changes in satellite geometry or ionospheric conditions between morning and afternoon can introduce small biases, so regular checks detect cumulative errors early. Also, after actions like swapping rover batteries or re-establishing a base station, re-measure a known point to confirm correct restart.

• Multiple measurements for critical points – For reference points or points that are hard to re-establish later, perform independent repeated measurements. For example, measure the same point twice or on different days/satellite configurations. If consistent coordinates are obtained across times, the point is reliable. Consider additional observations depending on the point’s importance. The “three-point check” is also useful: select three arbitrary points, measure them with RTK, and check mutual distances and angles—if the triangle sides logically match, the survey scale is consistent.

• Closure check at finish – After obtaining all points, re-measure the start reference or points measured at the beginning. If no coordinate difference exists between start and finish measurements, major errors did not creep in during surveying (closure check). If discrepancies are found, data acquired within that period may be affected; ideally re-measure problematic sections if time permits.

• On-site data review – Before leaving the site, display and inspect the data on the device. Use a checklist to confirm point counts, point names, notes, and attached photos are complete. In large projects it’s easy to miss points—verify no points were omitted and add any missing ones immediately. Neglecting this often forces return visits later. Always perform on-site data QA.

• Backup and sharing – Finally, promptly back up collected data. Save to surveying terminals and SD cards, and if possible upload to the cloud or send to the office. If cloud-linked, upload before leaving site. This reduces data-loss risk and allows others to review data. Maintaining shared, up-to-date data between field and office prevents rework and improves team efficiency.

Adopting such a flow routinely will ensure RTK surveying accuracy management. In particular, measuring reference points at the start and end follows the long-standing principle of “verify at the beginning, verify at the end.” Even with high-precision RTK, human double-checks minimize the risk of rework due to surveying errors.

Best practices to leverage RTK in the field, design, and maintenance

Having covered RTK utility and precautions, here are best practices for leveraging RTK across project phases—field (construction), design, and maintenance. Applying RTK effectively by role will greatly improve survey quality and efficiency.

Using RTK on construction sites

On construction sites, actively use RTK for as-built verification and stakeout. If the surveyor uses a single RTK device to perform positioning and stakeout, tasks that previously required a total station and an assistant can be streamlined. Best practice is to align design and field coordinate systems ahead of time and establish a workflow of as-built measurement → immediate cloud sharing → supervisor/designer review. This enables on-the-spot quality checks and quick corrective actions to prevent rework. It is also effective for site supervisors to carry an RTK-equipped smartphone to quickly measure and verify questionable areas. Shifting small-scale surveying from a specialist team to site staff empowers immediate correction of minor stakeout errors. Key points for on-site RTK use include keeping device data and design drawings up to date on the terminal, selecting appropriate measurement modes (single-point vs. continuous) for the target, and coordinating safety and communication with nearby machines and workers. With these practices, RTK becomes a powerful quality-control tool on site.

Using RTK in design work

RTK surveying offers many advantages in the design stage. Designers and investigators can obtain high-accuracy location data themselves in the field, quickly obtaining initial survey results. For example, in road design, rough RTK measurement of candidate routes helps assess elevation and access road positioning. Information that previously required waiting for survey company drawings can now be grasped quickly within the design team. RTK is also useful for validating design coordinates on site before construction: check whether the planned structure location is compatible with the terrain or land boundaries. This prevents design mistakes and misinterpretation that lead to rework. Best practices for designers handling RTK data include unifying the coordinate systems used in CAD/BIM and RTK, and documenting procedures for converting to design coordinates (localization and geoid corrections). Directly importing RTK-collected site data into design drawings streamlines design–field data integration and reduces design changes and additional work.

Using RTK in maintenance and management

RTK is also very useful in maintenance of roads and structures, enabling accurate recording and sharing of inspection/repair locations and facilitating asset management and tracking of changes over time. For instance, recording damage locations encountered during road patrols with RTK allows repair crews to locate the exact spot later. In bridge or tunnel inspections, recording crack or defect positions with high accuracy allows quantitative assessment of progression at subsequent inspections. Best practice is to integrate RTK-derived positions directly into GIS or asset ledgers. Using web services like LRTK Cloud to store field-collected data eliminates the need to copy coordinates into paper ledgers or Excel, enabling instant sharing of up-to-date information among staff. RTK is also valuable for disaster response: quickly measuring affected areas and sharing to the cloud helps agencies grasp the situation. In maintenance, the key is to “record site conditions accurately in location as a common language.” Incorporating RTK into routine maintenance transforms traditionally experience-based workflows into data-driven processes, enabling planned, efficient maintenance with fewer errors.

Recommendation for simple surveying with LRTK

So far we’ve covered common RTK mistakes and prevention, plus application across fields. Although RTK is highly useful, maximizing its benefits requires knowledge of device settings and careful checks, which can be a barrier for beginners. A promising option is the smartphone-based RTK solution LRTK. LRTK mounts a compact dedicated GNSS receiver to a smartphone and links to cloud correction services to enable centimeter-class positioning easily.

Using LRTK reduces many causes of rework mentioned above. For example, tasks users previously had to manage—coordinate system settings and base station management—are simplified: LRTK can use cloud reference stations and satellite augmentation signals (e.g., QZSS CLAS), removing the need for manual coordinate transformations or base station setup. With a smartphone app, correct coordinate-system high-precision positioning starts automatically by pressing a button. The app clearly shows positioning status, so beginners can more easily notice mistakes. For offset settings, using a dedicated monopod with presets makes changing antenna height as simple as selecting a preset value, minimizing setting errors. Measured data is automatically backed up to the cloud, eliminating concerns about forgotten or lost data, and results are shared immediately for office verification. These cloud features embody the earlier-described cloud advantages as standard functionality.

Above all, the LRTK series is pocket-sized and affordable. You no longer need survey vehicles with expensive gear or multiple specialists—field staff can perform surveying with a smartphone. This immediacy improves decision speed on site. Designed as a “one-person, one-device universal surveying tool,” LRTK’s ease and reliability have led to adoption in construction sites and municipalities.

If rework from RTK surveying troubles you, consider such modern simple surveying systems. LRTK enables correct procedures without specialized knowledge, greatly reducing human error. The combination of smartphone convenience and cloud integration can dramatically improve productivity and quality. If interested, check official LRTK information. It can change on-site surveying styles and contribute to smooth, rework-free operations.

FAQ

Q: What are RTK Fix and Float solutions? A: In RTK, a Fix solution means the GNSS integer phase ambiguities have been correctly resolved, yielding horizontal accuracy on the order of a few centimeters. A Float solution indicates unresolved ambiguities and is a provisional solution with large errors—typically tens of centimeters to over 1 m (3.3 ft). In short: Fix = a precise, resolved solution; Float = an insufficient, provisional solution. RTK surveying generally requires Fix before recording points.

Q: How can I verify accuracy when I’m unsure during RTK surveying? A: First check the receiver or app display to confirm it shows FIX. Then, if possible, measure a nearby known point to verify accuracy; if the known point yields correct coordinates, the system is functioning correctly. Measuring the same point multiple times and checking variability is also useful. If large variations occur, satellite reception may be unstable. Check accuracy indicators like PDOP and satellite count if available. If indicators are within acceptable ranges, the system is generally okay. If still uncertain, wait for improved satellite geometry or move to a less-obstructed area before re-measuring.

Q: What level of accuracy can RTK provide? A: Under good conditions with a Fix, typical RTK GNSS provides horizontal errors of about 1-3 cm (0.4-1.2 in) and vertical errors of about 2-5 cm (0.8-2.0 in). However, this varies with baseline length and satellite geometry. With short baselines and open sky, sub-centimeter accuracy is possible (in the 1 cm range, about 0.4 in). Conversely, a Float solution can produce horizontal errors of tens of centimeters and vertical errors of over 1 m (3.3 ft). In urban areas with limited sky view, even Fix solutions may exceed 5 cm (2.0 in) error. To stabilize accuracy, use multi-GNSS, dual-frequency receivers, and averaging to reduce transient errors. In any case, obtaining a Fix solution is the prerequisite for high accuracy.

Q: How do I prevent coordinate system shifts in RTK surveying? A: The most important step is confirming coordinate system settings before work. Decide the reference coordinate system to use (e.g., a specific JGD2011 zone) and have the entire team verify the correct system is selected in devices and software. For network RTK using public coordinates, most reference station services use the geodetic datum (JGD) and are fine as-is, but if you need to match site-specific local coordinates, perform localization (one-point or multi-point local correction). Measure a known point, compute the difference between displayed and expected coordinates, and apply the correction so subsequent measurements match the local coordinate system. If you install your own base station, be careful not to enter the base coordinates incorrectly—verify by independently surveying the reference point beforehand. Finally, routinely compare field data to design drawings or known points; if anything seems off, suspect and investigate early to avoid large-scale rework.

Q: What is smartphone surveying with LRTK? A: LRTK combines a smartphone, a dedicated GNSS receiver, and cloud services into a new high-precision positioning system. By attaching a pocket-sized RTK receiver to a smartphone and obtaining corrections via the internet (from reference station networks or QZSS CLAS), anyone can perform centimeter-class surveying with a single button. The system removes the need for complex base station setup or coordinate transformation and allows accurate surveying without specialist knowledge. Positioning data is automatically saved and shared to the cloud, reducing the risk of data loss and eliminating manual data transfers. In short, LRTK turns a smartphone into a high-precision surveying tool and significantly improves field productivity. Dedicated devices are relatively affordable, making one-device-per-person workflows realistic. For those who want RTK surveying to be easier and more reliable, LRTK is a strong option.