GEOSPATIAL REFERENCE & DATA SERVICES

Connect map location to STA, sheets, assets, source records, and project context.

GDRS organizes authorized infrastructure records into structured geospatial reference layers and data indexes that help field and office teams move between the map and the project record more efficiently.

Reference layers built around practical project questions.

KMZ/KML Operational Reference Layers

Organize routes, assets, construction features, status, stationing, sheet references, and source information into field-friendly folders and descriptions.

STA-Linked Geospatial Layers

Relate project features to the applicable station or chainage reference, drawing sheet, source record, and available crossing or utility information.

As-Built Sheet Reference Layers

Connect mapped locations to the applicable drawing/page references so users can move from the field view back to the source record.

Utility & Crossing Reference Layers

Extract and organize utility, bore, casing, road, railroad, bridge, structure, depth, and crossing references shown in authorized project records.

Data Conversion & Asset Indexing

Standardize authorized PDF, KMZ/KML, spreadsheet, drawing-derived, and GIS information into consistent features, attributes, indexes, and agreed exchange formats.

Photo & Field-Evidence Indexing

Organize authorized timestamped or GPS-enabled photos and supporting records by asset, location, station, date, work item, or closeout requirement.

A two-way reference workflow.

Existing records → geospatial reference

Stationing, as-built drawings, utility/crossing information, and project records are connected to mapped locations.

  1. 1
    Identify authorized source records and alignment.
  2. 2
    Build the station, sheet, asset, and source-reference structure.
  3. 3
    Publish the agreed reference layer and index.

New field coordinate → project reference

A new coordinate or asset can be referenced back into the established project stationing/as-built framework when sufficient source information is available.

  1. 1
    Receive the authorized coordinate/asset record.
  2. 2
    Relate it to the approved project reference framework.
  3. 3
    Document the derived STA/sheet/source relationship and applicable limitations.
FIELD DATA VALIDATION & CORRELATION

Validate infrastructure field data against the authorized project record.

GDRS can compare supplied field coordinates, asset records, photos, identifiers, station references, KMZ/KML features, and as-built information to identify whether the documentation agrees, conflicts, or needs follow-up.

Cross-source reconciliation

Relate field-supplied records to the applicable route, STA or chainage, as-built sheet, asset ID, and source reference where the project framework supports the relationship.

Documentation QA/QC

Check naming, identifiers, source links, geometry context, required fields, duplicates, and missing or conflicting records without converting uncertainty into an unsupported clean result.

Exception visibility

Flag records that are unreadable, unmatched, unsupported, inconsistent, or outside the available source framework so the responsible project party can resolve them.

Important: In this context, validation means record-based correlation and documentation QA/QC. It is not land surveying, utility locating, field verification, engineering certification, or a statement that an asset is physically located exactly where a supplied record shows it.

Reference accuracy follows the source framework.

Station references: Derived from the authorized alignment, drawings, controls, and other project records supplied or approved for the assignment. They are not a substitute for survey control or field verification.
Utility references: Record-based information shown in authorized project records. It does not constitute a utility locate, SUE determination, excavation clearance, or statement of actual field position.

Related GDRS Insight

Fiber geospatial reference layers

See how STA, KMZ/KML, as-built sheets, assets, and source records can be connected.

Read the Insight

Field data validation workflow

See how coordinates, photos, redlines, asset IDs, and project records can be correlated without overstating field certainty.

Read the Insight

Need a reference layer—or a closeout file that carries the same source context?

Start with the existing records and the decisions your field, construction, GIS, closeout, or operations team needs the output to support.

Request a Project Review