> 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.md). # Concepts - [Borehole and Location Model](https://docs.geodin.com/concepts/borehole-and-location-model.md): GeoDin's General Data model for borehole and location records - [Layer and Stratigraphy](https://docs.geodin.com/concepts/layer-and-stratigraphy.md): GeoDin's Layer Data model - soil/rock layers, ground descriptions, and coding - [Sample and Specimen Model](https://docs.geodin.com/concepts/sample-and-specimen-model.md): GeoDin's data model for samples, specimens, and the parent-child relationships between them - [Object Types](https://docs.geodin.com/concepts/object-types.md): GeoDin object types - the data-entry schemas (G1, AGS4, German SEP3, ISO, and others) behind boreholes, locations, and custom tables. - [Dictionaries](https://docs.geodin.com/concepts/dictionaries.md): GeoDin dictionaries - the coded value lists behind drop-down fields - [Data Types](https://docs.geodin.com/concepts/data-types.md): Reference list of the (G1) Location Data Types available in GeoDin for geotechnical, geological, and laboratory data - name, short name, long name/description, and which are complex data types. --- # 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.md?ask=&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.