AGS 4

1. Overview

The AGS 4 Standard consists of three different object types developed according to AGS 4.1.1 with additions from AGS 4.0.4. The default settings are AGS 4.1.1.

All three must be installed in GeoDin to ensure full functionality:

1. AGS 4 [AGSSTAND]: Includes general location data, geological layers, samples, well design information, object type tables, and data types.

2. AGS 4 LBSG - Testing schedule [AGSLBSG]: Used to define and manage project-specific testing schedules.

3. AGS 4 PREM - Project-specific time-related remarks [AGSPREM]: Used to record project-specific time-dependent events (e.g., “Heavy rainfall for two days; site flooded”).

1.1 Missing AGS groups in GeoDin

Some AGS groups are not stored in GeoDin because they are either automatically generated during the AGS export process or are not supported by GeoDin’s data model and therefore cannot be stored within the system.

• ABBR – automatically generated on AGS Export • DICT – not part of the GeoDin structure • FILE – automatically generated on AGS Export • TRAN – not imported into GeoDin; users must complete these values during the AGS Export in Step 4 • TYPE – automatically generated on AGS Export • UNIT – GeoDin provides its own dedicated unit dictionary (PU) • STND – not part of the GeoDin structure

1.2 General information for GeoDin

1.2.1 Parameters and Groups

Parameters or groups that are only included in AGS 4.1.1 and not in AGS 4.0.4 are marked with the note “(4.1)”.

Example: CTRG – Cyclic triaxial test [CTRG] is a new group for AGS 4.1.1.

1.2.2 Input Forms

GeoDin allows users to enter data using input forms (masks). GeoDin provides support for entering parameters. The description of the AGS parameter name can be found below the mask as a note containing the long field name and, in brackets, the short field name.

1.2.3 Grid View

When entering data via the grid view, users can switch between the long field name and the AGS short field name. To do this, the user clicks on the column heading with the right mouse button, and a menu bar appears, as shown in the image. Users can also use this menu bar to switch the unit view on and off.

1.2.4 Dictionaries

• GeoDin includes comprehensive dictionaries that store all AGS codes from the AGS 4.1.1 and AGS 4.0.4 standards.

• The following dictionaries are exceptions and are intentionally empty:

  • (AGS) Layer data: GEOL – Second geology code

  • (AGS) Layer data: GEOL – Geology code These must be populated with project-specific codes in accordance with AGS standards.

• Users can edit GeoDin dictionaries.

  • Once modified, dictionaries are not updated during an object type update, ensuring user changes are retained.

• The following database-specific dictionaries must be populated by user input:

  • (AGS) Testing schedule: LBSG – Schedule reference, used in data type LBST

  • (AGS) Monitoring installation: PIPE – Pipe reference, used in data type MONG These dictionaries are only usable once the required information has been entered into the database.

• In contrast to the AGS structure, GeoDin includes an additional EPSG dictionary to enable location display in:

  • Map preview

  • GeoDin Maps

  
• The following dictionaries are repeatedly used in GeoDin:

  • (AGS) Units: UNIT – Unit, defining all units used for data headings and data records

    • Used multiple times for all AGS types = PU

  • (AGS) Yes or No: YN

    • Used multiple times for all AGS types = YN

• The dictionary (AGS) Data type: PTST – Type of permeability test contains duplicate entries with different upper- and lower-case letters, reflecting differences between AGS 4.0 and AGS 4.1 standards.

• GeoDin does not allow spaces in dictionary codes.

  • AGS-standard codes containing spaces are converted to underscores within GeoDin.

  • This conversion is handled automatically by the importer and exporter, where it is reversed.

• Users can enter their own ABBR codes into GeoDin dictionaries.

  • During export, these codes are written to the ABBR group with their corresponding long texts.

  • Such entries are marked with “GeoDin” instead of “AGS4” in the ABBR_LIST heading.

1.2.5 Presentation with Fill Patterns

