> 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/geodin-onsite/configuration/geo-data-standards.md).

# Geo-data standards

A **geo-data standard** defines the schema for describing drilling, sampling, and layer data - what columns exist, what values are allowed, what units are used. Different countries and industries use different standards. Onsite supports several of them and lets you choose the right one for each project.

Standards are configured in Configuration > Integration > Geo-data delivery, via the settings (gear) button.

## Supported standards

This version of Onsite supports five standards. When you select one, Onsite also asks you to pick the relevant **description types** associated with it - the specific logging conventions your project uses.

<figure><img src="https://1217489807-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmQJR7ILUjg2L6Y9M99Va%2Fuploads%2Fgit-blob-955af4002e7ed4c3ca61039aca7e71f68bc463c6%2Fimage%20(28).png?alt=media" alt=""><figcaption></figcaption></figure>

## Choose your standard before starting

Decide on the standard **before** you create any forms for a project. Standards affect which fields appear, how data is entered, and what the exported GeoDinML will look like - they need to be correct from day one.

{% hint style="danger" %}
**Once a standard is applied and the project has active forms, it cannot be changed retroactively.** If you realise you've picked the wrong standard after creating forms, you'll need to start a new project with the correct standard.
{% endhint %}

## The standards tab is locked when forms are open

If any forms are currently open in Onsite, the geo-data delivery tab is locked - you cannot change the standard while forms are being edited.

{% hint style="info" %}
If you see this error, close all open forms and try again.

<img src="https://1217489807-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmQJR7ILUjg2L6Y9M99Va%2Fuploads%2Fgit-blob-4e6fc82f25b5c75eda820e0ecd9b643a8ea80855%2Fimage%20(29).png?alt=media" alt="" data-size="original">
{% endhint %}

***

**See also**

* [Project setup](/geodin-onsite/configuration/project-setup.md) - configure the project this standard applies to
* [Exporting to GeoDin](/geodin-onsite/guides/exporting-to-geodin.md) - how your standard shapes the GeoDinML export


---

# 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/geodin-onsite/configuration/geo-data-standards.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.