> For the complete documentation index, see [llms.txt](https://docs.geodin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geodin.com/support/glossary.md). # Glossary Short definitions of the terms, file formats, and standards used throughout the GeoDin documentation. Where a German term is common in support conversations, it is shown in italics after the English term. Each entry links to the page that covers the topic in full - the definition here is only the starting point. | Term | Definition | | -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **AGS** | The UK-standard geotechnical data exchange format. GeoDin's AGS object type mirrors the AGS group and header structure, so imported files arrive with ground descriptions and nested measurement data in place. GeoDin supports AGS 4.0.4 and 4.1.1. See [AGS 4](/object-types/ags-4.md). | | **Borehole log** (*Bohrsaeule*) | The vertical graphic column of a borehole, drawn as a complex graphic element inside an object frame. See [Creating borehole logs](/visualization-layouts-and-reporting/creating-borehole-logs.md). | | **BS 5930** | The British ground description standard, available in GeoDin both as an object type and as a ground description standard. See [Object types](/object-types/object-types.md). | | **COM API** | GeoDin's automation interface for scripting and plug-ins. See [COM API overview](/integrations-and-plug-ins/overview-1.md). | | **Complex data type** | A data type that contains structured sub-data rather than single values, for example CPT or cyclic triaxial results. See [Data types](/concepts/data-types.md). | | **Coordinate system / EPSG** | Each location stores its coordinates plus a coordinate system, selected from the G1 EPSG dictionary of EPSG-coded reference systems. See [Coordinate systems and EPSG](/maps/coordinate-systems-and-epsg.md). | | **CPT** (cone penetration test) | An in-situ probing test that produces a continuous measurement series over depth. GeoDin stores CPT results as a data sequence. See [Data sequences and CPT](/workspace-and-data-management/working-with-measurement-data/data-sequences-and-cpt.md). | | **Cross-section** (*Profilschnitt*) | A vertical slice through the ground that displays borehole data projected onto a user-defined line of section. See [Creating cross-sections](/visualization-layouts-and-reporting/creating-cross-sections.md). | | **Custom data type** | A user-created data type with its own parameter names, formulas, and validations, identified by a unique three-character short name and stored in syslib so updates do not overwrite it. See [Object types (concepts)](/concepts/object-types.md). | | **Data sequence** (*Sondierung*) | The measurement value series held against a data type - the per-row records the measurement editor reads and writes. Covers CPT, SPT, and geophysical or chemical profiles. See [Data sequences and CPT](/workspace-and-data-management/working-with-measurement-data/data-sequences-and-cpt.md). | | **Data type** | Defines how specific geotechnical and laboratory test results are stored, structured, and visualized, identified by a name, short name, and long name. See [Data types](/concepts/data-types.md). | | **Data Type Manager** | The database-level tool for defining which data types and parameters are used in a database - the central configuration point for measurement data collection. See [Working with measurement data](/workspace-and-data-management/working-with-measurement-data.md). | | **Detection limit** | The threshold below which a lab value is flagged, recorded as a negative value or with a "<" additional character; affected cells are framed blue. See [Working with measurement data](/workspace-and-data-management/working-with-measurement-data.md). | | **Dictionary** (*Woerterbuch*) | A pre-made list that populates drop-down fields, storing a full text plus the short code that is actually saved. Each dictionary is a `.GSD` file in syslib. See [Dictionaries](/administration/dictionaries.md). | | **Dongle** (*Lizenzstecker*) | The hardware USB license key used by older GeoDin versions; a network dongle is shared over the LAN. Replaced by the license service. See [Configure network dongle access](/support/troubleshooting/configure-network-dongle-access-geodin-7-9.0.md). | | **DXF export** | Export of layouts as DXF vector geometry for editing in AutoCAD or other CAD software. See [DXF export](/exporting-data/dxf-export.md). | | **EN ISO 22475** | The European standard for geotechnical investigation and sampling documentation, supported by a dedicated object type. See [Geotechnical investigation EN ISO 22475](/object-types/geotechnical-investigation-en-iso-22475.md). | | **Exchange database** (*Austauschdatenbank*) | A special Access database that acts as a bridge: it reads the SEP3 table structure from an authority's file and exposes the objects so they can be copied into GeoDin. See [SEP3 exchange database](/importing-data/sep3-exchange-database.md). | | **Fill pattern** (*Fuellmuster*) | The graphical hatching used to represent geological layers and backfill materials. Source `.SGA` signature tables are compiled to `.SGN` files in syslib. See [Fill patterns and symbols](/administration/fill-patterns-and-symbols.md). | | **Filter (screen)** | The well design element representing the screened interval of a monitoring well; it generates a "filter" measurement point for groundwater sampling. See [Well design data](/workspace-and-data-management/creating-objects/well-design-data.md). | | **Formula** | An expression in GeoDin's own syntax used for calculations and validations in object types and measurement values. See [Formula basics](/data-analysis/formula-basics.md). | | **G1 location** | The general-purpose location object type, mainly used for boreholes and CPT locations; geological descriptions combine everything in one field. See [Object types (concepts)](/concepts/object-types.md). | | **GDOF / GDOB** | GeoDin Onsite's file formats: the `.gdof` form definition and `.gdob` data files that Onsite publishes alongside PDF and GeoDinML deliverables. See [GeoDinML import](/importing-data/geodin-ml-import.md). | | **GEF** | The CPT exchange format used in the Netherlands, supported natively for CPT data import. See [Data sequences import](/importing-data/data-sequences.md). | | **General data** (*Stammdaten*) | The headline record for a borehole or location: identifiers, project context, geometry, and drilling and sampling metadata that all downstream tables hang off. See [Borehole and location model](/concepts/borehole-and-location-model.md). | | **GeoDin Object Manager** (GOM) | The main object tree of the GeoDin workspace, from which objects, queries, and groups are selected and dragged into editors, layouts, and maps. See [The GeoDin user interface](/getting-started/user-interface.md). | | **GeoDin Ground** | The companion product for 3D ground modeling and virtual logs in Civil 3D, documented in its own section of [docs.geodin.com](https://docs.geodin.com). | | **GeoDin Onsite** | The field data collection app. It has no direct connection to a GeoDin database - published GeoDinML files are the bridge from field to office. See [GeoDinML import](/importing-data/geodin-ml-import.md). | | **GeoDinML** | GeoDin's structured XML data exchange format - the bridge between GeoDin Onsite in the field and GeoDin in the office, also used to distribute central project lists. See [GeoDinML import](/importing-data/geodin-ml-import.md). | | **gINT converter** | The GeoDin tool that converts data from gINT databases (the PROJECT, LITHOLOGY, POINT, and SAMPLING groups) into GeoDinML for import. See [Convert gINT databases to GeoDinML](/integrations-and-plug-ins/introduction/convert-gint-databases-to-geodinml.md). | | **Ground description standard** | The coding scheme that defines which properties and ground types are available for describing soil and rock, and how entries are translated for output. See [Ground description standards](/administration/ground-description-standards.md). | | **Ground type** | A compilation of the concrete properties needed to describe a ground material, defined by a property list and a unique GUID. See [Ground description standards](/administration/ground-description-standards.md). | | **GUID** | The unique identifier stored in the database for standards, ground types, and properties. Only GUIDs are saved, not names - a GUID must never change once in use. See [Ground description standards](/administration/ground-description-standards.md). | | **Interbedding** | A layer description condition where two or more ground types are entered for one layer, drawn as a horizontal periodic repetition of fill patterns. See [Ground description standards](/administration/ground-description-standards.md). | | **KA5 / KA6** (*Bodenkundlicher Aufschluss*) | Object types for the German soil survey guidelines (Bodenkundliche Kartieranleitung), 5th and 6th edition; KA6 has been mandatory in Germany since July 2024. See [KA6 Bodenkundlicher Aufschluss](/object-types/ka6-bodenkundlicher-aufschluss.md). | | **Layer data** (*Schichtdaten*) | The soil and rock layers of a location with their descriptions, entered layer by layer; the bottom depth of one layer is the top depth of the next. See [Layer and stratigraphy](/concepts/layer-and-stratigraphy.md). | | **Layer query** (*Schichtabfrage*) | A query on attributes of the layer description, which cannot be answered by plain SQL because descriptions are strings of codes; GeoDin decomposes them into single codes first. See [Layer queries](/data-analysis/layer-queries.md). | | **Layout** | A template that defines how object data is drawn onto a report page - borehole logs, cross-sections, site plans, and diagrams are all placed on layouts. See [Creating custom layouts](/visualization-layouts-and-reporting/creating-custom-layouts.md). | | **License Manager** | The web app of the license service, used to activate, update, and display licenses and active users. See [Using a license server](/installation-and-licensing/license-server.md). | | **License models** | GeoDin licenses come as Individual (single user), Professional (network, served by the license service), and Educational (academic use). See [Activate your license](/installation-and-licensing/activating-your-license.md). | | **License service** (*Lizenzdienst*) | The software licensing service that answers license requests from GeoDin clients over the network, replacing hardware dongles. See [Using a license server](/installation-and-licensing/license-server.md). | | **Measurement point** | The point or interval that measurement values attach to. Three kinds exist: object, undeveloped (typically a sample), and developed (permanent construction such as a piezometer filter). See [Working with measurement data](/workspace-and-data-management/working-with-measurement-data.md). | | **Measurement program** (*Messprogramm*) | A named, saved selection of parameters within a data type, for quickly applying the same parameter set again. See [Working with measurement data](/workspace-and-data-management/working-with-measurement-data.md). | | **Measurement values** (*Messwerte*) | Lab and field test results entered against a data type via the measurement value editor. See [Working with measurement data](/workspace-and-data-management/working-with-measurement-data.md). | | **Object** | A georeferenced record in the GeoDin database - a borehole, well, CPT location, or monitoring station - created from an object type. See [Creating objects](/workspace-and-data-management/creating-objects.md). | | **Object frame** (*Objektrahmen*) | The first required element on any layout: it connects the layout to database objects via drag and drop, and all complex graphic elements are placed inside one. See [Object frames](/visualization-layouts-and-reporting/creating-custom-layouts/object-frames.md). | | **Object type** (*Objektart*) | A data entry schema for the GeoDin database: predefined tables, input forms, dictionaries, fill patterns, and symbols, usually based on a standard such as EN ISO 22475. Object types must be installed before use. See [Object types](/object-types/object-types.md). | | **Parameter** | An individual measurable field of a data type, with a long and short name, field type, and defaults. See [Data sequences and CPT](/workspace-and-data-management/working-with-measurement-data/data-sequences-and-cpt.md). | | **Particle size distribution** (PSD, *Korngroessenverteilung*) | Grain size test data from sieve and hydrometer analysis, stored as a complex data type and displayable as a curve or bar chart. See [Data types](/concepts/data-types.md). | | **Piezometer** | A monitoring well instrument for groundwater levels; its filter is the classic developed measurement point. See [Well design data](/workspace-and-data-management/creating-objects/well-design-data.md). | | **Project** | Combines objects, measurement values, and documents that belong together, stored in database tables and accessed over a database connection. See [Working with projects](/workspace-and-data-management/working-with-projects.md). | | **Query Builder** | Defines a GeoDin sub-query as a set of node definitions - table list, FROM clause, conditions, result and display fields - which GeoDin combines into a full SQL statement. See [Query Builder reference](/data-analysis/query-builder-reference.md). | | **Sample / specimen** (*Probe*) | A physical sample taken at a location, each with a reference, depth interval, and sampling metadata; subsamples and specimens reference their parent sample. See [Sample and specimen model](/concepts/sample-and-specimen-model.md). | | **SEP1 / SEP3** | German geological data exchange standards; state authorities deliver borehole data as plain SEP3 Access databases, and SEP1 is the legacy predecessor. See [SEP3 exchange database](/importing-data/sep3-exchange-database.md). | | **Signature table** | The graphical notation mapping for borehole columns; each standard maps to a signature table such as DIN4023 or NENNORM. See [Translation style sheets](/administration/translation-style-sheets.md). | | **Site plan** (*Lageplan*) | A georeferenced plan of GeoDin objects in a configurable map frame, with automatic non-overlapping label placement. See [Creating site plans](/visualization-layouts-and-reporting/creating-site-plans.md). | | **Small / Large Data Model** (SDM / LDM) | The two storage models for measurement data: SDM stores one row per record with parameters as columns (up to 254 parameters); LDM stores one row per parameter value and is mandatory above 254. See [Working with measurement data](/workspace-and-data-management/working-with-measurement-data.md). | | **SPT** (standard penetration test) | An in-situ test recording blow counts (N-values), stored as a data type and depth-indexed data sequence. See [Data types](/concepts/data-types.md). | | **Stratigraphy** | The layering of soil and rock at a location, recorded as layer data with ground descriptions. See [Layer and stratigraphy](/concepts/layer-and-stratigraphy.md). | | **Sublayer** | A layer created inside a parent layer with its own from/to boundaries, rendered as a small break in the main fill pattern. See [Layer and stratigraphy](/concepts/layer-and-stratigraphy.md). | | **Symbol table** | Source `.SYA` symbol tables compiled to `.SYM` files in syslib, holding symbol definitions in text form. See [Fill patterns and symbols](/administration/fill-patterns-and-symbols.md). | | **Syslib** | The system library folder (`C:\ProgramData\GeoDin\System\`) storing dictionaries, compiled fill patterns, filters, and custom data types. See [Dictionaries](/concepts/dictionaries.md). | | **System configuration** | The central store of object types, data types, and dictionaries under the System tab; centrally distributed tables cannot be edited by users, while custom data types stay local. See [Object types](/object-types/object-types.md). | | **Text macro / variable text** | A layout element that places dynamic text resolving live database values at render time, used for headers and titles per object. See [Text macros and variable text](/visualization-layouts-and-reporting/creating-custom-layouts/text-macros-and-variable-text.md). | | **Translation style sheet** | Controls the translation of a ground type description into the text used for layer labels in graphics, with separate sheets for main layers and sublayers. See [Translation style sheets](/administration/translation-style-sheets.md). | | **Well design data** (*Brunnenausbau*) | Records the physical construction of a monitoring well: hole diameter, casing diameters and depths, filter and screen positions, and backfill materials. See [Well design data](/workspace-and-data-management/creating-objects/well-design-data.md). | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.geodin.com/support/glossary.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.