# 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”). Follow the process outlined [here](https://docs.geodin.com/navigating-the-geodin-workspace/object-types/installing) in Method 1 and select **“AGSSTAND\_Geotechnical Geoenvironmental Standard“** to install all three object types including the associated data types. #### 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 or colons (:)** in dictionary codes. * AGS-standard codes containing spaces are converted to **underscores (\_)** within GeoDin. * AGS-standard codes containing colons are converted to **minus (-)** 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**.
Data typeShortnameLongnameGeoDin Table1. level sub-data type2. level sub-data type
(AGS) CORECORCoring InformationCORTAB01
(AGS) DISCDISDiscontinuity DataDISTAB01
(AGS) DCPGDPGDynamic Cone Penetrometer Tests - GeneralDPGTAB01DCPT
(AGS) DPRGDRGDynamic Probe Tests - GeneralDRGTAB01DPRB
(AGS) FGHGFGGField Geohydraulic Testing - General (4.1)FGGTAB01

FGHI

FGHS

FGHT
(AGS) FRACFRAFracture SpacingFRATAB01
(AGS) ICBRICBIn Situ California Bearing Ratio TestsICBTAB01
(AGS) IDENIDEIn Situ Density TestsIDETAB01
(AGS) IFIDIFIOn Site Volatile Headspace Testing Using Flame Ionisation DetectorIFITAB01
(AGS) IPENIPEIn Situ Hand Penetrometer TestsIPETAB01
(AGS) IPRG*IPGIn Situ Permeability Tests - General (4.0.4)IPGTAB01IPRT*
(AGS) IRDXIRDIn Situ Redox TestsIRDTAB01
(AGS) IRESIREIn Situ Resistivity TestsIRETAB01
(AGS) ISAGISGSoakaway Tests - GeneralISGTAB01ISAT
(AGS) ISPTISPStandard Penetration Test ResultsISPTAB01
(AGS) IVANIVAIn Situ Vane TestsIVATAB01
(AGS) MONGMOGMonitoring Installations and InstrumentsMOGTAB01MOND
(AGS) PLTGPLGPlate Loading Tests - GeneralPLGTAB01PLTT
(AGS) PMTGPMGPressuremeter Test Results - GeneralPMGTAB01

PMTD

PMTL

(AGS) PTIMPTIBoring/Drilling Progress by TimePTITAB01
(AGS) PUMGPUGPumping Tests - GeneralPUGTAB01PUMT
(AGS) SCPGSCGStatic Cone Penetration Tests - GeneralSCGTAB01

SCDG

SCPP

SCPT

SCDT
(AGS) TREMTRELocation Specific Time Related RemarksTRETAB01
(AGS) WADDWADWater Added RecordsWADTAB01
(AGS) WETHWETWeatheringWETTAB01
(AGS) WGPGWGGWireline Geophysics - General (4.1)WGGTAB01WGPT
(AGS) WINSWINWindow or Windowless Sampling Run DetailsWINTAB01
(AGS) WSTGWSGWater Strike - GeneralWSGTAB01WSTD
**6.1.2 Sample data types** **58 data types** are linked to **Samples**, including **19 sub‑data types**.
Data typeShortnameLongnameGeoDin Table1. level sub-data type2. level sub-data type
(AGS) AAVTAAVAggregate Abrasion TestsAAVTAB01
(AGS) ACVTACVAggregate Crushing Value TestsACVTAB01
(AGS) AELOAELAggregate Elongation Index TestsAELTAB01
(AGS) AFLKAFLAggregate Flakiness TestsAFLTAB01
(AGS) AIVTAIVAggregate Impact Value TestsAIVTAB01
(AGS) ALOSALOLos Angeles Abrasion TestsALOTAB01
(AGS) APSVAPSAggregate Polished Stone TestsAPSTAB01
(AGS) ARTWARTAggregate Determination of the Resistance to Wear (micro-Deval)ARTTAB01
(AGS) ASDIASDSlake Durability Index TestsASDTAB01
(AGS) ASNSASNAggregate Soundness TestsASNTAB01
(AGS) AWADAWAAggregate Water Absorption TestsAWATAB01
(AGS) CBRGCBGCalifornia Bearing Ratio Tests - GeneralCBGTAB01CBRT
(AGS) CHOCCHOChain of Custody InformationCHOTAB01
(AGS) CMPGCMGCompaction Tests - GeneralCMGTAB01CMPT
(AGS) CONGCOGConsolidation Tests - GeneralCOGTAB01CONS
(AGS) CTRGCTGCyclic Triaxial Tests - General (4.1)CTGTAB01

CTRC

CTRS

