AGS 4.1 in and out
AGS files import through the same mapping and checks as live entry, and packages are generated from approved records only.
AGS 4.1 data management
Error
Blocking findings
Warning
Review required
FYI
Information
Product interface shown with demo project data.
AGS files import through the same mapping and checks as live entry, and packages are generated from approved records only.
Data integrity, engineering logic, AGS 4.1 reference checks and plausibility run on every record, continuously.
Official validation with the AGS python-ags4 checker, round-trip and file mechanics, structural integrity, and a pre-issue dictionary census — run on the exact copy that is issued.
Validation report, heading census, change log, flags log, transmittal, anomalies file and SHA-256 checksums.
Any value traces back to its test, sample, borehole and raw reading, and forward to the report table, AGS file and submission version.
G& is not the official AGS Validator. A clean conformance report is not a certification, an approval, or a guarantee that a submission will be accepted.
No. G& performs AGS 4.1 conformance checks against the official dictionaries and validates issued files with the AGS python-ags4 checker. The receiving party's validator remains terminal.
AGS 4.1 governs all formal deliverables. AGS 4.2 is reference-only: a 4.1 file leaves as 4.1.
Yes. A received AGS file imports through the same four checking layers, and every finding is listed with its group, heading and row.
A companion set: validation report, heading census, change log, flags log, transmittal, anomalies file and SHA-256 checksums.