> 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/getting-started/user-interface.md). # The GeoDin user interface The GeoDin interface is organized around a hierarchical tree view on the left, a central methods ribbon, and key controls for graphics, help, and system settings. This page is a tour of that workspace: the panels you start from, how the tree is structured, the interface controls around it, and the methods you run on a selected object. Read it top to bottom for orientation, or jump to the reference tables for the data sections, controls, and shortcuts. ## Databases panel The **Databases** panel is the starting point of your work in GeoDin. Each database contains **Projects**, and each project consists of **Objects** (such as boreholes and locations), **Measurement Points**, and **Documents**. ### Database types GeoDin supports client-server databases, which can be hosted on a single computer or across a network. Databases are color-coded: * **Yellow** - network-level databases (shared by a group of users for collaboration) * **Blue** - local databases (accessible only to the individual user) {% hint style="info" %} GeoDin databases are based on Microsoft Access files. For other backend options, see the [Installation guide](/installation-and-licensing/express-installation.md). {% endhint %}
GeoDin Databases panel with the G1_ASTM_DEMO_LasVegas database expanded to show a project's Objects, Measurement points, and Documents branches

The Databases panel: each database opens into projects, and each project into its Objects, Measurement points, and Documents branches.

### Tree hierarchy and navigation The GeoDin tree hierarchy follows a consistent pattern: ``` Database > Project > Objects (boreholes/locations) > Data Management (General Data, Layer Data, Samples, Well Design Data, Data Sequences) > Measurement Data > Documents ``` The **Measurement Points** branch holds **Locations** and **Samples** sub-branches, each containing their own measurement records. Clicking different levels in the left-hand tree populates the central "methods" ribbon with actions applicable to the selected item. Right-clicking a tree item shows the same methods in a context menu (e.g., New Project, Close Database, Maintain, Optimize). {% hint style="info" %} Each borehole with measurement data is marked with a small blue sphere icon in the tree view. {% endhint %} A project's **Documents** area lives directly under the project level and can hold folders and files - cross-sections, PDFs, videos, or any other file type. ## System panel The **System** panel provides access to system-level configuration. Within this panel, you can access and edit pre-made dictionaries, data types, and object types - including those for G1 locations and AGS standards.
GeoDin System panel with the System configuration tree expanded and the system-level methods shown in the central ribbon

The System panel: the System configuration tree lists the configurable areas (system databases, object types, data types, dictionaries, fill patterns, queries), and the central ribbon shows the system-level methods that apply to the selected branch.

## Central ribbon When you select a location within a project, the central ribbon displays the available methods for that object. Methods are activated by **double-clicking** the method icon.
GeoDin object manager with borehole BH01 selected in the tree and its available methods listed in the central ribbon

With borehole BH01 selected in the tree, the central ribbon lists the methods available for it - from Data management to Check measurements. Double-click an icon to start a method.