GeoDin uses fill patterns defined in the AGS dictionaries to visually represent geological layers and backfill materials in drilling logs. This enables clear graphical differentiation of materials and ensures consistent, AGS-compliant visual outputs.

Dictionaries used:

• (AGS) Layer data: GEOL – Legend code

• (AGS) Well design: BKFL – Backfill legend

2. Data structure of the GeoDin object types

The below image shows an extensive data structure for the GeoDin object types:

3. Object type AGS 4 [AGSSTAND]

The AGS 4 object type is the core structure for AGS data in GeoDin. It contains:

• General location data

• Geological layer descriptions

• Sampling information

• Well design details

• Supplementary object type tables

• Data types for all groups of the AGS 4.1.1 and AGS 4.0.4 standards

The user can find the AGS groups and the associated parameters in GeoDin in the following structure:

General data	Layer data	Samples	Well design	Object type tables
LOCA	GEOL	SAMP	HDIA	CDIA
	DETL		FLSH	CHIS
	DLOG		BKFL	HDPH
			PIPE	DREM
			FILT	DOBS
				HORN

All AGS groups except LBSG and PREM that are not listed above are implemented in GeoDin as data types. The complete list of AGS data types is provided in Chapter 6 – Data Types.

3.1 General data – Location details - LOCA

3.2 Layer data – GEOL, DETL, DLOG

3.2.1 Field geological description - GEOL

3.2.2 Stratum detail description - DETL

3.2.3 Driller geological description (4.1) - DLOG

The DLOG group represents the driller’s geological description according to AGS 4.1.1.

3.3 Samples - SAMP

3.4 Well design – HDIA, FLSH, BKFL, PIPE, FILT

3.4.1 Hole diameter - HDIA

3.4.2 Flushing details - FLSH

3.4.3 Backfill - BKFL

3.4.4 Monitoring installation pipe - PIPE

The user must create a Pipe reference entry in order to make it available in the Pipe reference dictionary and to use it for the Monitoring Installations and Instruments [MONG] data type.

The entries of the dictionary (AGS) Monitoring installation: PIPE - Pipe reference are only available, if the user creates an entry in the Monitoring installation pipe. The dictionary is database specific.

3.4.5 Filter details - FILT

Pipe reference in monitoring installation pipe (PIPE group) and in filter details should be identical. Pipe name in filter details is used as the name (monitoring point ID) in the MONG group.

3.5 Additional object type tables – CDIA, CHIS, HDPH, DREM, DOBS, HORN

Additional object type tables store advanced drilling information that supports detailed project documentation:

1. CDIA – Casing diameter

2. CHIS – Chiseling details

3. HDPH – Depth‑related hole information

4. DREM – Depth related remarks

5. DOBS – Drilling advancement observation and parameters

6. HORN – Hole orientation and inclination

3.5.1 Casing diameter - CDIA

3.5.2 Chiseling details - CHIS

3.5.3 Depth related hole information - HDPH

3.5.4 Depth related remarks - DREM

3.5.5 Drilling advancement observation and parameters - DOBS

3.5.6 Hole orientation and inclination - HORN

4. Object type AGS 4 LBSG - Testing schedule [AGSLBSG]

4.1 General data - Testing schedule - LBSG

A testing schedule object must be created so that its reference can be used in the Testing Schedule Details [LBST] data type records.

The dictionary (AGS) Testing schedule: LBSG – Schedule reference is database‑specific. Schedule references are only available if corresponding objects are created in the AGS 4 LBSG – Testing schedule object type.

Using the Add objects method at the level of the opened database, testing schedule objects can be copied from one database to another. Once copied, they are also available as schedule references for the Testing Schedule Details [LBST] data type.

5. Object Type AGS 4 PREM – Project-Specific Time-Related Remarks [AGSPREM]

5.1 General data - Project specific time related remarks - PREM

The AGS 4 PREM object allows users to document project‑specific, time‑dependent events such as delays, weather events, and site accessibility issues. These records form part of the project’s AGS‑compliant documentation.

6. Data types

