Ensuring Reliable Geotechnical Data Exchange Through Effective QA/QC
The AGS (Association of Geotechnical and Geoenvironmental Specialists) data format has become one of the most widely used standards for exchanging geotechnical, geological, geoenvironmental, and laboratory data. Across infrastructure, transportation, mining, environmental, and construction projects, AGS files enable organizations to transfer borehole information, laboratory results, groundwater observations, and site investigation data between different software systems without relying on paper reports or manual data entry.
While AGS significantly improves interoperability, importing AGS files is not simply a matter of loading data into a database. Differences in AGS versions, coding practices, project standards, software implementations, and data quality can introduce errors that compromise the reliability of the resulting database.
Without proper validation procedures, organizations may unknowingly import incomplete records, invalid coordinates, inconsistent lithology descriptions, duplicate samples, or incorrect laboratory results. These issues can affect engineering decisions, reporting accuracy, regulatory compliance, and overall data quality.
To maximize the benefits of AGS data exchange, organizations should implement structured import and validation workflows that combine automated checks with human review.
This article explores best practices for importing and validating AGS files, focusing on schema validation, data mapping, error handling, and QA workflows.
Why AGS Validation Matters
AGS was designed to improve consistency and interoperability, but the standard itself does not guarantee that every AGS file is error-free.
An AGS file may contain:
- Missing fields
- Invalid codes
- Incorrect coordinates
- Duplicate records
- Formatting issues
- Incomplete laboratory data
- Broken relationships between datasets
If these issues are imported directly into a geological database, they can propagate throughout reports, models, and analyses.
Validation ensures that data is trustworthy before it becomes part of the organization’s permanent records.
Understanding the AGS Structure
Before discussing validation procedures, it is important to understand the structure of an AGS file.
AGS data is organized into:
Groups
Logical collections of related information.
Examples:
- LOCA (Location Data)
- GEOL (Geology)
- SAMP (Samples)
- ISPT (SPT Data)
- WELL (Well Information)
Fields
Individual data elements within each group.
Examples:
- Borehole ID
- Sample depth
- Lithology code
- Recovery percentage
Relationships
Links between datasets.
Examples:
- Samples linked to boreholes
- Laboratory tests linked to samples
- Monitoring data linked to wells
Maintaining these relationships is critical during import.
Schema Validation
The first step in any AGS import workflow should be schema validation.
Schema validation verifies that the file complies with the expected AGS format and structure.
What Is Schema Validation?
Schema validation evaluates whether:
- Required groups exist
- Required fields are present
- Field names are correct
- Data types are valid
- Relationships follow AGS rules
Think of schema validation as verifying that the file is structurally correct before evaluating the data itself.
Common Schema Issues
Examples include:
| Issue | Example |
|---|---|
| Missing Group | GEOL group absent |
| Invalid Field Name | BH_ID instead of LOCA_ID |
| Incorrect Data Type | Text entered into numeric field |
| Missing Mandatory Field | Borehole identifier omitted |
| Unsupported AGS Version | AGS 3.x imported into AGS 4.x workflow |
These issues should be detected before import proceeds.
Version Compatibility
One of the most common challenges involves AGS version differences.
Organizations may encounter:
- AGS 3.1
- AGS 3.1a
- AGS 4.0
- AGS 4.1
- AGS 4.1.1
Field definitions and group structures may vary between versions.
Import systems should identify the AGS version automatically and apply the appropriate validation rules.
Data Mapping
Once schema validation is complete, the next step is data mapping.
Data mapping determines how AGS fields correspond to the target database structure.
Why Data Mapping Is Important
No two databases are exactly alike.
An organization’s internal database may use:
| AGS Field | Internal Field |
| LOCA_ID | BoreholeID |
| LOCA_NATE | Northing |
| LOCA_NATN | Easting |
| GEOL_DESC | Lithology |
Mapping ensures that imported data is stored correctly.
Standardized Mapping Rules
Organizations should establish documented mapping rules.
Benefits include:
- Consistency
- Repeatability
- Easier troubleshooting
- Reduced import errors
Mapping should be maintained as part of the organization’s QA documentation.
Controlled Vocabularies
Many AGS files use project-specific terminology.
Examples:
- Clay
- CLAY
- CL
- Firm Clay
Organizations should map these values to standardized classifications whenever possible.
This improves consistency across projects.
Error Handling
Even well-structured AGS files may contain data issues.
Effective error handling prevents bad data from entering production databases.
Types of Errors
Errors generally fall into several categories.
Critical Errors
Critical errors prevent reliable import.
Examples:
- Missing borehole identifiers
- Invalid coordinates
- Corrupted files
- Missing mandatory groups
Imports should stop until these issues are resolved.
Validation Errors
Validation errors indicate data quality problems.
Examples:
- Sample depths exceed borehole depth
- Recovery greater than 100%
- Invalid lithology codes
These records should be flagged for review.
Warnings
Warnings identify unusual but potentially acceptable situations.
Examples:
- Missing optional fields
- Rare lithology classifications
- Unusual groundwater observations
Warnings should be reviewed but may not block import.
Informational Messages
Informational messages document non-critical observations.
Examples:
- Optional group omitted
- Default value applied
- Legacy code converted
These messages improve transparency.
Automated Validation Rules
After import, additional QA/QC validation should occur.
Modern geological databases often perform hundreds of automated checks.
Borehole Validation
Examples include:
- Duplicate borehole IDs
- Invalid coordinates
- Elevation inconsistencies
- Missing collar data
Lithology Validation
Checks may include:
- Overlapping intervals
- Gaps in intervals
- Invalid classifications
- Missing descriptions
Sampling Validation
Examples include:
- Sample depths outside borehole limits
- Duplicate sample numbers
- Missing recovery values
Geotechnical Validation
Checks may include:
- RQD greater than recovery
- Invalid SPT values
- Incorrect test depths
Groundwater Validation
Examples include:
- Water level above ground surface
- Duplicate readings
- Missing measurement dates
These checks help ensure imported data remains reliable.
QA Workflows
Validation alone is not enough.
Organizations should implement formal QA workflows that combine automated validation with human oversight.
Recommended Workflow
A structured AGS import process may include:
Step 1 – File Receipt
Receive AGS file from consultant, contractor, or laboratory.
Step 2 – Schema Validation
Verify AGS structure and version compliance.
Step 3 – Data Mapping
Map AGS fields to internal database fields.
Step 4 – Import
Load data into a staging environment.
Step 5 – Automated Validation
Execute QA/QC rules.
Step 6 – Technical Review
Review warnings and exceptions.
Step 7 – Approval
Approve validated records.
Step 8 – Production Import
Move approved data into the production database.
This workflow minimizes risk while maintaining efficiency.
Audit Trails and Traceability
Every AGS import should be traceable.
Organizations should record:
- File name
- Source organization
- Import date
- User performing import
- Validation results
- Approval records
This information becomes valuable during audits, investigations, and regulatory reviews.
Import History Records
A typical import log may include:
| Field | Example |
| File Name | SiteInvestigation.ags |
| AGS Version | 4.1.1 |
| Import Date | 2026-06-10 |
| Imported By | J. Smith |
| Errors | 2 |
| Warnings | 8 |
| Status | Approved |
These records support accountability and quality management.
Common AGS Import Challenges
Several issues frequently occur during AGS imports.
Examples include:
Inconsistent Coding
Different consultants use different classification systems.
Legacy AGS Versions
Older projects may not match current standards.
Missing Metadata
Coordinate systems or datum information may be absent.
Duplicate Data
Repeated imports may create duplicate records.
Custom Fields
Organizations sometimes add non-standard AGS fields.
Import workflows should account for these possibilities.
Best Practices for AGS Data Quality
Organizations can significantly improve AGS import reliability by following several best practices.
Validate Before Import
Never load unvalidated AGS files directly into production databases.
Use Staging Areas
Review imported data before approval.
Maintain Mapping Standards
Document and regularly update field mappings.
Automate QA/QC Rules
Reduce reliance on manual checking.
Preserve Import Logs
Maintain traceability for all imported datasets.
Require Technical Review
Human expertise remains essential for identifying geological inconsistencies.
Monitor Version Compatibility
Support multiple AGS versions where necessary.
The Future of AGS Validation
As geotechnical databases become increasingly sophisticated, AGS import workflows are evolving.
Emerging capabilities include:
- Automated schema verification
- AI-assisted anomaly detection
- Real-time validation
- Digital approval workflows
- Audit-ready reporting
- Integration with AGS and DIGGS standards
These advancements will further improve data quality while reducing manual effort.
Conclusion
AGS has become a cornerstone of modern geotechnical data exchange, but successful implementation depends on more than simply importing files. Effective schema validation, structured data mapping, robust error handling, and comprehensive QA workflows are essential for ensuring that imported information remains accurate, reliable, and defensible. By combining automated validation with technical review, organizations can improve data quality, reduce import errors, strengthen regulatory compliance, and maximize the value of their geological databases. As digital geotechnical workflows continue to expand, well-designed AGS validation processes will remain a critical component of professional borehole data management.