> For the complete documentation index, see [llms.txt](https://docs.dietrichs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dietrichs.com/dietrichs-intelligent-documentation/docs-de-en/design-program/modellbereiche/dach/dachbauteile/dachbauteile-kehlbohle.md).

# Roof Components - Valley Board

With the selection list at the top of the dialog box you can choose existing settings. Using the disk icon you can save the current setting under the same name or a new name. Via the management icon you can create new settings, also by adopting existing settings, or modify or delete existing settings. See 'Save settings' in the 'General Help' manual.

**Identification number:** The identification number determines the material of the valley board. Using the switch at the end of the field, you can branch into the database and select a material.

**Thickness:** Thickness of the valley board.

**Height:** Height (width on the roof) of the valley board. For the height, a fixed value can be entered or it can be calculated according to the rafters. If you choose the option 'by rafters', the following fields are enabled. There you can enter a rounding value and the offset height for both sides.

**Rounding for height:** If the height of the valley board is calculated according to the rafters, you can enter a rounding value here. The calculated height will then be rounded up to the next whole value set here. Thus a value of '0.02m' will always produce heights (cm) of: 10, 12, 14, 16, etc.

**Offset height adjacent roof:** For the calculation 'by rafters' the program requires the offset height of the adjacent roof.

**Chamfering:** The valley board can be chamfered differently:

> **only top:** The valley board is chamfered only at the top edge.
>
> **top and bottom:** The valley board is chamfered at the top and bottom edges.
>
> **None:** The valley board is not chamfered.

**Lies on top layer:** The board is placed on the top of the layer specified here. If the board is to be placed directly on the rafters from layer 0, select layer 0 here. If the board is to lie on the sheathing from layer -1, select layer -1 here.

**Valley board at eave:** For the connection of the valley board to an eave you can optionally set 'horizontal', 'vertical' or 'like rafters'. With the 'horizontal' option the valley board is cut horizontally parallel to the main roof eave. With the 'vertical' option it is cut vertically parallel to the adjacent roof eave. With the 'like rafters' option the board receives the same cut as the first rafter of the adjacent roof surface next to the board. The rafter sections are adopted so that they lie in one plane. If the rafter has a concave or convex profile, the board is cut as if the rafter had a rectangular section.

After setting all values and options, the valley board can be entered using the following buttons:

**All valley lines:** The configured valley board is generated on all valley lines.

**Valley lines:** The valley board is generated on the valley line or lines that were selected graphically.

**Length-limited:** The length and position of the valley board can be entered using two points.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.dietrichs.com/dietrichs-intelligent-documentation/docs-de-en/design-program/modellbereiche/dach/dachbauteile/dachbauteile-kehlbohle.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.