> 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/tsu-webapuri/znmapputo/znwodematahareiykara.md).

# ゾーンを手動で描画、または既存レイヤーから複製

カスタムゾーンを手動で描画するか、既存レイヤーのポリゴンを複製してすばやく編集します。

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

*インタラクティブデモ - ポリゴンの複製、ゾーンの分割、新しい区画の作成、散布量の割り当て、エクスポート*

GeoPardでは、ゾーンを手動で描画できます。

オプション:

* ゼロから描画
* 既存レイヤーの複製から開始する（この場合は散布実績）
* 試験区画を追加
* ポリゴンの結合/分割/集約
* 製品の散布量を割り当て
* 最終マップをさまざまな形式（iso、shp）でエクスポートするか、統合プラットフォーム（John Deere Ops Center、Climate FieldView）へ直接送信する


---

# 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/tsu-webapuri/znmapputo/znwodematahareiykara.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.