6.1 General information

There are three types of measuring points used in the AGS object type:

• (AGS) Location [AGL]

• (AGS) Samples [AGS]

• (AGS) Screens / filter [AGF]

GeoDin includes 86 AGS data types, each linked either to:

• (AGS) Location [AGL], or

• (AGS) Samples [AGS]

There are currently no data types linked to (AGS) Screens / filter [AGF].

Naming Pattern

Each data type follows the naming pattern:

"(AGS) GROUPNAME" Example: “(AGS) AAVT”

Data types may include first-, second-, and third‑level sub data types, which provide a more detailed structure for specific measurements.

All data types are listed in the tables below.

Short Name Convention

The short name of each data type:

• consists of three letters

• usually uses the first three letters of the AGS group name

• if two groups would have identical short names, the third letter is replaced by the fourth to differentiate them

Measurement Programs

GeoDin provides measurement programs for the AGS data types. These programs correspond to the AGS version in use:

• AGS 4.1.1 (default)

• AGS 4.0.4

If differences exist between AGS 4.1.1 and AGS 4.0.4, GeoDin provides the corresponding version‑specific measurement program.

6.1.1 Location data types

A total of 28 data types are linked to Locations, including 18 sub‑data types.

(AGS) CORE	COR	Coring Information	CORTAB01
(AGS) DISC	DIS	Discontinuity Data	DISTAB01
(AGS) DCPG	DPG	Dynamic Cone Penetrometer Tests - General	DPGTAB01	DCPT
(AGS) DPRG	DRG	Dynamic Probe Tests - General	DRGTAB01	DPRB
(AGS) FGHG	FGG	Field Geohydraulic Testing - General (4.1)	FGGTAB01	FGHI FGHS	FGHT
(AGS) FRAC	FRA	Fracture Spacing	FRATAB01
(AGS) ICBR	ICB	In Situ California Bearing Ratio Tests	ICBTAB01
(AGS) IDEN	IDE	In Situ Density Tests	IDETAB01
(AGS) IFID	IFI	On Site Volatile Headspace Testing Using Flame Ionisation Detector	IFITAB01
(AGS) IPEN	IPE	In Situ Hand Penetrometer Tests	IPETAB01
(AGS) IPRG*	IPG	In Situ Permeability Tests - General (4.0.4)	IPGTAB01	IPRT*
(AGS) IRDX	IRD	In Situ Redox Tests	IRDTAB01
(AGS) IRES	IRE	In Situ Resistivity Tests	IRETAB01
(AGS) ISAG	ISG	Soakaway Tests - General	ISGTAB01	ISAT
(AGS) ISPT	ISP	Standard Penetration Test Results	ISPTAB01
(AGS) IVAN	IVA	In Situ Vane Tests	IVATAB01
(AGS) MONG	MOG	Monitoring Installations and Instruments	MOGTAB01	MOND
(AGS) PLTG	PLG	Plate Loading Tests - General	PLGTAB01	PLTT
(AGS) PMTG	PMG	Pressuremeter Test Results - General	PMGTAB01	PMTD PMTL
(AGS) PTIM	PTI	Boring/Drilling Progress by Time	PTITAB01
(AGS) PUMG	PUG	Pumping Tests - General	PUGTAB01	PUMT
(AGS) SCPG	SCG	Static Cone Penetration Tests - General	SCGTAB01	SCDG SCPP SCPT	SCDT
(AGS) TREM	TRE	Location Specific Time Related Remarks	TRETAB01
(AGS) WADD	WAD	Water Added Records	WADTAB01
(AGS) WETH	WET	Weathering	WETTAB01
(AGS) WGPG	WGG	Wireline Geophysics - General (4.1)	WGGTAB01	WGPT
(AGS) WINS	WIN	Window or Windowless Sampling Run Details	WINTAB01
(AGS) WSTG	WSG	Water Strike - General	WSGTAB01	WSTD

6.1.2 Sample data types

58 data types are linked to Samples, including 19 sub‑data types.

