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.
- 1Identify authorized source records and alignment.
- 2Build the station, sheet, asset, and source-reference structure.
- 3Publish 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.
- 1Receive the authorized coordinate/asset record.
- 2Relate it to the approved project reference framework.
- 3Document the derived STA/sheet/source relationship and applicable limitations.
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.
Reference accuracy follows the source framework.
Related GDRS Insight
Fiber geospatial reference layers
See how STA, KMZ/KML, as-built sheets, assets, and source records can be connected.
Field data validation workflow
See how coordinates, photos, redlines, asset IDs, and project records can be correlated without overstating field certainty.
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.