> 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/de/objektarten/ka6-bodenkundlicher-aufschluss.md).

# (KA6) Bodenkundlicher Aufschluss

Eingeführt in GeoDin 15.6 (Release 15.6.6.125, Juni 2026) unterstützt die Objektart KA6 die 6. Auflage der deutschen Bodenkundlichen Kartieranleitung (Bodenkundliche Kartieranleitung, KA6), die in Deutschland seit Juli 2024 verbindlich ist. Sie umfasst diagnostische Horizonte, überarbeitete Horizont-Symbole, das erweiterte Substratsystem und die neuen Bodentypen, die von KA6 definiert werden. Projekte, die der 5. Auflage folgen, können die bestehende KA5-Unterstützung weiter nutzen.

{% hint style="info" %}
**Ressourcen für den deutschen Markt (Deutsch)**

* [Bodenkundlicher Aufschluss nach KA5](https://support.geodin.com/hc/de/articles/360016072780-Bodenkundlicher-Aufschluss-nach-KA5)
* [Bodenkundlicher Aufschluss nach 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/de/objektarten/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.