> 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/concepts/dictionaries.md).

# Dictionaries

GeoDin dictionaries - the coded value lists behind drop-down fields

Dictionaries are pre-made lists that populate drop-down fields (marked with a `?` symbol to the right of the field).

## How dictionary values are stored

Dictionary values have two representations: full text (e.g. "Cone Penetration Testing") and short code (e.g. "CPT") - the short code is what GeoDin actually stores in the database.

Dictionaries support multi-language translations (e.g. English, Dutch); language switch happens at a setting level and applies to layer descriptions.

Every dictionary is stored as a separate file with a `.GSD` extension in the syslib folder (`C:\ProgramData\GeoDin\System\`).

Example dictionary files: `G1_Investigation_Method`, `BS5930_Walker_Secondary_Soil_Type`, `G1_EPSG` (coordinate systems), `Sample_Type`.

## Viewing dictionary entries

Dictionaries are viewable/editable via `System > Dictionaries > [dictionary name]` - double-click to see all entries with short code and language translations.

## How dictionaries behave in forms

Some dictionaries are context-sensitive - e.g. the secondary soil type dictionary is restricted based on the primary ground type (clay+silt vs coarse-grain).

Some dictionary-backed fields allow free-text entry in addition to dictionary selection; free text does not add the value to the dictionary.

## Editing dictionaries

Users can add their own terms to dictionaries (new clients, new labs, new soil types).

When a user edits a dictionary, a timestamp is recorded and that dictionary becomes "frozen" - GeoDin distribution updates will no longer overwrite it, preserving user changes.

Users should keep a list of dictionaries they have edited so they can request updates from GeoDin support when needed.

Low-risk dictionaries (clients list, lab names) can be edited freely; higher-risk dictionaries (soil types, field patterns) require more care because missing distribution updates could matter.

## Sharing custom dictionaries

When sending data to a client without the same custom dictionaries, the user must also send the `.GSD` dictionary files or the full syslib folder.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.geodin.com/concepts/dictionaries.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
