> 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/apidokyumento/furno/1.-pu-chang-deng-lu.md).
# 1. 圃場登録
Field登録シーケンス図は、GeoPardで新しいFieldエンティティを登録するプロセスの概要を示します。
最初のステップはFarmエンティティの作成を含みます（[リクエスト1 または R1](/geopard-tutorials/jpn/apidokyumento/geopard-apirikuesuto/13-mytshon-wo.md)）。FarmはFieldの必須の親エンティティであり、Fieldを登録する前に作成する必要があります。
Farmエンティティの作成に続く第2のステップはFieldの登録を伴います（[リクエスト2 または R2](/geopard-tutorials/jpn/apidokyumento/geopard-apirikuesuto/14-mytshon-womatahanoworaberuha.md)）。このステップでは、Farmに紐づくUUIDやField境界などの必須パラメータが提供されます。ラベルは登録時に任意ですが、割り当てることも可能です。
その後、Field登録後にラベルを割り当てたり更新したりすることができます。 [リクエスト3 または R3](/geopard-tutorials/jpn/apidokyumento/geopard-apirikuesuto/44-mytshon-raberuwo.md).
シーケンス図：Field登録
---
# 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/apidokyumento/furno/1.-pu-chang-deng-lu.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.