CTRPCTRD
(AGS) ECTNECTSample Container Details (4.1)ECTTAB01
(AGS) ELRGELREnvironmental Laboratory Reporting (4.1)ELRTAB01
(AGS) ERES*EREEnvironmental Contaminant Testing (4.0.4)ERETAB01
(AGS) ESCGESGEffective Stress Consolidation Tests - GeneralESGTAB01ESCT
(AGS) FRSTFRSFrost Susceptibility TestsFRSTAB01
(AGS) GCHMGCMGeotechnical Chemistry TestingGCMTAB01
(AGS) GRAGGRGParticle Size Distribution Analysis - GeneralGRGTAB01GRAT
(AGS) IPIDIPIOn Site Volatile Headspace Testing by Photo Ionisation DetectorIPITAB01
(AGS) LBSTLBTTesting Schedule DetailsLBTTAB01
(AGS) LDENLDEDensity TestsLDETAB01
(AGS) LDYNLDYDynamic TestingLDYTAB01
(AGS) LFCNLFCLaboratory Fall Cone Tests (4.1)LFCTAB01
(AGS) LLINLLILinear Shrinkage TestsLLITAB01
(AGS) LLPLLLPLiquid and Plastic Limit TestsLLPTAB01
(AGS) LNMCLNMWater/Moisture Content TestsLNMTAB01
(AGS) LPDNLPDParticle Density TestsLPDTAB01
(AGS) LPENLPELaboratory Hand Penetrometer TestsLPETAB01
(AGS) LRESLRELaboratory Resistivity TestsLRETAB01
(AGS) LSTGLSGInitial Consumption of Lime Tests - GeneralLSGTAB01LSTT
(AGS) LSLTLSLShrinkage Limit TestsLSLTAB01
(AGS) LSWLLSWSwelling Index TestingLSWTAB01
(AGS) LTCHLTCLaboratory Thermal Conductivity (4.1)LTCTAB01
(AGS) LUCTLUCLaboratory Unconfined Compression Test (4.1)LUCTAB01
(AGS) LVANLVALaboratory Vane TestsLVATAB01
(AGS) MCVGMCGMCV Tests - GeneralMCGTAB01MCVT
(AGS) PTSTPTSLaboratory Permeability TestsPTSTAB01
(AGS) RCAGRAGRock Abrasiveness Tests - General (4.1)RAGTAB01RCAT
(AGS) RESGRCGResonant Column Test - General (4.1)RCGTAB01

RESC

RESD

RESS

