Skip to main content
← Resources

Guide / AGS 4.1

How to check an AGS 4.1 file before you issue it

Short answer

Check the file in four layers before it leaves your team: structure (groups, headings, units, types), integrity (keys, parents, orphans), engineering logic (depths, sequences, plausible values) and reference conformance (dictionary and client specification). Then run the client's own validator, which remains the final check.

Why a file that opens can still be rejected

Most AGS rejections are not syntax failures. A file can be well-formed and still carry a sample deeper than its hole, a test with no parent sample, or a code the client's dictionary does not recognise. Syntax checkers catch the first class of problem; engineers catch the rest, usually late.

The four-layer check

  1. 1. Structure

    Every group has its HEADING, UNIT and TYPE rows; headings belong to their group; data types and units match the declared rows; the TRAN group states the AGS version.

  2. 2. Integrity

    Key fields are unique; every child row has a parent (SAMP to LOCA, test groups to SAMP); no orphaned results; ABBR and UNIT entries exist for every code used.

  3. 3. Engineering logic

    Top depth is below or equal to base depth; strata are continuous; samples and tests sit inside their hole depth; SPT increments add up; values fall in plausible ranges.

  4. 4. Reference conformance

    Codes and headings conform to the AGS 4.1 dictionary and to any client-specific requirements. Record which reference version you checked against.

  5. 5. Client validator

    Run the client's nominated validator last. It is the terminal check; your own checks exist so it passes first time.

How G& handles this

G& runs these checks continuously as records are entered, not only at export, and keeps a census of each issue so the responsible engineer reviews exceptions rather than whole files. G& checks conformance against references; it does not certify files, and the client's validator remains final.

Questions

Is passing a syntax checker enough?
No. Syntax checks confirm the file is well-formed. Integrity and engineering-logic errors still cause rejections.
Does G& certify AGS files?
No. G& checks conformance against the AGS reference and client specifications. The client's validator remains the terminal check.