> 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/esp/documentacion-de-la-api/diagrams-with-basic-flows/1.-field-registration.md).

# 1. Registro de parcela

El diagrama de secuencia del registro de parcelas describe el proceso para registrar una nueva entidad de parcela en GeoPard.

El primer paso consiste en crear una entidad de explotación ([Solicitud 1 o R1](https://docs.geopard.tech/geopard-tutorials/esp/documentacion-de-la-api/geopard-api-requests-overview/13.-mutation-create-farm.md)). La explotación es una entidad superior obligatoria para la parcela y debe crearse antes de registrar esta última.

Una vez creada la entidad de explotación, el segundo paso consiste en registrar la parcela ([Solicitud 2 o R2](https://docs.geopard.tech/geopard-tutorials/esp/documentacion-de-la-api/geopard-api-requests-overview/14.-mutation-create-a-field-or-edit-the-boundary-of-the-existing-field-with-optional-labels.md)). En este paso se proporcionan parámetros obligatorios, como el UUID asociado a la explotación y el límite de la parcela. También se pueden asignar etiquetas, aunque son opcionales durante el registro.

A continuación, se pueden asignar o actualizar etiquetas después de registrar la parcela mediante la [Solicitud 3 o R3](https://docs.geopard.tech/geopard-tutorials/esp/documentacion-de-la-api/geopard-api-requests-overview/44.-mutation-set-field-labels.md).

<figure><img src="https://2708050521-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2FC6kAAhocq29uHkKNXKqv%2Fimage.png?alt=media&amp;token=30256021-be12-480e-9f92-1ed4451525b2" alt=""><figcaption><p>Diagrama de secuencia: registro de parcelas</p></figcaption></figure>


---

# 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/esp/documentacion-de-la-api/diagrams-with-basic-flows/1.-field-registration.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.