(AGS) AAVT	AAV	Aggregate Abrasion Tests	AAVTAB01
(AGS) ACVT	ACV	Aggregate Crushing Value Tests	ACVTAB01
(AGS) AELO	AEL	Aggregate Elongation Index Tests	AELTAB01
(AGS) AFLK	AFL	Aggregate Flakiness Tests	AFLTAB01
(AGS) AIVT	AIV	Aggregate Impact Value Tests	AIVTAB01
(AGS) ALOS	ALO	Los Angeles Abrasion Tests	ALOTAB01
(AGS) APSV	APS	Aggregate Polished Stone Tests	APSTAB01
(AGS) ARTW	ART	Aggregate Determination of the Resistance to Wear (micro-Deval)	ARTTAB01
(AGS) ASDI	ASD	Slake Durability Index Tests	ASDTAB01
(AGS) ASNS	ASN	Aggregate Soundness Tests	ASNTAB01
(AGS) AWAD	AWA	Aggregate Water Absorption Tests	AWATAB01
(AGS) CBRG	CBG	California Bearing Ratio Tests - General	CBGTAB01	CBRT
(AGS) CHOC	CHO	Chain of Custody Information	CHOTAB01
(AGS) CMPG	CMG	Compaction Tests - General	CMGTAB01	CMPT
(AGS) CONG	COG	Consolidation Tests - General	COGTAB01	CONS
(AGS) CTRG	CTG	Cyclic Triaxial Tests - General (4.1)	CTGTAB01	CTRC CTRS	CTRP	CTRD
(AGS) ECTN	ECT	Sample Container Details (4.1)	ECTTAB01
(AGS) ELRG	ELR	Environmental Laboratory Reporting (4.1)	ELRTAB01
(AGS) ERES*	ERE	Environmental Contaminant Testing (4.0.4)	ERETAB01
(AGS) ESCG	ESG	Effective Stress Consolidation Tests - General	ESGTAB01	ESCT
(AGS) FRST	FRS	Frost Susceptibility Tests	FRSTAB01
(AGS) GCHM	GCM	Geotechnical Chemistry Testing	GCMTAB01
(AGS) GRAG	GRG	Particle Size Distribution Analysis - General	GRGTAB01	GRAT
(AGS) IPID	IPI	On Site Volatile Headspace Testing by Photo Ionisation Detector	IPITAB01
(AGS) LBST	LBT	Testing Schedule Details	LBTTAB01
(AGS) LDEN	LDE	Density Tests	LDETAB01
(AGS) LDYN	LDY	Dynamic Testing	LDYTAB01
(AGS) LFCN	LFC	Laboratory Fall Cone Tests (4.1)	LFCTAB01
(AGS) LLIN	LLI	Linear Shrinkage Tests	LLITAB01
(AGS) LLPL	LLP	Liquid and Plastic Limit Tests	LLPTAB01
(AGS) LNMC	LNM	Water/Moisture Content Tests	LNMTAB01
(AGS) LPDN	LPD	Particle Density Tests	LPDTAB01
(AGS) LPEN	LPE	Laboratory Hand Penetrometer Tests	LPETAB01
(AGS) LRES	LRE	Laboratory Resistivity Tests	LRETAB01
(AGS) LSTG	LSG	Initial Consumption of Lime Tests - General	LSGTAB01	LSTT
(AGS) LSLT	LSL	Shrinkage Limit Tests	LSLTAB01
(AGS) LSWL	LSW	Swelling Index Testing	LSWTAB01
(AGS) LTCH	LTC	Laboratory Thermal Conductivity (4.1)	LTCTAB01
(AGS) LUCT	LUC	Laboratory Unconfined Compression Test (4.1)	LUCTAB01
(AGS) LVAN	LVA	Laboratory Vane Tests	LVATAB01
(AGS) MCVG	MCG	MCV Tests - General	MCGTAB01	MCVT
(AGS) PTST	PTS	Laboratory Permeability Tests	PTSTAB01
(AGS) RCAG	RAG	Rock Abrasiveness Tests - General (4.1)	RAGTAB01	RCAT
(AGS) RESG	RCG	Resonant Column Test - General (4.1)	RCGTAB01	RESC RESD RESS	RESP
(AGS) RCCV	RCV	Chalk Crushing Value Tests	RCVTAB01
(AGS) RDEN	RDE	Rock Porosity and Density Tests	RDETAB01
(AGS) RELD	REL	Relative Density Tests	RELTAB01
(AGS) RPLT	RPL	Point Load Testing	RPLTAB01
(AGS) RSCH	RSC	Schmidt Rebound Hardness Tests	RSCTAB01
(AGS) RSHR	RSH	Shore Scleroscope Hardness Tests	RSHTAB01
(AGS) RTEN	RTE	Tensile Strength Testing	RTETAB01
(AGS) RUCS	RUC	Rock Uniaxial Compressive Strength and Deformability Tests	RUCTAB01
(AGS) RWCO	RWC	Water Content of Rock Tests	RWCTAB01
(AGS) SHBG	SHG	Shear Box Testing - General	SHGTAB01	SHBT
(AGS) SUCT	SUC	Suction Tests	SUCTAB01
(AGS) TREG	TEG	Triaxial Tests - Effective Stress - General	TEGTAB01	TRET
(AGS) TRIG	TIG	Triaxial Tests - Total Stress - General	TIGTAB01	TRIT
(AGS) TNPC	TNP	Ten Per Cent Fines	TNPTAB01

