> 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/borehole-and-location-model.md).

# Borehole and Location Model

GeoDin's General Data model for borehole and location records

The **General Data** section of a GeoDin object holds the headline record for a borehole or location: identifiers, project context, geometry, and the drilling/sampling metadata that all downstream tables hang off.

For the related concepts, see also:

* [Layer and Stratigraphy](https://docs.geodin.com/concepts/layer-and-stratigraphy.md) - soil/rock layers and ground descriptions attached to a location.
* [Sample and Specimen Model](https://docs.geodin.com/concepts/sample-and-specimen-model.md) - samples taken from a location.
* [Object Types](https://docs.geodin.com/concepts/object-types.md) - G1, AGS, and other object-type families.

## What General Data holds

* **Identifiers and project context:** borehole name, location name, project title, report number, client, method.
* **Geometry:** coordinates, coordinate system, depth, ground level, penetration, recovery.
* **Drilling information:** vessel, drilling method, drilling standard, start time, pressure on instrument, drilling tool type, auger/bit type, diameter.

## Compulsory fields

Compulsory fields (e.g. `Method` in general data) appear in a darker purple colour. Saving a record without a compulsory field triggers a validation error that names the missing field - the record cannot be persisted until the field is supplied.


---

# 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/borehole-and-location-model.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.