## Beta design mode (opt-in) From GeoDin 15.5 (release 15.5.0.185, April 2026), an opt-in Beta design is available: a customizable title bar that unifies the top navigation, layout controls, and Help/Info in a single header. You can switch between the Beta and Classic design at any time from the title bar; the Classic design remains unchanged and is the default. Screenshots in this documentation show the Classic design unless noted. *** ## Reference: Interface controls ### Bottom-left controls | Button | Function | | ------------------- | ------------------------------------------------------------- | | **Layout Overview** | Quick view of available layouts for the current object type | | **Edit Graphics** | Opens the layout editor to modify or create graphic templates | ### Top-right controls | Button | Shortcut | Function | | ---------------- | -------- | ------------------------------------------ | | **GeoDin Help** | F1 | Opens context-sensitive help documentation | | **Information** | Alt+I | Shows version and license validity | | **SQL Protocol** | Alt+S | Opens the SQL protocol log | | **Log Folder** | Alt+H | Opens the log file directory | ### Inside the help window **F1** opens the help at the chapter describing the current function or option; **Alt+F1** shows the last viewed chapter instead. Close the help window with **Esc** or the **Hide help** button. The window has its own navigation: | Feature | How it works | | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | | Chapter tree | The structured view of all chapters in the upper-left section. Links inside chapter text appear as blue underlined writing and jump to the linked chapter | | History | The **arrow** buttons at the upper left move back and forward through previously viewed chapters; the **Last viewed theme** icon selects one from a menu | | **Search for** field | The lower-left area lists all chapters alphabetically; typing a term reduces the list to chapters whose names contain it, regardless of case or position | | Full-text search | Searches the contents of all chapters (case-insensitive). Matching chapters are added to the list, and the term is highlighted yellow in the opened chapter | | **Print** icon | Prints the current chapter | ## Reference: Understanding data management sections When you navigate to an object (borehole) in the tree, the following data sections are available under **Data Management**: | Section | Contents | | -------------------- | --------------------------------------------------------------------------------- | | **General Data** | Location metadata - coordinates, elevation, project information, classification | | **Layer Data** | Geological layer descriptions - stratigraphy, petrography, colors, consistency | | **Samples** | Physical samples taken from the borehole, with depth intervals | | **Well Design Data** | Casing, screens, backfill, piezometer installations | | **Data Sequences** | Continuous depth-indexed data (CPT traces, geophysical logs, custom measurements) | **Measurement Data** is accessed via the Measurement Points branch and contains test results (e.g., triaxial, consolidation, Atterberg limits) linked to specific samples or locations. For detailed information about each section, see: * [Creating Objects](/workspace-and-data-management/creating-objects.md) * [General Data](/workspace-and-data-management/creating-objects/general-data.md) * [Sample Data](/workspace-and-data-management/creating-objects/sample-data.md) * [Well Design Data](/workspace-and-data-management/creating-objects/well-design-data.md) * [Measurement Values](/workspace-and-data-management/working-with-measurement-data.md) ## Working with methods All available methods for the selected object(s) appear on the right-hand side of the object manager under **Methods**. To run a method, double-click its icon. Because many methods apply to either a single object or several selected objects, it is important to select the right objects before starting a method. **Example.** The method **Measurement data** is available for a single measurement point as well as for a group or query. With just one measurement point selected, only data for this point is loaded into the measurement data editor. If a group of measurement points (for example, a query) is selected, all the measurement data for the selected points is loaded. There are two main types of methods: ### Discrete methods A discrete method must be completed before further operations in the object manager are carried out, or another method is started. For example, when the method **Delete project** is chosen, the new window dialog allows the choice between carrying out the delete action or cancelling. While this window is open, you cannot choose another method nor select another object. ### Parallel methods Parallel methods remain active until they are ended by closing the method window. When a parallel method is active, you can select and start other methods in the object manager. Parallel methods retain their direct connection to the object manager and react to changes in object selection. An example is **Data management**: choose an object, double-click the method symbol, and the object is loaded in the editor for editing general data, borehole logs, and so on. If another object is chosen, it is automatically opened for editing - the editor does not have to be closed first. An unlimited number of parallel methods may be used concurrently. This means you can edit borehole data and its graphical presentation simultaneously. ### Selection-bound methods Some methods take a selection from the object manager on startup and then keep that selection even if you click elsewhere in the tree. The **Cross-section assistant** is the typical example: the initial boreholes shown in the assistant are those selected as a group when the method started. You can expand the selection from inside the method using the **Add** button or by dragging further objects into the method's window. ### Methods without a selection A handful of methods can be started directly from the task bar at the bottom of the object manager, without first selecting anything in the tree. **GeoDin-Graph** (the CAD module for creating drawings independent of any database object) is one example - you do not need any object selected to launch it. ### Switching between active methods Switching between active methods is done by clicking the method's symbol in the **Active Methods** toolbar. The method currently in use is highlighted by a blue frame. | Shortcut | Action | | ----------- | --------------------------------------------------------------------- | | **F8** | Switch to the method on the right | | **Ctrl+F8** | Switch to the method on the left | | **F9** | Maximize or minimize the object manager's Objects and Methods windows | | **Ctrl+F9** | Maximize or minimize both at once | For the complete list of shortcuts across all editors, see [Keyboard shortcuts](/getting-started/keyboard-shortcuts.md). On the right side of each method symbol, a small switch closes the method - even when the method is in the background. The **Close all methods** switch on the right side of the **Active Methods** toolbar closes every active method in one step. {% hint style="info" %} It is not necessary to shut down all methods before closing GeoDin. Selecting **File > Exit** (or **Alt+F4**) closes all active methods automatically; if any have unsaved changes, a save dialog appears first. {% endhint %} All methods available for a selected object are also available as a popup menu via right-click on the tree entry - the methods window does not need to be maximized to start a method. --- # 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/getting-started/user-interface.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.