> 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/visualization-layouts-and-reporting/depth-oriented-images-as-borehole-profiles.md).

# Depth-Oriented Images as Borehole Profiles

### Requirements

* Image files in **BMP, JPG, PNG, or TIF** format.
* Document object type **`(DOC) Depth-oriented image [DOC_DEPT]`** installed in GeoDin and registered in the database.

### Step 1: Check object type installation

Verify that `(DOC) Depth-oriented image [DOC_DEPT]` is installed in your GeoDin system. If not, install it (see [Installing Object Types](/object-types/installing.md)).

### Step 2: Prepare and attach images

Name your image files clearly (e.g., by drill core section) for easy depth assignment. Add the images as documents to the borehole and register the document description `(DOC) Depth-oriented image [DOC_DEPT]` in the database if needed. For each image, enter depth values under the **Dimensions** tab.

{% hint style="info" %}
Place all core photos in one folder (e.g., `core photos`) for easier display later.
{% endhint %}

<div align="center"><figure><img src="https://3138966068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOh9veY55xgALNVUW8siX%2Fuploads%2Fgit-blob-ff271bf672cc8147b8f26c07c6527e58a1906c41%2Fimage%20(42).png?alt=media" alt=""><figcaption></figcaption></figure></div>

### Step 3: Display images in a layout

1. Use a reference graphic element based on the borehole's vertical scale (e.g., borehole log, well design, samples).
2. Add a **borehole log** element next to the reference element.
3. In the borehole log's **object properties**, set the data source to **Documents**.
4. Click **Browse Documents** and select the folder containing the depth-oriented images.
5. GeoDin will automatically stitch images at the correct depths based on the **Dimensions** tab values.

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

### Optional image display settings

* **Pixel position from/to:** Defines which pixel lines correspond to the depth values. Top margin equals pixel position 0.
* **Pixel position left/right:** Crop unwanted left and right margins by specifying pixel positions.
* **Pixel position header from/to:** Define a header area to display above the image column. Enable "Draw header" in object properties under `Properties > Document settings > Header`.
* **Rotation angle:** Rotate the image before mosaicking into the profile.

***

The borehole log element is not limited to layer data and documents: any database table with a depth value (e.g., sample data or well design data) can serve as its data source. Select the table with the icon at the right of the entry field in the element's object properties. For layer data, choose between **Original data** (the database contents as recorded) and analyzed contents based on a [layer query](/data-analysis/layer-queries.md).

Detailed borehole-log element reference: [Borehole Elements](/visualization-layouts-and-reporting/creating-custom-layouts/borehole-elements.md).


---

# 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/visualization-layouts-and-reporting/depth-oriented-images-as-borehole-profiles.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.