ISKRIT / Site investigation & geotechnics / AGS4 checker
Site investigation & geotechnics
AGS checker: line-by-line AGS4 file validation
The tool reads an AGS4 data file and checks it against the format rules: row syntax, group composition, data types, in-file dictionaries and key links. Every finding is tied to a file line and a rule number, so fixes go straight into the source file.
Standards
AGS Data Format v4.x: rules 1-5 (row syntax), 2b and 7 (group composition), 8 (data types), 10 (LOCA and SAMP keys), 13-17 (PROJ, TRAN, UNIT, ABBR, TYPE), 19 (group and heading names).
Input
An AGS4 file; checked on the server, nothing is stored.
Output
Verdict, errors and warnings with file line numbers, a group summary.
What it does
- Line-by-line report: line, rule, group, message
- Field and quoting syntax, GROUP/HEADING/UNIT/TYPE/DATA descriptors
- Data types against the declared TYPE row: 2DP, DT, YN and the rest
- Key links: LOCA_ID and the composite SAMP sample key
- Summary: groups, data rows, boreholes, samples, geology layers
Free and full version
Free
- Code-based calculations right in the browser
- Input validation and printable results
- Works instantly, no sign-up required
Full version
- Batch checking of multiple files
- Report export to XLSX
- Check history per project
- Hand-off to the lab processing and soil unit delineation tools
Questions
What counts as an error and what as a warning?
An error is a direct violation of a format rule: broken syntax, field count mismatch, a wrong data type, a reference to a non-existent borehole or sample. A warning is a doubtful spot that cannot be proven without the reference dictionary: a unit or data type missing from the in-file dictionaries, a heading outside the naming format.
Is the AGS standard dictionary checked?
No: the reference dictionary of groups and headings (rule 9) is not built in. The checker validates the dictionaries of the file itself: the TYPE, UNIT and ABBR groups, and heading names are checked against the naming format.
Is the file stored?
No: the check runs in memory, the content is not written anywhere or passed to third parties.