A mapped utility point can be precisely positioned and still describe the wrong conductor. Digital locating records become valuable when they preserve enough evidence for another person to understand what was detected, how it was measured and what remains uncertain. Coordinates alone do not provide that explanation.
For contractors exploring UCG Underground’s Vivax-Metrotech collection, the important comparison extends beyond receiver hardware. Internal logging, GPS source, correction services, export formats and the review process together determine whether a field observation becomes useful project information.
This review examines manufacturer documentation and U.S. guidance available in September 2026. It covers basic logging, phone-assisted mapping and integrated RTK workflows, then proposes practical controls for data acceptance. The examples and pilot measures are analytical recommendations, not reported field trials. The reviewed evidence does not establish a percentage reduction in utility strikes caused by GPS logging alone.
Digital records change the handoff between crews
The main opportunity is continuity between the person who makes an observation and the people who later use it. A construction superintendent needs to distinguish a traced alignment from an unresolved response. A designer needs to know whether a point represents an exposed facility or a geophysical interpretation. An asset manager needs the original measurement context when a later investigation disagrees.
Digital records can support those tasks by retaining observations that would otherwise depend on field notes, temporary marks or recollection. The operational benefit is conditional: someone must review the record and use its limitations when making decisions.
FHWA’s July 2026 discussion of Subsurface Utility Engineering treats utility information as something managed throughout design, construction and beyond. That is a broader process involving investigation, surveying and communication. It should not be reduced to purchasing a GPS-enabled instrument.
A useful project workflow therefore separates three states:
- Captured: a field observation exists.
- Reviewed: its meaning, completeness and limitations have been checked.
- Accepted for a stated purpose: the relevant project team understands how it may be used.
These are proposed workflow states, not universal software labels. Their value is that a successful upload cannot quietly become construction authorization. A file may be complete as a record while containing a segment that still requires further investigation.
GPS accuracy and utility location accuracy are different
GPS is one satellite system within the broader category of Global Navigation Satellite Systems, or GNSS. A GNSS position describes a reference point associated with the receiving equipment. Electromagnetic locating interprets the field associated with a conductor or transmitting source. The two measurements answer different questions.
| Evidence layer | Principal question | A favorable result does not prove |
| GNSS positioning | Where is the defined recording point? | Which service produced the locating response |
| Electromagnetic interpretation | What response is being traced and where is its estimated alignment? | That every nearby service was detected |
| Depth estimation | What depth does the instrument infer under these conditions? | Verified clearance for mechanical excavation |
| Data processing | Did the exported record preserve its meaning? | That the original observation was correct |
GPS.gov’s archived accuracy guidance gives a general smartphone example of approximately 16 ft (4.9 m) radius under open sky, with poorer results near buildings, bridges and trees. This is background guidance, not a fresh 2026 benchmark for every phone. It illustrates why a phone coordinate and a corrected surveying workflow should not be treated as equivalent.
Satellite geometry, blockage, reflected signals known as multipath and receiver design affect positioning. A high-quality coordinate source cannot repair a mistaken service identification. Equally, a well-interpreted locate can be assigned an unsuitable coordinate if the recording point or positioning conditions are wrong.
The vLoc3 RTK-Pro handbook describes its displayed 2DRMS value as expected GNSS/RTK positioning accuracy. That number should not be relabeled as total subsurface uncertainty. The field record needs separate statements about coordinate quality and the evidence supporting the target interpretation.
What current locating systems actually record
There are several ways to combine locating and mapping. They differ in where measurements originate and what supporting components are required.
Receiver logging and desktop transfer
Vivax-Metrotech lists internal logging for the vLoc3-Pro, with Bluetooth connectivity available as an option for external GPS use. Internal memory does not mean every unit includes integrated survey-grade GNSS. Its catalog also describes distortion diagnostics using screened 3D antennas and a simultaneous peak/null view. These can inform interpretation, but a buyer must still verify which diagnostic information survives export.
The MyLocator3 data-management sheet describes USB downloads of timestamped coordinates, depth measurements, line current and notes. Its July 2024 edition lists CSV, KML, SHP, XLS and XLSX exports. It also describes online application and firmware-update checks and configuration controls, with some lockouts requiring an optional dongle.
For procurement, confirm the actual installed hardware, software version and usable exported fields. A capability listed for a product family should not be assumed to be active in a used receiver or included in a particular package.
Phone or external GPS with a mobile application
The VMMap application uses Bluetooth-enabled receivers and location information from a phone or compatible external GPS device. Its product description includes iOS and Android support, survey-photo attachments in JPEG format, cloud or email sharing and several GIS-compatible output formats.
This creates a flexible workflow, but the coordinate source remains material. Attaching an external receiver is not equivalent to continuing with the phone’s position. The acceptance test should identify which source was used and check whether the receiving application preserves that distinction.
Integrated corrected GNSS
The vLoc3 RTK-Pro product page describes integrated GNSS, 4G LTE connectivity and NTRIP access to RTCM 3 corrections. It also describes onboard retention and cloud transfer for subsequent mapping use.
Radiodetection’s RD8200SG offers another integrated approach. Its current page describes an integrated GNSS antenna, compatible mobile applications and correction providers, automatic antenna-offset handling and direct export through RD Manager Online. The correction workflow depends on cellular data and service availability.
| Workflow | Coordinate source | What the buyer should confirm |
| Receiver logging with desktop review | Depends on the installed and paired configuration | Which records actually contain coordinates and usable context |
| Mobile mapping with phone positioning | The phone’s location service | Suitability for the intended deliverable and preservation of source metadata |
| Mobile mapping with external GNSS | A compatible external positioning device | Pairing, recording-point geometry and retained quality information |
| Integrated RTK locating and mapping | The system’s GNSS and correction workflow | Services, setup, capture procedure and behavior when requirements are not met |
This is a workflow comparison, not a ranking of independently tested subsurface accuracy. The appropriate arrangement depends on what the project needs the record to establish.
RTK adds dependencies as well as precision
Real-Time Kinematic positioning uses correction information to support higher-accuracy GNSS work. A receiver advertised with RTK does not remove the need to configure and verify the complete service chain.
The May 2026 RTK-Pro handbook requires a data-enabled SIM, correction-provider registration and software/cloud setup. It describes 4 GB of internal storage and distinguishes operator-captured locate records from automatically recorded self-tests, warnings and alarms.
Its capture process also addresses displacement between the GNSS antenna and locator geometry. A separate alignment step uses the electronic spirit level to compensate for that offset; the log index can increment again. An index count is therefore not automatically a count of distinct surveyed utility points.
The analytical acceptance questions are broader than “Did the receiver connect?” Ask whether the saved point is the intended compensated observation, whether its positioning-quality information is available and whether the team can distinguish it from other log entries.
Test loss of connectivity and recovery on a safe, controlled assignment before relying on the workflow. Onboard retention is a documented feature, but it does not by itself prove every app’s offline behavior, correction fallback or later synchronization logic. Those behaviors need a configuration-specific demonstration.
Define the response to an unacceptable positioning result in advance. The crew may need to preserve the locate observation while flagging the coordinate for another method of recording or later review. It should not silently substitute a different positioning source and retain the same acceptance label.
A useful record needs an evidence schema
A record should distinguish what the instrument measured from what the operator inferred and what the project reviewer accepted. This distinction is especially important when data moves between a locator application and an owner’s asset system.
The VMMap portal manual displays information including time, coordinates, frequency, depth, current, locate mode, gain and utility type. Those fields provide useful context. They do not establish that every project-specific evidence field below is automatically captured by every receiver.
The following is a proposed project schema:
| Field group | Example contents | Responsibility |
| Assignment identity | Project, ticket or work-order ID; operator; device ID | Project setup and crew |
| Observation identity | Raw log reference; stable point ID; capture time and time zone | Capture system and data manager |
| Locate configuration | Actual frequency; mode; application method; accessory context | Instrument where available and operator |
| Measured quantities | Depth and current with units and defined meaning | Instrument record plus project specification |
| Positioning context | Coordinate source; reference system; quality information; recording point | Positioning workflow and reviewer |
| Interpretation | Intended service; identity evidence; unresolved alternatives | Qualified operator and reviewer |
| Supporting evidence | Photograph; access-point note; linked verification record | Crew and project team |
| Review history | Acceptance purpose; exceptions; revision; responsible reviewer | Project data process |
Keep unavailable fields visibly unavailable. If a receiver does not export a required attribute, decide whether another approved capture method can supply it. Do not manufacture a populated field by repeating the same default across all observations.
A utility-type code needs an associated basis. It may come from a known application point, an owner’s records or an operator’s provisional classification. The asset system should not erase those differences simply because its final layer uses one category called “gas” or “communications.”
Stable point IDs also matter when photos, exposure records and corrected interpretations arrive later. A row number that changes after filtering is a poor long-term reference. Preserve the original log reference and assign project identifiers through a controlled process.
Feature dictionaries make records searchable
Vivax’s Feature Logging guide describes an Excel-based dictionary with a human-readable definition and an associated code. The published limits are 48 characters for definitions, nine for codes and 200 entries. These are documented limits of that feature, not a general database standard.
The guide also permits above-ground points of interest without a locating signal, and describes carrying feature codes and descriptions into CSV or SHP exports. Its Auto Log Feature setting retains the selected classification until changed or disabled.
For a contractor, a controlled vocabulary can make records easier to review. But automatic reuse of a label can also propagate an incorrect classification if the operator moves to a different feature without changing it. The code is a statement attached to the observation, not independent proof of identity.
A proposed dictionary should separate objects such as “access cover,” “interpreted cable point” and “exposed facility measurement.” Where ownership or service type is unknown, retain that state rather than forcing a convenient category.
Define each code once, assign responsibility for changes and retain the dictionary version used on an assignment. Otherwise, a later edit to a code’s meaning can make an older record appear to describe something the crew never intended.
Coordinates need a defined reference and measured object
Two files can contain plausible coordinates yet refer to different reference systems or different objects. Before combining them, establish the coordinate reference, units and recording-point definition.
When using GIS data in underground utility mapping, integration depends on preserving these distinctions. Overlaying a locator export on a project map is the beginning of a reconciliation, not proof that the layers agree.
For project acceptance, distinguish a surface position associated with an interpreted alignment from a measured point on an exposed utility. Also distinguish both from an uncorrected antenna position or the location of an above-ground feature. A map symbol alone may not reveal which object was recorded.
Specify the horizontal reference system and any transformation into project control. Where the project requires it, document the applicable reference-frame realization and epoch. State whether linear quantities are in feet or meters rather than relying on an application’s display preference.
Height is not locator depth
A GNSS height and a locator depth are different quantities. They should not be combined into a utility elevation until the reference surface, vertical reference and measured target are defined and the project process supports the calculation.
A useful downstream-format example is RFC 7946 GeoJSON. It uses longitude followed by latitude in decimal degrees with WGS 84, and an optional third coordinate representing height in meters relative to the WGS 84 ellipsoid. That third coordinate is not a place to insert a locator’s depth reading without an appropriate conversion and definition.
GeoJSON is discussed here as a possible downstream conversion, not as a verified native Vivax export. Similar care is needed with any output format: the destination must preserve meaning, not merely accept numbers.
Export success is not data acceptance
Different parts of a manufacturer’s software ecosystem may advertise different formats. MyLocator3, the mobile application and the web portal should be tested separately against the actual required deliverable, rather than treated as one interchangeable export function.
The RTK-Pro handbook allows configurable distance units, date formats and UTC or local time in desktop export. The portal manual lists CSV, KML and SHAPE output, along with current/depth graphs and filters. These features can help review observations, but the destination import remains another opportunity for information loss.
Esri documents several shapefile limitations: attribute names are limited to 10 characters, null values are not natively supported and date fields do not preserve time. Depending on the conversion tool, a missing numeric value can be substituted with zero. Other database features and types may also be lost.
For locating data, that creates a substantive risk. An unavailable depth must not arrive as a genuine zero-depth observation. A truncated field name must not become indistinguishable from another field, and a retained date must not be mistaken for a preserved capture timestamp.
Use a proposed round-trip test before rollout:
- Capture a small set that includes valid observations, deliberately missing optional values and explicit uncertainty notes.
- Export through the intended software version and format.
- Import into the actual destination used by the client or project.
- Compare identifiers, quantities, units, timestamps, missing values and labels with the source.
- Retain the mappings and document any transformations or losses.
Do not use a map screenshot as the sole test. It cannot establish whether the attributes, time zone or original uncertainty survived. Preserve a source copy separately from the transformed deliverable so that later corrections can be traced.
Quality levels describe evidence rather than equipment
The FHWA explanatory hierarchy distinguishes the evidence behind utility information:
| Quality level | General evidence basis | What does not create it automatically |
| QL-D | Existing records or recollection | Digitizing an old drawing |
| QL-C | Surveyed visible features correlated with records | Plotting an access cover without the required investigation |
| QL-B | Appropriate surface geophysical investigation of existence and approximate horizontal position | Adding an RTK coordinate to an unsupported response |
| QL-A | Exposure and measurement at a particular location | A precise GNSS fix or an instrument depth estimate |
The older FHWA brochure provides the explanatory definitions. Its July 2026 SUE page references ASCE 38-22 for investigation/documentation and ASCE 75-22 for recording/exchanging utility data. Project deliverables should follow the applicable current specification and responsible professional’s requirements, rather than treating this summary as the complete standards text.
The analytical implication for digital records is that quality attribution belongs with the evidence. A high-resolution coordinate should not silently upgrade a record-derived alignment. Nor should exposure at one point be extrapolated into verified geometry along the entire connecting line.
Show sampled observations and inferred connections differently. If software joins points across an uninvestigated gap, label the connection as an interpretation and retain the gap’s status. A continuous line on a map can otherwise imply continuity that the field investigation did not establish.
Review the record before it becomes a construction instruction
A practical review asks whether another qualified person can reconstruct the basis of the observation. It should address both the field interpretation and the integrity of the transferred data.
Radiodetection’s depth guidance warns that distortion, noise, bends and junctions can compromise measurements, and that estimated depth must not determine mechanical digging depth. Saving the number in a GIS does not remove those conditions.
For a proposed acceptance process, use five checks:
- Capture completeness: the required observation and identifiers exist.
- Coordinate/reference check: the positioning source and recording point suit the stated purpose.
- Interpretation review: identity evidence and unresolved alternatives remain visible.
- Transfer reconciliation: exported attributes retain their units and missingness.
- Construction handoff: the recipient understands required verification and open questions.
When observations conflict, retain the original and document the resolution. Do not average two different target interpretations into an apparently smoother alignment. Similarly, do not discard a questionable point merely to make a current or depth graph look consistent.
The VMMap portal manual describes company and team roles and user-specific visibility. That supports an access model, but does not by itself establish an immutable revision history. If the project needs controlled amendments, preserve raw exports, derived versions and review decisions through an explicitly specified process.
Limit access according to the actual audience. Field observations may contain operator information, photographs and infrastructure details. A project team should agree who can view, modify, export and distribute them without assuming that a cloud upload resolves those responsibilities.
Digital records can help in three practical situations
These examples illustrate decision mechanisms. They are not measured case studies or claims of prevented strikes.
Returning after surface marks have changed
Assume a second crew arrives after traffic, weather or other work has disturbed marks. A retained record can provide the earlier observation time, configuration, access-point context and photographs. It can help the crew understand what the first investigation covered and where uncertainty remained.
The defensible next action is to use that context for the current investigation and required notification process, not to recreate marks from old coordinates and assume they remain sufficient. The record supports continuity while preserving the distinction between a historical observation and current acceptance.
A congested crossing with good positioning
Assume corrected GNSS is performing adequately, but electromagnetic responses at a planned crossing remain ambiguous. The coordinate quality does not resolve the ambiguity. A useful record keeps the candidate observations, field warnings and identity limitations visible.
This is where documentation can change behavior: the unresolved condition reaches the planner or superintendent before the crew commits to the crossing. Given the consequences of underground utility strikes, identifying that information gap is more valuable than presenting a confident-looking map without its limitations.
The appropriate additional investigation depends on the project and affected utilities. The example does not imply that digital logging supplies a universal clearance distance or replaces verification.
An exposed point contradicts an older record
Assume a later approved exposure establishes geometry inconsistent with an earlier interpretation. Link the new measurement to its specific location, method and date, then flag the affected previous interpretation for review.
Keep the older source rather than silently overwriting it. The contradiction may concern one point, a segment or identity, and each has a different implication. Updating the entire line to match one exposure would introduce a new unsupported assumption.
The damage-prevention mechanism is an accountable correction process: a discrepancy becomes visible, someone assesses its extent and the information reaches subsequent users. More storage capacity alone does not perform those steps.
Measure improvement without claiming GPS caused it
A logging pilot should evaluate the work process before attempting a broad strike-reduction claim. The Damage Prevention Institute requires monthly metrics from measured stakeholder groups to normalize damage data. The same principle matters when a contractor evaluates its own digital workflow.
The following are proposed pilot measures, not reported performance targets:
| Measure | Suggested denominator or comparison | Interpretation limit |
| First-pass record acceptance | Accepted submissions divided by all submitted work packages | Acceptance must include required evidence, not merely a successful upload |
| Field completeness | Present required values divided by required opportunities | Legitimately unavailable observations must be distinguished from skipped capture |
| Revisit frequency | Record-related revisits per completed assignment | Access, weather and scope changes may also cause return visits |
| Exception resolution | Time from documented exception to agreed disposition | Faster closure is useful only if the disposition is technically justified |
| Damage outcomes | Incidents normalized to the relevant work exposure | Work mix and other prevention measures affect comparisons |
Retain the numerator, denominator and period for each measure. A lower incident count during a smaller or easier work program does not show improvement. Similarly, collecting more points per shift does not demonstrate better target interpretation.
Compare reasonably similar assignments and document concurrent changes in training, staffing, application methods and verification practices. A before-and-after result can be useful operational evidence without proving that GPS was the sole cause.
Pay attention to changed reporting behavior. A system that makes exceptions easier to document may initially produce more visible exceptions. Treat that as a reason to inspect the process, not an automatic sign that locating has become worse.
Buy a complete data workflow rather than a GPS label
The purchase specification should cover the complete deliverable, including equipment, installed options, software, services, export and review responsibilities. A receiver specification alone cannot confirm that the client’s required data will be available and correctly interpreted.
Ask for a representative acceptance demonstration that includes a clean observation, an unresolved observation, an above-ground feature and a controlled import into the destination system. Require the supplier to identify which fields are native, which are operator-entered and which require downstream processing.
There is also a documentation conflict worth resolving explicitly. The RTK-Pro product page describes optional Tx-Link, while the May 2026 handbook says factory Bluetooth and Tx-Link are mutually exclusive. Obtain configuration-specific written confirmation rather than assuming both capabilities are included.
Include the recurring operational requirements in the evaluation: correction access, cellular service, supported app/operating-system versions, training, data administration and any integration work. Request actual costs rather than inventing a payback period from a hypothetical number of avoided strikes.
Acceptance should establish what happens when pairing, positioning, upload or import does not work as intended. The crew needs a documented recovery path and a way to retain uncertainty. Test that path before committing the workflow to a time-sensitive project.
Finally, specify the handoff. The asset owner or construction team should receive understandable records, not just the only format the supplier finds convenient. A deliverable that opens successfully but loses identity evidence, missing values or review status has not met the intended requirement.
The damage prevention value comes from how records are used
Data logging and GPS can preserve the context of a locate, support repeat investigations and make discrepancies available to the people planning work. Their practical value depends on distinguishing measurements from interpretations and preserving those distinctions through review and export.
For U.S. excavation work, OSHA 1926.651(b) requires estimated utility locations before excavation and exact locations by safe, acceptable means as operations approach them. A digital map does not replace that requirement or the applicable local notification and site procedures.
The defensible approach is to capture the observation, define the coordinate and measured object, retain uncertainty, review the transfer and communicate what still needs verification. Evaluate the workflow through matched operational measures rather than unsupported promises of strike reduction.
The project deliverable should pair the recorded position with evidence another crew can interpret. Precise coordinates are useful only within that documented context.







