> 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-desktop/fr/types-dobjets/ka6-bodenkundlicher-aufschluss.md).

# (KA6) Ouverture pédologique

Introduit inclus GeoDin 15.6 (version 15.6.6.125, Juin 2026), le Type de puits KA6 prend en charge la 6e édition des directives de relevé des sols Allemand (Bodenkundliche Kartieranleitung, KA6), obligatoire inclus Allemagne depuis Juillet 2024. Il couvre les horizons diagnostiques, les Symboles d'horizon révisés, le Système de substrat étendu ET les Nouveau types de sols définis par KA6. Les Projets suivant la 5e édition peuvent Continuer sur Utiliser le support KA5 existant.

{% hint style="info" %}
**Ressources du marché Allemand (Deutsch)**

* [Profil pédologique selon KA5](https://support.geodin.com/hc/de/articles/360016072780-Bodenkundlicher-Aufschluss-nach-KA5)
* [Profil pédologique selon KA6](https://support.geodin.com/hc/de/articles/28347769127196-Bodenkundlicher-Aufschluss-nach-KA6)
  {% endhint %}


---

# 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-desktop/fr/types-dobjets/ka6-bodenkundlicher-aufschluss.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.