RESP
(AGS) RCCVRCVChalk Crushing Value TestsRCVTAB01
(AGS) RDENRDERock Porosity and Density TestsRDETAB01
(AGS) RELDRELRelative Density TestsRELTAB01
(AGS) RPLTRPLPoint Load TestingRPLTAB01
(AGS) RSCHRSCSchmidt Rebound Hardness TestsRSCTAB01
(AGS) RSHRRSHShore Scleroscope Hardness TestsRSHTAB01
(AGS) RTENRTETensile Strength TestingRTETAB01
(AGS) RUCSRUCRock Uniaxial Compressive Strength and Deformability TestsRUCTAB01
(AGS) RWCORWCWater Content of Rock TestsRWCTAB01
(AGS) SHBGSHGShear Box Testing - GeneralSHGTAB01SHBT
(AGS) SUCTSUCSuction TestsSUCTAB01
(AGS) TREGTEGTriaxial Tests - Effective Stress - GeneralTEGTAB01TRET
(AGS) TRIGTIGTriaxial Tests - Total Stress - GeneralTIGTAB01TRIT
(AGS) TNPCTNPTen Per Cent FinesTNPTAB01
**6.1.3 List of sub-data types**
Sub-data typeLongnameGroup nameGeoDin Table
CBT(CBRT) California Bearing Ratio Tests - DataCalifornia Bearing Ratio Tests - DataCBTTAB01
CMT(CMPT) Compaction Tests - DataCompaction Tests - DataCMTTAB01
COS(CONS) Consolidation Tests - DataConsolidation Tests - DataCOSTAB01
CTC(CTRC) Cyclic Triaxial Tests - ConsolidationCyclic Triaxial Tests - Consolidation (4.1)CTCTAB01
CTD(CTRD) Cyclic Triaxial Tests - DataCyclic Triaxial Tests - Data (4.1)CTDTAB01
CTP(CTRP) Cyclic Triaxial Tests - Derived ParametersCyclic Triaxial Tests - Derived Parameters (4.1)CTPTAB01
CTS(CTRS) Cyclic Triaxial Tests - SaturationCyclic Triaxial Tests - Saturation (4.1)CTSTAB01
DPT(DCPT) Dynamic Cone Penetrometer Tests - DataDynamic Cone Penetrometer Tests - DataDPTTAB01
DRB(DPRB) Dynamic Probe Tests - DataDynamic Probe Tests - DataDRBTAB01
EST(ESCT) Effective Stress Consolidation Tests - DataEffective Stress Consolidation Tests - DataESTTAB01
FGI(FGHI) Field Geohydraulic Testing - Instrumentation DetailsField 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 ResultsField Geohydraulic Testing - Test Results (4.1)FGTTAB01
GRT(GRAT) Particle Size Distribution Analysis - DataParticle Size Distribution Analysis - DataGRTTAB01
IPT*(IPRT) In Situ Permeability Tests - DataIn Situ Permeability Tests - Data (4.0.4)IPTTAB01
IST(ISAT) Soakaway Tests - DataSoakaway Tests - DataISTTAB01
LST(LSTT) Initial Consumption of Lime Tests - DataInitial Consumption of Lime Tests - DataLSTTAB01
MCT(MCVT) MCV Tests - DataMCV Tests - DataMCTTAB01
MOD(MOND) Monitoring ReadingsMonitoring ReadingsMODTAB01
PLT(PLTT) Plate Loading Tests - DataPlate Loading Tests - DataPLTTAB01
PMD(PMTD) Pressuremeter Test - DataPressuremeter Test Results - DataPMDTAB01
PML(PMTL) Pressuremeter Test Results - Individual LoopsPressuremeter Test Results - Individual LoopsPMLTAB01
PUT(PUMT) Pumping Tests - DataPumping Tests - DataPUTTAB01
RAT(RCAT) Rock Abrasiveness Tests - DataRock Abrasiveness Tests - Data (4.1)RATTAB01
RCC(RESC) Resonant Column Tests - ConsolidationResonant Column Test - Consolidation (4.1)RCCTAB01
RCD(RESD) Resonant Column Tests - DataResonant Column Test - Data (4.1)RCDTAB01
RCP(RESP) Resonant Column Tests - Derived ParametersResonant Column Test - Derived Parameters (4.1)RCPTAB01
RCS(RESS) Resonant Column Tests - SaturationResonant Column Test - Saturation (4.1)RCSTAB01
SCP(SCPP) Static Cone Penetration Tests - Derived ParametersStatic Cone Penetration Tests - Derived ParametersSCPTAB01
SCT(SCPT) Static Cone Penetration Tests - DataStatic Cone Penetration Tests - DataSCTTAB01
SDG(SCDG) Static Cone Dissipation Tests - GeneralStatic Cone Dissipation Tests - GeneralSDGTAB01
SDT(SCDT) Static Cone Dissipation Tests - DataStatic Cone Dissipation Tests - DataSDTTAB01
SHT(SHBT) Shear Box Testing - DataShear Box Testing - DataSHTTAB01
TET(TRET) Triaxial Tests - Effective Stress - DataTriaxial Tests - Effective Stress - DataTETTAB01
TIT(TRIT) Triaxial Tests - Total Stress - DataTriaxial Tests - Total Stress - DataTITTAB01
WGT(WGPT) Wireline Geophysics - ReadingsWireline Geophysics - Readings (4.1)WGTTAB01
WSD(WSTD) Water Strike - DetailsWater Strike - DetailsWSDTAB01
### 7. Installation of the Plugins for Import and Export of AGS Files 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 version 15.4 or higher** * **.NET 8 Desktop Runtime or higher** Users running **GeoDin versions 15.0 to 15.3** can update **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](https://dotnet.microsoft.com/en-us/download/dotnet) 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 and colons**, which are **not permitted** in GeoDin dictionaries.\ To address this: * In GeoDin dictionaries, **spaces are replaced with underscores (\_)**. * In GeoDin dictionaries, **colons are replaced with minus symbol (-)**. * 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. {% hint style="danger" %} Note: The AGS Importer can automatically create the required database tables for AGS object types only when using a **Microsoft Access database** in GeoDin.\ If you are working with a **client–server database** and the AGS object types have not yet been registered, you must first create these tables manually via GeoDin. Ensure that the relevant user has **permission to create tables** in the client–server database. {% endhint %} **Creating AGS Database Tables in a Client–Server Database** 1. In GeoDin, Open a project in your client-server database and go to the “Objects“ node. Start the “New object“ method. 2. Select the object type “AGS 4“ \[AGSSTAND] and confirm with “OK“. GeoDin will now create the corresponding tables in your client-server database.\ You may cancel the data entry afterwards by clicking the “Cancel edits“ button (prohibition sign). 3. Repeat the process for the following object types to create all necessary AGS tables: * “AGS 4 LBSG – Testing schedule” \[AGSLBSG] * “AGS 4 PREM – Project specific time related remarks” \[AGSPREM] These steps only need to be performed once per client-server database. After all required tables have been created, you can proceed with the AGS import using the AGS Importer. **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.” * [x] 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.” * [x] 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 --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.geodin.com/object-types/ags-4.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.