> For the complete documentation index, see [llms.txt](https://docs.geopard.tech/geopard-tutorials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geopard.tech/geopard-tutorials/jpn/nong-xue/soil-lime-and-tillage/vr-tillage-from-soil-compaction.md).

# 土壌締め固まりに基づく可変耕起

複数の深さで測定した土壌締め固まりデータを用いて、可変耕起アプリケーションを作成します。

{% hint style="success" %}
開始点となるのは、複数の深度で測定した土壌硬度データセット（または同等のデータセット）です。
{% endhint %}

{% hint style="warning" %}
以下のチュートリアルは複数の言語に対応しています。言語アイコンから、ご希望の言語を選択してください。 <img src="https://1993076779-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2FBI5BLx6lztxQTYIHqvsr%2Fimage.png?alt=media&amp;token=0d402011-668e-4a9c-8853-0fb4f56ace99" alt="" data-size="line">.
{% endhint %}

## 単一圃場の可変率耕起アプリケーション

以下では、単一圃場の土壌硬度データを使って可変率耕起アプリケーションを作成する方法を紹介する、多言語対応のインタラクティブガイドをご覧いただけます。

{% @arcade/embed url="<https://app.arcade.software/share/WTv30agzTwuMh8wQuIEm>" flowId="WTv30agzTwuMh8wQuIEm" %}

## 複数圃場の可変率耕起マップ

以下では、インタラクティブな *多言語対応の* ガイドをご覧いただけます。このガイドでは、3圃場を対象に、土壌硬度データに基づいて可変率耕起マップを作成する方法を紹介します。

{% @arcade/embed url="<https://app.arcade.software/share/3xbue8272p71qIRWCiA6>" flowId="3xbue8272p71qIRWCiA6" %}

## 使用する計算式

以下は、深度25 cmでの土壌硬度値に基づいて耕起深度を算出する計算式です。

この計算式（またはその変形版）は、GeoPardのカスタム計算式ライブラリに保存できます。

```python
if pressure < 15:
    tillage_depth = 25
elif pressure < 21:
    tillage_depth = 27
else:
    tillage_depth = 30
```


---

# 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.geopard.tech/geopard-tutorials/jpn/nong-xue/soil-lime-and-tillage/vr-tillage-from-soil-compaction.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.