6.1.3 List of sub-data types

CBT	(CBRT) California Bearing Ratio Tests - Data	California Bearing Ratio Tests - Data	CBTTAB01
CMT	(CMPT) Compaction Tests - Data	Compaction Tests - Data	CMTTAB01
COS	(CONS) Consolidation Tests - Data	Consolidation Tests - Data	COSTAB01
CTC	(CTRC) Cyclic Triaxial Tests - Consolidation	Cyclic Triaxial Tests - Consolidation (4.1)	CTCTAB01
CTD	(CTRD) Cyclic Triaxial Tests - Data	Cyclic Triaxial Tests - Data (4.1)	CTDTAB01
CTP	(CTRP) Cyclic Triaxial Tests - Derived Parameters	Cyclic Triaxial Tests - Derived Parameters (4.1)	CTPTAB01
CTS	(CTRS) Cyclic Triaxial Tests - Saturation	Cyclic Triaxial Tests - Saturation (4.1)	CTSTAB01
DPT	(DCPT) Dynamic Cone Penetrometer Tests - Data	Dynamic Cone Penetrometer Tests - Data	DPTTAB01
DRB	(DPRB) Dynamic Probe Tests - Data	Dynamic Probe Tests - Data	DRBTAB01
EST	(ESCT) Effective Stress Consolidation Tests - Data	Effective Stress Consolidation Tests - Data	ESTTAB01
FGI	(FGHI) Field Geohydraulic Testing - Instrumentation Details	Field Geohydraulic Testing - Instrumentation Details (4.1)	FGITAB01
FGS	(FGHS) Field Geohydraulic Testing - Test Results (per stage)	Field Geohydraulic Testing - Test Results (per stage) (4.1)	FGSTAB01
FGT	(FGHT) Field Geohydraulic Testing - Test Results	Field Geohydraulic Testing - Test Results (4.1)	FGTTAB01
GRT	(GRAT) Particle Size Distribution Analysis - Data	Particle Size Distribution Analysis - Data	GRTTAB01
IPT*	(IPRT) In Situ Permeability Tests - Data	In Situ Permeability Tests - Data (4.0.4)	IPTTAB01
IST	(ISAT) Soakaway Tests - Data	Soakaway Tests - Data	ISTTAB01
LST	(LSTT) Initial Consumption of Lime Tests - Data	Initial Consumption of Lime Tests - Data	LSTTAB01
MCT	(MCVT) MCV Tests - Data	MCV Tests - Data	MCTTAB01
MOD	(MOND) Monitoring Readings	Monitoring Readings	MODTAB01
PLT	(PLTT) Plate Loading Tests - Data	Plate Loading Tests - Data	PLTTAB01
PMD	(PMTD) Pressuremeter Test - Data	Pressuremeter Test Results - Data	PMDTAB01
PML	(PMTL) Pressuremeter Test Results - Individual Loops	Pressuremeter Test Results - Individual Loops	PMLTAB01
PUT	(PUMT) Pumping Tests - Data	Pumping Tests - Data	PUTTAB01
RAT	(RCAT) Rock Abrasiveness Tests - Data	Rock Abrasiveness Tests - Data (4.1)	RATTAB01
RCC	(RESC) Resonant Column Tests - Consolidation	Resonant Column Test - Consolidation (4.1)	RCCTAB01
RCD	(RESD) Resonant Column Tests - Data	Resonant Column Test - Data (4.1)	RCDTAB01
RCP	(RESP) Resonant Column Tests - Derived Parameters	Resonant Column Test - Derived Parameters (4.1)	RCPTAB01
RCS	(RESS) Resonant Column Tests - Saturation	Resonant Column Test - Saturation (4.1)	RCSTAB01
SCP	(SCPP) Static Cone Penetration Tests - Derived Parameters	Static Cone Penetration Tests - Derived Parameters	SCPTAB01
SCT	(SCPT) Static Cone Penetration Tests - Data	Static Cone Penetration Tests - Data	SCTTAB01
SDG	(SCDG) Static Cone Dissipation Tests - General	Static Cone Dissipation Tests - General	SDGTAB01
SDT	(SCDT) Static Cone Dissipation Tests - Data	Static Cone Dissipation Tests - Data	SDTTAB01
SHT	(SHBT) Shear Box Testing - Data	Shear Box Testing - Data	SHTTAB01
TET	(TRET) Triaxial Tests - Effective Stress - Data	Triaxial Tests - Effective Stress - Data	TETTAB01
TIT	(TRIT) Triaxial Tests - Total Stress - Data	Triaxial Tests - Total Stress - Data	TITTAB01
WGT	(WGPT) Wireline Geophysics - Readings	Wireline Geophysics - Readings (4.1)	WGTTAB01
WSD	(WSTD) Water Strike - Details	Water Strike - Details	WSDTAB01

