GDRS INSIGHT · FIELD DATA QA/QC

Infrastructure Field Data Validation: Connecting Photos, GPS, Redlines and Project Records

How record-based correlation can turn separate field records into a traceable documentation workflow without confusing documentation review with surveying or field verification.

The difficult part of field documentation is often not collecting information. It is proving which record belongs to which asset, location, station, drawing, and project change.

Field records arrive in different forms

A construction team may have GPS coordinates, photos, redline notes, daily production records, KMZ/KML features, spreadsheets, handhole or reel lists, repair notes, and drawing references. Each source may be useful on its own, but closeout and QA/QC become harder when those records cannot be confidently related to one another.

Record-based validation asks a narrower and more defensible question: Do the authorized records agree with the documentation being prepared, and where do they conflict or remain incomplete?

A five-part correlation workflow

1. Identify the source

Record which drawing, KMZ/KML, spreadsheet, field note, photo set, or other authorized source supports the item being reviewed.

2. Normalize identifiers

Check asset names, span/reel identifiers, station labels, dates, and other fields so the same item is not represented under inconsistent naming.

3. Relate location and project reference

Where the project framework supports it, connect the field coordinate or mapped feature to the applicable route, station, drawing page, or asset reference.

4. Compare sources

Review whether the authorized records agree on identifiers, location context, stationing, drawing relationship, and documentation status.

5. Log exceptions

Do not silently choose one source when two records disagree. Preserve the conflict so the responsible project party can resolve it.

Example: one handhole, four records

Suppose a handhole appears in a field coordinate list, a photo folder, a KMZ, and a redline drawing. The coordinate and KMZ location are close, but the asset number on the photo differs from the asset number on the redline. A documentation workflow should not simply pick the cleaner value. It should preserve the source references, identify the mismatch, and route the exception for clarification.

Illustrative Documentation Check
Field recordKMZRedlineStatusHH-012HH-012HH-021Exception — identifier conflict

Example only. Real project handling depends on the authorized records, scope, and responsible reviewer.

What “validation” means in this context

GDRS can validate whether a deliverable consistently reflects the authorized source records and agreed project-reference framework. That can include checking required fields, source links, identifiers, drawing relationships, station references, duplicates, missing information, and conflicting records.

It does not mean independently proving the physical field position of an asset. A GPS coordinate supplied by a project team remains a supplied coordinate unless a qualified party establishes something more.

Useful inputs for record-based QA/QC

  • Current drawing/as-built set.
  • Existing KMZ/KML or GIS export.
  • Field coordinates or asset list.
  • Photos with available identifiers, timestamps, or location context.
  • Existing redlines and construction-change records.
  • Daily/production records relevant to the documentation scope.
  • Client naming, folder, or closeout requirements.

Outputs can make uncertainty visible

A strong closeout or reference deliverable is not one that hides uncertainty. It is one that separates confirmed source relationships from unresolved questions. Depending on scope, that may include a QA/QC exception log, unmatched-item list, missing-source list, revision record, or comments that identify where client clarification is required.

When record-based correlation is most useful

Before closeout production

Identify missing or contradictory source information before it becomes embedded in final deliverables.

During redline preparation

Connect documented field changes to the appropriate drawing, station, or asset reference.

During KMZ/KML cleanup

Check whether names, layers, asset IDs, and source references are consistent with the authorized project records.

During handoff QA/QC

Confirm that the final package reflects the agreed records while keeping unresolved exceptions visible.

Important: GDRS field-data validation is documentation and record correlation. It is not land surveying, utility locating, SUE, engineering certification, or independent field verification.
Explore GDRS QA/QC Geospatial Reference Services Request a Project Review