> 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/object-types/object-types.md).

# Object Types Overview

GeoDin uses *object types* to represent various standards for recording drilling data or general geodata.\
\
An object type can be regarded as a data entry schema for the GeoDin database. It includes:

* Predefined database tables
* A predefined set of input forms
* Dictionaries for standardized terminology
* Fill patterns and symbols for standardized representation

These components are tailored to meet relevant standards and configured for specific use cases.

## Features

In GeoDin, the acquisition of drilling data or general geodata is always linked to an **object type**.\
The object type determines:

* Which **input forms** and **dictionaries** are available
* The **fill patterns and symbols** used for visualization
* The **structure of associated tables** in your GeoDin databases

Each object type is configured for specific purposes and based on recognized standards such as **EN ISO 22475**, **ISO 14688/14689**, or **BS 5930:1999**.

## Handling Object Types

<figure><img src="/files/JH8ryu6ofpyPh1AZThSz" alt=""><figcaption><p>The <strong>System</strong> tab with <strong>Object types</strong> expanded under System configuration: the installed object types (DOC and G1 families) are listed on the left, and the <strong>Install</strong>, <strong>Deinstall object types</strong>, and <strong>Export</strong> method buttons are on the right.</p></figcaption></figure>

* GeoDin includes predefined object types by default.
* Additional object types can be installed via the **System** tab.
* Installed object types can be updated or removed in the application.
* Files for each object type are stored in the **Syslib** directory.
* Properties (version, dictionaries, input forms, symbols) are visible under **System**.
* Dictionaries can be customized or extended for most object types.

## Choosing an Object Type

* Object types cannot usually be converted - Please note to choose carefully before data acquisition.
* Explore demo databases to check suitability.
* Discuss the choice with clients before starting.
* For corrections or change requests to existing object types, or to discuss a custom object type, please contact **GeoDin Client Success** at <geodinclientsuccess@fugro.com>

***

## Reference: Available object types

The table below lists the object types GeoDin can record against and the capabilities each one supports (multilingual dictionaries, layer data, EPSG coordinate references, samples, well design, data sequences, meta data, customisability, and Fugro-supplied types), grouped by domain - Standard, Environment, Geotechnical, Water, and Documents.

<table><thead><tr><th width="149.111083984375">Object type</th><th>Multilingual</th><th>Layer data</th><th>EPSG</th><th>Samples</th><th>Well design</th><th>Data sequences</th><th>Meta data</th><th>Customisable</th><th>Fugro</th></tr></thead><tbody><tr><td><strong>Standard</strong></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>BS 5930</td><td>x</td><td>x</td><td>x</td><td>x</td><td>x</td><td></td><td></td><td></td><td></td></tr><tr><td>EN ISO 22475</td><td>x</td><td>x</td><td>x</td><td>x</td><td>x</td><td>x</td><td></td><td></td><td></td></tr><tr><td>KAS</td><td>x</td><td>x</td><td>x</td><td>x</td><td>x</td><td></td><td></td><td></td><td></td></tr><tr><td>SEP 1</td><td>x</td><td>x</td><td>x</td><td>x</td><td>x</td><td></td><td></td><td></td><td></td></tr><tr><td>SEP 3</td><td>x</td><td>x</td><td>x</td><td>x</td><td>x</td><td></td><td></td><td></td><td></td></tr><tr><td><strong>Environment</strong></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>Contaminated site investigation</td><td>x</td><td>x</td><td>x</td><td>x</td><td></td><td>x</td><td></td><td></td><td></td></tr><tr><td>Climate measurement station</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>x</td></tr><tr><td><strong>Geotechnical</strong></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>UGS</td><td>x</td><td>x</td><td>x</td><td>x</td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>GTS</td><td>x</td><td>x</td><td>x</td><td>x</td><td></td><td>x</td><td></td><td></td><td></td></tr><tr><td>AGS</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td><strong>Water</strong></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>Well</td><td>x</td><td>x</td><td>x</td><td>x</td><td>x</td><td></td><td></td><td></td><td></td></tr><tr><td>Groundwater Well gallery</td><td>x</td><td>x</td><td>x</td><td>x</td><td>x</td><td></td><td></td><td>x</td><td></td></tr><tr><td>Waterworks</td><td>x</td><td>x</td><td>x</td><td>x</td><td></td><td></td><td></td><td></td><td></td></tr><tr><td><strong>Documents</strong></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>Document</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>x</td></tr><tr><td>GeoDIN graphic</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>x</td></tr><tr><td>GeoDIN map</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>x</td></tr><tr><td>GeoDIN map layer</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>x</td></tr><tr><td>Photo</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>x</td></tr><tr><td>Report</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>x</td></tr><tr><td>Image with depth information</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>x</td></tr></tbody></table>


---

# 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/object-types/object-types.md?ask=<question>&goal=<endgoal>
```

`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.