7. Installation of the Plugins for Import and Export of AGS Files

Follow the process outlined here in Method 1 and select AGS to install the object type.

Users can install plugins on the System side of GeoDin, as shown below. By pressing the Connecting button, GeoDin displays a list of all available plugins.

If a plugin is already installed, it appears under Installed plugins.

System Requirements

• GeoDin.exe version 15.4 or higher

• .NET 8 Desktop Runtime or higher

Users running GeoDin versions 15.0 to 15.3 can update the GeoDin.exe directly from within GeoDin by using the “Update GeoDin” function on the System page.

When the AGS plugins are started and the required .NET runtime is not already installed, a message is displayed informing the user that the .NET Desktop Runtime must be downloaded and installed first. If the user confirms the prompt by selecting “Yes”, they are automatically redirected to the official Microsoft download page. From there, the user can download and install the required .NET Desktop Runtime to proceed with the plugin import/export process.

7.1 General

GeoDin stores dictionary entries as long texts in the database. During import, the GeoDin dictionaries are checked, and the corresponding long texts are written into the GeoDin database. During export, the exporter reviews the database contents and writes the appropriate codes into the AGS file.

Some official AGS codes contain spaces, which are not permitted in GeoDin dictionaries. To address this:

• In GeoDin dictionaries, spaces are replaced with underscores.

• During import, the importer converts AGS codes by replacing spaces with underscores.

• During export, the exporter converts underscores back to spaces to generate PA entries that comply with the AGS standard.

7.2 AGS Importer

