Skip to main content
Migration guide · gINT → AGS 4 · 2026

Leaving gINT: a working AGS 4 export, start to finish

gINT support ends on 31 December 2028. The move itself is not a project — it is one open file. This guide is the working version: which AGS groups carry your factual data, what TerraBrains maps them to, and the three checks to make before you trust the move. It assumes you have a gINT project open in front of you.

1 · Export the project as AGS 4

In gINT, export the project (not the library) to AGS 4. The result is a single text file with the factual record of the job. We do not read gINT .gpj project files directly — the AGS 4 export is the bridge, and it is an open standard so nothing is locked in.

2 · What is in the file, and where it goes

An AGS 4 file is a set of groups. Four carry the core of a borehole record; TerraBrains maps each one when you drop the file in.

AGS groupWhat it carriesWhat TerraBrains makes of it
LOCABorehole and trial-pit locations: ID, type, co-ordinates, ground level, final depth.A borehole on the project map, with its ground level and total depth.
GEOLThe stratum in each interval: top and base depth, geology, description, legend.The soil layers in the log, drawn to scale.
ISPTStandard Penetration Test readings: depth, blows per increment, the N value.The SPT series down the hole, kept beside the layers.
SAMPSamples taken: depth, type, reference, recovery.The sample register for the hole.

Also read where present: LLPL (lab tests by sample), CMPG (grading), GRAG (particle-size) and PTIM (in-situ tests) where present. The mapping happens in your browser; the file is not uploaded. Anything that needs a human eye — an unmatched column, a depth that does not line up — is flagged for your review before it is saved to a project. Nothing is imported silently.

3 · The three checks before you trust it

  1. Open one hole end to end. Pick the deepest borehole. Does the total depth match gINT? Do the layer boundaries (GEOL top and base) fall where the log shows them, and does the SPT series (ISPT) carry the right N at each depth?
  2. Count the holes. The number of LOCA entries should equal the number of holes in the job. A short count means the export was scoped to a selection.
  3. Check one level against the datum. Take a ground level and a layer depth and confirm they read against the same datum as your issued drawings.

4 · The mistakes that lose readings

Export the project, not the library

A gINT library export carries your templates and lookup lists, not the factual data of a job. Export the project itself as AGS 4 — the LOCA, GEOL, ISPT and SAMP groups are what move the boreholes.

Check the co-ordinate system before you map

LOCA co-ordinates mean nothing without their grid. Confirm the export used the grid you expect (national grid, local grid or lat/long) and that ground level is recorded against the datum your levels refer to. A wrong datum shifts every layer boundary.

Depths are down, not elevations

AGS records depth below ground level. TerraBrains keeps the same convention and can show elevation against the borehole’s ground level when you ask. If your levels are site-wide rather than per-hole, say so when you drop the file.

A photo of a log is a fallback, not a source

A PDF or a photograph of a paper log can be read, but it is read by AI and flagged for your review — never trusted silently. If the AGS export exists, use it; it is the factual record and carries the most information.

5 · Then the analysis is in the same place

Once the boreholes are in, the lab, the analysis and the signed report read the same record — nothing is retyped between the log and the report. That is the reason to move, and it is what the migration page checks for you before you sign up.

Ready to try it on a real file? Drop an AGS 4 export and see what we read, or read the short version.

Bring a file across and see it read.

An AGS 4 export moves your boreholes in minutes. The analysis and the signed report are then in the same place.