5 Recording Rules to Properly Maintain the Observation Log for an Electronic Distance Measurement (EDM) Instrument
By LRTK Team (Lefixea Inc.)
When using a total station for surveying, it is important not only to measure correctly on site but also to keep an observation log in a form that allows later verification. If the observation log is not organized, even if the measurements themselves remain, it can be difficult to determine under what conditions, by whom, from which reference, and which points were measured, making verification of results and rework time-consuming. In particular, during control point surveying, staking out, as-built verification, checks near boundaries, and work by multiple crews, omissions or inconsistencies in records can affect construction decisions.
In this article, we organize and explain five field-friendly recording rules for correctly keeping observation logs when using an optical surveying instrument. Whether the observation log is on paper or in electronic form, the underlying idea is the same: make records that can be traced later. To avoid problems after measurement, aim to keep records that allow you to follow the whole sequence—not just the measured values but also the observation conditions, references, verification results, and correction history.
Table of Contents
• Keep the observation logbook as a record that can be reproduced later.
• Rule 1: Write the observation conditions and task assumptions first
• Rule 2: Use consistent names for the instrument point, backsight point, and survey point.
• Rule 3: Record not only measured values but also verification values and judgments
• Rule 4 Do not omit instrument height, mirror height, or units
• Rule 5: Ensure revision history and data transfers can be tracked
• Practical measures for keeping a total station observation log in the field
• Summary Organizing observation logs preserves survey quality
Keep observation logs as records that can be reproduced later
The observation logbook for a total station is not merely a form for recording measured values. The purpose of the logbook is to enable anyone who reviews it later to understand the day's work and, if necessary, to verify the sequence of measurements. Details that may seem obvious to the person who worked on site become difficult to use as a basis for judgment when they are not recorded and are reviewed a few days later by another staff member, an inspector, the design team, or construction management.
With a total station, the operator identifies a backsight from the instrument station, measures angles and distances, and determines coordinates and elevations. Therefore, if only the measured values are retained, it becomes difficult to assess the validity of the results unless it is clear which reference was used for the observations, which point was used as the backsight, and how mirror height and instrument height were handled. The observation log must record not only the survey results but also the conditions and decisions that led to those results.
When observation logs are insufficient, various problems arise on site. For example, if survey point names do not match the drawings or coordinate lists, it takes time to verify which point the record refers to. Without recorded backsight check values, it becomes difficult later to determine whether the instrument moved during work. If records of re-measurements are not kept, it becomes unclear why a particular value was adopted as the final value. Each of these is a small omission in the records, but they can lead to significant rework during as-built documentation or internal verification.
A correct observation log does not mean a neatly transcribed record. It is a record that allows what actually took place on site to be traced accurately without omission or excess. Even if there are some notes, its practical value increases when the reasons for corrections are clear, the adopted values are identifiable, and the connection to the standards can be confirmed. Conversely, even if the numbers are neatly arranged, it is weak as supporting documentation if the observation conditions are not known.
On sites using total stations, filling out the observation log is sometimes deferred in favor of working quickly. However, once you leave the site it can be difficult to reconfirm measurements under the same conditions. Weather, visibility, construction progress, the positions of temporary structures, and the condition of survey points change from day to day. Therefore, recording the necessary information at the time and place of observation is fundamental to reducing omissions in the record.
The five rules covered in this article are not dependent on any particular report format. They can be applied in any format—paper field notebooks, electronic forms, data output from surveying instruments, internal management sheets, and so on. The important thing is not to make the recorded items inconsistent from site to site. If you ensure that anyone performing the work can record from the same perspective, the quality of the observation logs will remain stable.
Rule 1 Write the observation conditions and work assumptions first
The first information that should be recorded in the survey logbook is the observation conditions and the assumptions underlying the work. Even if the measurements themselves remain as data from an electronic distance meter (EDM), the numerical values cannot be correctly interpreted without knowing the working conditions on the day. The observation date, work location, nature of the work, person in charge, reference used, weather, line-of-sight conditions, and the extent of the work should be recorded at the beginning of the logbook.
Observation date and work location are basic items, but they tend to be surprisingly ambiguous. When work is carried out over multiple days at the same site, omitting the date makes it difficult to determine which day's observations the values correspond to. Also, the work location may be insufficient if only the site name is given. It is important to record information in the units needed for later cross-checking, such as construction section, survey line, structure name, construction scope, and drawing number.
Simply writing "survey" as the work performed is insufficient as information. Depending on whether it is verification of control points, installation of batter boards, as-built verification, confirmation of excavation locations, or reference checks near boundaries, the aspects a reader of the observation log will focus on will vary. If the purpose of the work is known, it becomes easier to determine which measured values are important and which verification values should be checked.
Keeping records of personnel is also important. On sites where the surveyor, mirror operator, recorder, and verifier are separate, keeping a record of each role makes later checks smoother. When multiple teams are working, recording the team name and the version of the data used helps prevent confusion of coordinates. Making clear who worked under which conditions is not for assigning blame, but to shorten the verification path.
Weather and visibility conditions are useful for assessing the reliability of observation results. Optical surveying instruments can be affected by situations where the target being sighted is hard to see, rain, strong sunlight, heat shimmer, vibration, changes in reflection conditions, and the like. Of course, simply noting the weather does not guarantee accuracy, but it makes it easier to explain the conditions at the time if the measurements show variability or a decision to remeasure is made.
Also, the assumptions about the reference points and coordinate data used before the work should be retained. Make it clear whether public coordinates were used, a site-specific local coordinate system was used, a coordinate list created from design drawings was used, or existing on-site reference points were used. On sites where coordinate systems and the treatment of elevations are mixed, if these assumptions are omitted it becomes difficult to tell whether discrepancies in measurements are caused by machine issues or by data mix-ups.
Observation conditions are recorded more accurately at the start of work than by trying to remember and write them down afterward. If you fill in the opening items of the observation log when you enter the site and add entries if anything changes during the work, you can reduce omissions in the records. For example, changes such as visibility being good in the morning but heavy rain starting in the afternoon, changing the instrument station partway through, or swapping the coordinate data used are all pieces of information that should be kept together with the measurements.
In records of pre-work assumptions, it is important to record verifiable facts rather than definitive statements. Instead of simply writing “no issues,” describe what was checked and how you judged it—for example, “a follow-up check was conducted, and, in light of the site’s management criteria, it was decided to continue work”—so that it is clear what was verified and how the decision was made. If there are allowable values or management criteria specific to each site, record them according to those standards. Observation logs are not for writing impressions; they should link the confirmed facts to the judgments made.
Rule 2: Write instrument points, backsight points, and survey point names consistently
In the observation log of a total station, it is especially important to standardize the notation of instrument stations, backsight points, and survey point names. In survey records, even slight differences in point names can create significant extra work during reconciliation. If point-name notation varies across drawings, coordinate lists, data stored in surveying instruments, observation logs, and as-built documents, it becomes unclear whether they refer to the same point or to different points.
An instrument station is the reference point where a total station is set up. In the field book, write the instrument station name using the same notation as in the coordinate list. Even if a local name is used on site, it is important to retain a record showing its correspondence to the official point name. For example, even if the site calls it the "north reference," the field book should use the point name registered in the coordinate list and, if necessary, record the on-site name as a supplementary note.
The backsight point must likewise have its point name recorded accurately. The backsight is an important point used to align the instrument’s direction. If the backsight is mistaken, it will affect all subsequent observations. In the field book, record not only the backsight point name but also that a backsight check was performed, the results of the check, and, if necessary, the timing of any recheck. If a backsight check is performed during the work, recording not only the initial check but also any interim checks makes it easier to judge when instrument shift or tripod settlement is suspected.
Survey point names indicate the actual points observed. If a point name is ambiguous, it becomes unclear which location the measurements correspond to. This is especially true for as-built checks and batter-board staking, where similar point names tend to become numerous, so it is necessary to establish notation rules. When including items such as the construction section, survey line, point number, left/right, upper/lower, or structure classification in a point name, use a consistent order within the site.
When standardizing point names, avoid ad hoc abbreviations used only on the spot. Short abbreviations can be easier to enter during observations, but if their meaning is not clear to later readers they are an insufficient record. If abbreviations are used, record the correspondence in the observation log or on a separate sheet listing point names. If point names differ between the total station’s internal data and the observation log, the conversion rules must also be clearly defined.
Also, to prevent incorrect entry of point names, it is effective to check the coordinate list before observations and verify that it matches the point names to be recorded in the field book. When point names are entered manually on site, inconsistencies can easily occur in the number of digits, hyphens, sub-numbers, left/right notation, and letter case. In the field book, it is desirable to avoid visually similar characters and confusing abbreviations, and to use notations that are hard to misread.
The relationships among instrument stations, backsight points, and survey point names should be traceable within the field book. If it is clear from which instrument station, which backsight was used, and which survey points were measured, it becomes easier to verify the results. Conversely, if the record only lists the measurements of survey points without showing their correspondence to instrument stations and backsights, the sequence of measurements cannot be confirmed.
When multiple instrument stations are used, record the observation ranges separately for each instrument station. If the instrument is relocated partway through, record the new instrument station, the backsight, the relocation time, and the check value. If the change of instrument station is not clearly indicated in the field book, it becomes difficult to determine whether the same survey point was measured from a different reference or is merely a duplicate record.
Standardizing point names greatly affects post-survey data organization. When using data exported from surveying instruments to create reports or drawings, consistent point names shorten the cross-referencing process. If point names are inconsistent, even if the surveying itself is complete, office corrections and verifications will take time. The point-name rules in the observation log should be treated as a fundamental rule that connects field operations and office work.
Rule 3 Preserve not only measured values but also confirmation values and judgments
In the observation log, it is necessary to record not only the measurements obtained with the total station but also the verification values and judgments. Measurements are the results such as distance, angle, coordinates, and elevation. Verification values, on the other hand, are numbers and records used to confirm that the work is proceeding correctly. Examples include differences in backsight checks, check observations to known points, differences between duplicate observations, differences before and after re-surveying, and differences from design values.
A common issue on-site is that only the final adopted value remains, and it is unclear what checks were performed before adoption. There may be some variation in measured values, but if there is no record of how those variations were assessed, it becomes difficult to explain later. It is important to document whether the value was judged acceptable against site- or task-specific management standards, whether it was adopted after re-measurement, or whether it was verified against a different reference point.
Backsight checks are an item that should be especially recorded in the observation log of a total station. Confirm the backsight at the start of work, and check it as necessary during the work and at its completion to see whether the instrument’s orientation has shifted. In the observation log, record the time or timing of the backsight check, the check results, and the decision on whether to continue work. Rather than simply writing “checked,” note whether any difference was found and the rationale for the decision, as this will be helpful for later verification.
Verification observations to known points are also effective. To confirm there are no errors in the instrument point or the backsight setup, you may measure another known point to check differences in coordinates or distances. Recording these results in the observation log makes it easier to explain the validity of the reference used. This is especially helpful on sites with a wide work area or on sites using existing control points, where having records of known-point verification makes confirmation easier.
Do not omit records of re-measurements. You may need to re-measure for reasons such as the value not stabilizing during measurement, difficulty in sighting, possible movement of the mirror, or temporary obstruction of the line of sight by passing vehicles or people. In such cases, if you erase the initial value and leave only the final value, the fact that a re-measurement was made will be obscured. In the observation log, clearly record the reason for the re-measurement, the value adopted after the re-measurement, and how any values that were not adopted were handled.
Even when making corrections or amendments to measured values, avoid erasing them in a way that prevents the original content from being traced. For paper observation logbooks, make corrections so that the corrected entries are identifiable, and record the reason for the correction and the person who verified it. For electronic data, implement procedures to retain records from before and after updates and a history of corrections. An observation logbook is not a document intended to present only the final results attractively; it is a record that preserves the process of verification.
When recording verification values, make the units and reference clear. Even if you record a difference, it loses meaning unless it is clear whether the difference is in horizontal distance, elevation, or coordinates. Also, when recording differences from design values, make clear which design data set was used as the reference. On sites where design data are updated, it is important to know whether the difference is relative to the old data or to the new data.
In records of judgments, it is assumed that site management standards are followed. Do not write only subjective words such as "okay" or "no problem" in the observation log; instead, record what was checked and the decision made. For example, use expressions that make action and result clear, such as "continue work after backsight confirmation," "adopted after verification of a known point," or "adopted the value after re-measurement." If numeric values and judgments are recorded together, it will be easier to explain later.
In observations with a total station, the ease of measurement varies depending on site conditions. Poor visibility, difficulty setting up the prism, unstable footing, a tripod swaying in strong winds, or sighting made difficult by backlighting—there are various factors that can lead to variability in the measured values. When re-measurements or checks are carried out under such conditions, recording those circumstances in the observation log makes the entry a record that includes on-site judgment rather than just a list of numbers.
Rule 4: Do not omit instrument height, mirror height, or units
In the field book of an electronic distance meter, it is important not to omit instrument height, prism height, units, correction conditions, and similar details. These items directly affect the interpretation of measurements. In work that deals with heights in particular, failures to record instrument or prism height, input errors, or unit mix-ups can lead to discrepancies in the results. Even when a task only checks horizontal positions, it is safer to leave these details recorded rather than omit them.
Instrument height is the information indicating the height from the instrument point to the sighting axis of the total station. Mirror height indicates the height of the mirror erected at the survey point. Because these are related to the calculation and verification of heights, it is important that the values entered on site match the entries in the field book. If you only enter them without leaving a record, you will not be able to confirm which values were used later if questions about the heights arise.
Mirror height is an item that is easily changed on-site. Depending on the conditions at each survey point, the mirror may be raised or lowered, and it may not remain constant even on the same workday. Even if you intended to work with the same mirror height throughout, if it was changed midway without being recorded, you will not be able to determine it afterward. In the observation log, clearly record the mirror height used for each survey point or for each range where it was changed.
Care must be taken with unit handling when recording instrument height and mirror height. On site, meter units (m (ft)), the number of decimal places, and expressions converted to millimeters (mm (in)) can be mixed. In the observation log, record using a single unit consistently and establish rules for the number of decimal places. Because even misplacing the decimal point by one digit can cause a large discrepancy, it is important to make both the numbers and the units clear.
The units for distance and angle are the same. A total station handles multiple values such as horizontal distance, slope distance, height difference, horizontal angle, and vertical angle. If it is not clear which values have been recorded in the field book, you will become confused later when performing calculations or cross-checks. Make the field book’s column headings explicit and record whether a value is a horizontal distance or a slope distance, and whether it refers to height or elevation.
When recording elevations, it is necessary to clearly distinguish between different references such as elevation, design elevation, height from a temporary benchmark, and on-site reference elevations. The same term "height" can mean different things depending on which reference is used. In the survey log, record the elevation reference used so that it can be cross-checked with drawings and design data. If the elevation reference is recorded ambiguously, misunderstandings are likely to occur during as-built verification and when checking construction positions.
It is a good idea to record correction conditions according to the site and the type of work. In distance measurements with a total station, meteorological conditions and instrument settings can affect the results. Not every site requires detailed correction records, but you should retain the settings used and any conditions based on site rules. Especially for long-distance observations or tasks where precision control is important, making the measurement settings available for review later will make subsequent verification easier.
To prevent recording errors in instrument height and mirror height, verbal confirmation by reading aloud is effective. When the person operating the instrument, the person holding the mirror, and the person recording are different, always announce any change in mirror height aloud and record it in the observation log. Even if you intend to keep the mirror height fixed, it may be temporarily changed due to on-site circumstances, so it is important to establish rules for recording changes.
Also, when reviewing data after measurements, verify that the instrument height and mirror height recorded in the field book match the settings saved in the total station. If the handwritten field book and the data stored in the instrument disagree, you will need evidence to determine which is correct. If the time of changes, the range of measured points, or notes from the person in charge are available, it will be easier to identify the cause.
Units and height information tend to be omitted more often by people who are experienced. However, the observation log is not something only you will read. To ensure that another person can read it and interpret it the same way, information that seems obvious needs to be recorded clearly. Recording instrument height, mirror height, units, and reference heights is the foundation for correctly interpreting survey results.
Rule 5: Make revision history and data transfers traceable
To properly maintain observation logs, it is important to be able to trace the revision history and the flow of data transfers. In field surveying, recorded entries are sometimes corrected after verification. Situations requiring corrections are not uncommon, such as misrecorded point names, omissions in recording mirror heights, mix-ups of survey points, changes to adopted values due to re-surveying, and changes in comparison results following updates to design data.
The correction itself is not the problem. The problem is a situation in which it is unclear why the correction was made, when it was made, who verified it, and how the pre-correction values were handled. For observation logbooks, being able to trace the sequence of events when a correction has been made is more important than having no corrections at all from start to finish.
In a paper logbook, if you completely erase a correction, the original record becomes impossible to determine. In practice, it is desirable to handle corrections in a way that makes the fact of the correction clear, and to record the reason for the correction and the verifier. The same applies to electronic data: operations that only overwrite records without preserving a history make later verification difficult. It is reassuring to be able to record the files before and after corrections, the update timestamps, the person who performed the work, and the verifier.
Records of data handovers are also important. The data observed with a total station are not only stored in the device but are also used for report generation, drawing production, as-built documentation, and internal reviews. If it is not clear which data was extracted, when, by whom, in what format, and into which documents it was incorporated, old and new data may become mixed.
Particular attention should be paid when the same site is surveyed multiple times. When there are initial observations, re-surveys, post-correction observations, and additional observations, confusion can easily arise simply because file names and storage locations are ambiguous. In the survey logbook, keep the work date, scope of work, data names, storage locations, recipients, and the version of the coordinate list used linked together. This makes it possible to verify which logbook corresponds to which data.
The rules for file names are also related to the observation log. Including the date, site name, work section, task description, version number, etc. in the file name makes it easier to find later. However, you should not rely solely on the file name; it is necessary to also retain the corresponding data name in the observation log. Even if files are moved or saved under different names, having records in the observation log makes them easier to track.
In the revision history, clearly distinguish between accepted and rejected values. If it is not clear which value was ultimately accepted after remeasurement, there is a risk that the wrong value will be used when preparing reports. In the observation log, make the accepted value identifiable at a glance, and provide a reason for each value that was rejected. The reason does not need to be lengthy, but should convey the basis for the decision, for example: poor sighting, mirror-height check, acceptance of remeasurement, or correction of a misrecorded point name.
When handing over data, whether it has been verified is also recorded. After survey data are delivered to the office, they are checked against coordinate lists, incorporated into drawings, used to produce reports, and feedback is provided to the field. Keeping a record of how far verification has progressed makes it easier to prevent work from proceeding with unverified data. Especially for data related to construction positions, it is important to ensure that pre‑verification values are not returned to the field.
When multiple people are working, the person who records the observation log and the person who processes the data may be different. In such cases, abbreviations that the recorder wrote assuming they would be understood may not be communicated to the data processor. When keeping revision histories and handover records, use expressions that convey the same meaning to the parties involved and add clarifications as necessary. The observation log needs to function as a common language on-site.
Also, verify the consistency between the observation log and the deliverable documents. By confirming that the adopted values recorded in the observation log match the values listed in the final as-built documents and verification materials, you can prevent transcription errors. Even when data are extracted directly from surveying instruments and processed, items can be swapped or misassigned during the reporting or documentation process. The observation log should be maintained so that it can be used as the source for such verification.
An observation log that tracks revision history and data transfers is also useful in case of trouble. When questions arise about measurements, knowing which point in time the data came from, whether re-measurements were performed, and who verified them makes it easier to narrow down the cause. Conversely, if no history is kept, you end up relying on the memories of those involved, and verification takes more time. An observation log is both a record of work and a resource for reducing the time required for later verification.
Strategies for Keeping an Observation Log of an Electro-Optical Distance Meter (EDM) in the Field
Even if you establish rules for recording in the field book, they are meaningless if they are not followed on site. In work using a total station, setup, centering and leveling, backsighting, sighting, measuring, moving, and checking are carried out in sequence. On busy sites, recording tends to be put off, and trying to write everything up after the work can lead to omissions. To leave a correct field book, it is necessary to create a system in advance that makes recording easy.
First, arrange the observation log format so it is easy to use on site. If there are too many required items, filling it out becomes a burden; conversely, if there are too few, it cannot be used for verification. Organize the minimum necessary items—observation date, work location, person in charge, instrument point, backsight, survey point name, measured value, verification value, instrument height, mirror height, reason for remeasurement, adopted value, remarks, etc.—and use them according to the work content. Having fixed fields makes it easier to prevent omissions in records than writing free-form notes every time.
Next, determine the timing for recording. It is more accurate to make entries in the observation log at each break in observations than to write them all at once after the work. Incorporate into the site procedures the times when records should be made, such as when the instrument is set up, when the backsight is checked, when the mirror height is changed, when a re-measurement is taken, when the instrument station is moved, and when the work is completed. If the timing for recording is established, quality remains stable even if the person in charge changes.
Reading aloud is also effective. When the person operating the instrument and the person recording are different, speaking the station name, mirror height, and check values aloud can reduce entry errors. In particular, in tasks where similar station names follow one another or where left/right distinctions are involved, mishearing and assumptions are more likely to occur. Even just confirming once before writing in the observation book can reduce later correction work.
Unify the terminology used on site. If one person writes "prism height" and another writes "mirror height," having different words with the same meaning causes confusion during checks. Decide on the notation to be used within the company and on site, and align the field names in the observation log accordingly. It's not necessary to completely avoid technical terms, but it's important not to record the same meaning using multiple different words.
It is also effective to designate someone to verify the observation log. Not only the person who made the entries, but another responsible staff member should review the log after the work to check that there are no omissions in point names, instrument point, backsight point, instrument height, mirror height, adopted values, or re-measurement records. Because it becomes difficult to recheck if defects are noticed after leaving the site, it is desirable to carry out the verification on the same day whenever possible.
When using electronic data alongside paper records, separate the roles of the paper field book and the electronic data. The stored data from a total station retain numerical values, but may not sufficiently capture on-site judgments, reasons for remeasurement, line-of-sight conditions, or cautions taken during work. Therefore, a practical approach is to cross-check the instrument data with the field book and record supplementary information and decision rationale in the field book. Even when using electronic forms, input fields and verification items should be clearly defined.
Observation logs can also be used to improve each site. By reviewing the records, you can identify which tasks require frequent re-measurements, which survey points have poor lines of sight, and which point names tend to confuse any operator. Rather than treating observation logs merely as documents for submission, using them as preparatory material for the next task can lead to improvements in survey planning and the placement of survey points.
To reduce the burden of record-keeping, it is also important to minimize duplicate data entry. Entering the same information multiple times on paper, in spreadsheets, into surveying instruments, and into management documents not only increases the workload but also raises the chance of transcription errors. Clarifying where information required on site should be recorded, at which stage it will be checked, and which documents it will be reflected in makes it easier to sustain the use of observation logs.
The observation logbook for an optical surveying instrument will stop being used in the field if it is written in excessive detail, while if it is oversimplified it becomes unusable for verification. What matters is recording the information necessary to trace the surveying workflow later in a way that does not place an excessive burden on the field crew. By aligning the recording rules with the site’s work procedures, the observation logbook becomes a document that is naturally maintained.
Summary: Keeping observation records organized preserves survey quality
To properly maintain the observation logbook of an optical surveying instrument, it is important to record not only the measured values but also observation conditions, reference points, backsight points, point names, check values, instrument height, mirror height, units, correction history, and data handover as a continuous set. The observation logbook is a document for reviewing field measurements later and for being able to explain them when necessary. Even if only numbers remain, if you cannot tell under what conditions they were measured, the record becomes difficult to use in practice.
In Rule 1, we confirmed that observation conditions and work assumptions should be written at the beginning. By recording the observation date, work location, person in charge, purpose of the work, weather, visibility, and the reference standards used, the context of the measurements becomes clear. In Rule 2, we addressed standardizing the notation for instrument points, backsight points, and survey point names. When point names are consistent, it becomes easier to cross-check drawings, coordinate lists, survey data, and forms.
Rule 3 explained that you should record not only measured values but also verification values and judgments. By recording back-sight checks, known-point checks, remeasurements, and decisions on adopted values, it becomes easier to explain the validity of the results. Rule 4 addressed not omitting instrument height, mirror height, units, and height datum. Information that affects the interpretation of heights and distances should be recorded clearly even for familiar tasks. Rule 5 confirmed that correction histories and data handovers should be traceable. If it is clear when, who, and which data were corrected and which values were adopted, you can reduce the time required for later verification.
The quality of the observation log is an element that supports the quality of surveying. On site, attention tends to be focused on measurement techniques, but if the records are inadequate, the results that were measured correctly cannot be fully utilized. Conversely, if the observation log is well organized, post-survey document preparation, internal verification, responses to inspections, and preparation for subsequent work proceed smoothly.
Whether you use paper observation logs or electronic data, the important thing is to create records that can be traced later. Decide on record items that match the site's work procedures, and if you keep measured values, verification values, decisions, and correction history in the same sequence, it will be easier to share measurements from a total station both within and outside the site. Organizing the observation log not only makes post-survey checks easier but also contributes to more stable construction decision-making.
Next Steps:
Explore LRTK Products & Workflows
LRTK helps professionals capture absolute coordinates, create georeferenced point clouds, and streamline surveying and construction workflows. Explore the products below, or contact us for a demo, pricing, or implementation support.
LRTK supercharges field accuracy and efficiency
The LRTK series delivers high-precision GNSS positioning for construction, civil engineering, and surveying, enabling significant reductions in work time and major gains in productivity. It makes it easy to handle everything from design surveys and point-cloud scanning to AR, 3D construction, as-built management, and infrastructure inspection.