The AGS Importer is available at the level of an open GeoDin database and at the level of a GeoDin project.

The AGS Importer guides users through a four‑step process:

Step 1 – AGS Import configuration: The user can choose between the standard formats AGS 4.1.1 or AGS 4.0.4. Information about the standard can be found in the TRAN group in the TRAN_AGS parameter of the AGS import files.

Checkbox: “Update existing data with uploaded AGS.”

• If all key fields are filled in, existing data will be replaced with the current data record.

• If all key fields are filled in, existing data will NOT be replaced with the current data set.

Empty key fields lead to multiple imports because no comparison can take place.

Checkbox: “Ignore AGS project identifiers.”

• Import the data into the selected project without comparing the PROJ group.

Step 2 – File selection: The user selects the AGS file(s) to be imported. It is possible to import multiple AGS files at the same time.

Importing multiple files for the same object:

1. If the data within the AGS files differs, the data from the last file will be written, provided that the checkbox “Update existing data with uploaded AGS” is selected.

2. If the checkbox is not selected, the data from the first file will be written to the database. The data from the following files will then no longer be written to the database unless the parameter is not yet assigned.

Step 3 – Validation: Before importing, a validator checks the AGS file and issues warnings if there are any problems. In this case, importing is not possible, and the file must first be modified to comply with the standard and the import process restarted.

Step 4 - Import: The database structure is written during the first import after creating a GeoDin database. Warnings can be output as a list after the import has been completed (e.g. dictionary entry does not exist in GeoDin).

Warning can be saved as a list for review.

7.3 AGS Exporter

The AGS Exporter is available at the level of a GeoDin project. Starting the method you can navigate thru the plugin.

The AGS Exporter creates a fully validated AGS file.

Step 1 – Select objects: The tool is loading all objects from the project. You can select all locations, deselect or filter by the object name. Once selected, the user can go to the next step.

It is important that the user selects not only the LOCA objects, but also the corresponding PREM and LBSG objects for the export.

Step 2 – AGS export configuration: The user must choose the AGS export configuration. The Standards AGS 4.0.4 and AGS 4.1.1 are available. By choosing one standard, all parameters according to the standard are exported. Currently, it is not possible to export user-defined parameters from data types. The user can also choose AGS groups for the export. By default, all groups are exported.

A check mark can be used to remove empty headings if the lines do not contain any data.

Step 3 – Project details: The user must insert mandatory project details for the AGS Export, like project identifier [PROJ_ID] (PRJ_ALIAS in GeoDin) and Project name [PROJ_NAME] (PRJ_NAME in GeoDin and read-only). These fields are marked with a star, read from the GeoDin database and can be changed by the user. All other fields are optional.

The PROJ group must be filled in by the user because most of the data (Headings) are not stored in GeoDin: Location of site [PROJ_LOC], Client name [PROJ_CLNT], Contractors name [PROJ_CONT], Project Engineer [PROJ_ENG], General project comments [PROJ_MEMO]

Step 4 – Transmission details: In the next, the user must insert the transmission details, like Producer [TRAN_PROD], Issue sequence reference [TRAN_ISNO], Recipient [TRAN_RECV] and Transmission status [TRAN_STAT]. The two fields Description [TRAN_DESC] and Remarks [TRAN_REM] are optional fields. The AGS Edition Reference [TRAN_AGS] is read from the Step 2 (AGS export configuration) and can only be changed by the user in Step 2.

The TRAN group must be filled in by the user because the data is not stored in GeoDin. Mandatory fields marked with * are filled in automatically and can be changed by the user.

By clicking on the Export button, the user must choose the path and the name for the export file.

Step 5 - Export: The export starts automatically. Once the export has been successfully completed, the user is provided with a link to the AGS export file. Clicking on the link, the file is shown in an editor.

During the export, the file is validated. Any deviations from the AGS standard are listed.

If an error is detected, the export is aborted with the error message: “The export could not be completed.” Example: The database contains data for version 4.1.1 and is exported as format 4.0.4